Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING Error SCCM Client Push not working

  • Thread starter Thread starter Sachinbca
  • Start date Start date
  • Replies Replies 8
  • Views Views 7K

Sachinbca

Member
Messages
5
Reaction score
0
Points
1
======>Begin Processing request: "2097152004", machine name: "SAXOWKS3" SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:44 PM 5916 (0x171C)
Execute query exec [sp_IsMPAvailable] N'000' SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:44 PM 5916 (0x171C)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:44 PM 5916 (0x171C)
---> Attempting to connect to administrative share '\\SAXOWKS3\admin$' using account 'SAXOBANK\Administrator' SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:44 PM 5916 (0x171C)
---> Connected to administrative share on machine SAXOWKS3 using account 'SAXOBANK\Administrator' SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:44 PM 5916 (0x171C)
---> Attempting to make IPC connection to share <\\SAXOWKS3\IPC$> SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:44 PM 5916 (0x171C)
---> Searching for SMSClientInstall.* under '\\SAXOWKS3\admin$\' SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:44 PM 5916 (0x171C)
---> System OS version string "6.3.9600" converted to 6.30 SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:45 PM 5916 (0x171C)
---> Unable to connect to WMI (root\ccm) on remote machine "SAXOWKS3", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:45 PM 5916 (0x171C)
---> Creating \ VerifyingCopying exsistance of destination directory \\SAXOWKS3\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:45 PM 5916 (0x171C)
---> Copying client files to \\SAXOWKS3\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:45 PM 5916 (0x171C)
---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "MobileClient.tcf" SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:45 PM 5916 (0x171C)
---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe" SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:45 PM 5916 (0x171C)
---> Updated service "ccmsetup" on machine "SAXOWKS3". SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:46 PM 5916 (0x171C)
---> Started service "ccmsetup" on machine "SAXOWKS3". SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:46 PM 5916 (0x171C)
---> Deleting SMS Client Install Lock File '\\SAXOWKS3\admin$\SMSClientInstall.000' SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:46 PM 5916 (0x171C)
Execute query exec [sp_CP_SetLastErrorCode] 2097152004, 0 SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:46 PM 5916 (0x171C)
---> Completed request "2097152004", machine name "SAXOWKS3". SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:46 PM 5916 (0x171C)
Deleted request "2097152004", machine name "SAXOWKS3" SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:46 PM 5916 (0x171C)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152004, 4 SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:46 PM 5916 (0x171C)
Execute query exec [sp_CP_SetLatest] 2097152004, N'01/04/2019 12:07:46', 20 SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:46 PM 5916 (0x171C)
<======End request: "2097152004", machine name: "SAXOWKS3". SMS_CLIENT_CONFIG_MANAGER 1/4/2019 5:37:46 PM 5916 (0x171C)
 
There are no error within that log snipit. everything is normal.
 
Updated service "ccmsetup" on machine "SAXOWKS3"
Started service "ccmsetup" on machine "SAXOWKS3"

The client seems to be installed. What's not working ?.
 
Updated service "ccmsetup" on machine "SAXOWKS3"
Started service "ccmsetup" on machine "SAXOWKS3"

The client seems to be installed. What's not working ?.
Thanks Prajwal for your reply.
Well, Configuration Manger is not available in Control Panel also Client installation status shows "NO" in Devices for SAXOWKS3.
 
Did you looked at the Setup log on the computer?


following the logs on client machine SAXOWKS3

==========[ ccmsetup started in process 3984 ]========== ccmsetup 1/9/2019 2:10:16 PM 2812 (0x0AFC)
Running on platform X64 ccmsetup 1/9/2019 2:10:16 PM 2812 (0x0AFC)
Updated security on object C:\Windows\ccmsetup\cache\. ccmsetup 1/9/2019 2:10:16 PM 2812 (0x0AFC)
Launch from folder C:\Windows\ccmsetup\ ccmsetup 1/9/2019 2:10:16 PM 2812 (0x0AFC)
CcmSetup version: 5.0.7958.1000 ccmsetup 1/9/2019 2:10:16 PM 2812 (0x0AFC)
In ServiceMain ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
Running on 'Microsoft Windows 8.1 Pro' (6.3.9600). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
SslState value: 224 ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
CCMHTTPPORT: 80 ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
CCMHTTPSPORT: 443 ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
CCMHTTPSSTATE: 63 ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
CCMHTTPSCERTNAME: ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
FSP: SYSSCCM1.SAXOBANK.COM ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
CCMFIRSTCERT: 1 ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
Config file: C:\Windows\ccmsetup\MobileClientUnicode.tcf ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
Retry time: 10 minute(s) ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
MSI log file: C:\Windows\ccmsetup\Logs\client.msi.log ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
MSI properties: INSTALL="ALL" SMSSITECODE="000" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="63" FSP="SYSSCCM1.SAXOBANK.COM" CCMFIRSTCERT="1" ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
Source List: ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
\\SYSSCCM1.saxobank.com\SMSClient ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
\\SYSSCCM1.SAXOBANK.COM\SMSClient ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
MPs: ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
HTTPS://SYSSCCM1.saxobank.com ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
MapNLMCostDataToCCMCost() returning Cost 0x1 ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
No version of the client is currently detected. ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
Updated security on object C:\Windows\ccmsetup\. ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
Sending Fallback Status Point message to 'SYSSCCM1.SAXOBANK.COM', STATEID='100'. ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
Params to send FSP message '5.0.7958.1000 Deployment ' ccmsetup 1/9/2019 2:10:16 PM 4004 (0x0FA4)
State message with TopicType 800 and TopicId {F3AFFED6-CDE1-4EC3-9209-57F7BF621067} has been sent to the FSP FSPStateMessage 1/9/2019 2:10:17 PM 4004 (0x0FA4)
Running as user "SYSTEM" ccmsetup 1/9/2019 2:10:17 PM 4004 (0x0FA4)
Detected 15138 MB free disk space on system drive. ccmsetup 1/9/2019 2:10:17 PM 4004 (0x0FA4)
Checking Write Filter Status. ccmsetup 1/9/2019 2:10:17 PM 4004 (0x0FA4)
This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 1/9/2019 2:10:17 PM 4004 (0x0FA4)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=000))' ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>63</SecurityModeMask><SecurityModeMaskEx>63</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F2308201DAA003020102021072C4B925250A7D8F48BFFF72F7B19A3F300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3138313232353132343832325A180F32313138313230323132343832325A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100AB73D9487B4F01C92583AE85BF42AF83134E5657CB76B07422ACEEB3053655E24D62466D1C536B74BA90FE4175225827CF262BDF879D3820F3C970F6043F3578FE8676752B088218BCCE239B1523024C8B4CA10D74CB1E6F4F2E041E8EA51E9764AD3CCDAB8B1EFE661EB6DE1CF75A70298C62F3386E59CD2B064699BAA95CE12C2D5E5BFC8ED2E4C56CD56B73FAC8F3CB11A798471EA89C2C23AC2B2A94C525ED852C34952A4E70B6A7870D46000AA625A045CBB133772173241C08E889CE88B4940274E8FC5E4AEF393C4D25B449A6AED272265FC44424C7746A2AE901EFB2FE376AD50B5706AA8133693AD82E8F572CC7A2E91513F7E56795EF4857CF91750203010001A33A303830200603551D110419301782155359535343434D312E7361786F62616E6B2E636F6D30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B050003820101008B270F97F79C61374223C1A7AECB65B5BABC99D40DDF38A55D6A66E64046F814432F4C533C3FD3296257786346A8EFDFA1C0BAA574AA77D890A7A49B31DADF4943D01666F7DCA8EEACDB3AE530B8DEF30091677B6A6E8C03A83BA04C7EEF56119A950DEAE72B72BCF3D9588A0D2559878B52ECF3287FF9286005152F32EC66CAE4B3A028DE9818E8E119F3875BC90AF79A8C9A43A93EDCC3ADC14728CB0DBAB46FD57841221EA839B418A7EFC7F722FB0B8E65F169F44C5000A51D66D34BD7EB0C3C418F31614E993B1FB2CA321A1602DA043C8470B598668CE4B0B7B6CE84186FDE564B8D60998945BFF6B1BE1F775E44756D51DF1F4A602AAA42C9CD32FB6E</SiteSigningCert></SecurityConfiguration><RootSiteCode>000</RootSiteCode><CCM> <CommandLine>SMSSITECODE=000</CommandLine> </CCM><FSP> <FSPServer>SYSSCCM1.saxobank.com</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState" Value="63" /></Capabilities><Domain Value="saxobank.com" /><Forest Value="saxobank.com" /></ClientOperationalSettings>' ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown. ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
The MP name retrieved is 'SYSSCCM1.saxobank.com' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="63"/></Capabilities>' ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
MP 'SYSSCCM1.saxobank.com' is compatible ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Retrieved 1 MP records from AD for site '000' ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Retrived site version '5.00.7958.1000' from AD for site '000' ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
 
SiteCode: 000 ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
SiteVersion: 5.00.7958.1000 ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Only one MP HTTPS://SYSSCCM1.saxobank.com is specified. Use it. ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Searching for DP locations from MP(s)... ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Current AD site of machine is Default-First-Site-Name LocationServices 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Local Machine is joined to an AD domain LocationServices 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Current AD forest name is saxobank.com, domain name is saxobank.com LocationServices 1/9/2019 2:10:18 PM 4004 (0x0FA4)
DhcpGetOriginalSubnetMask entry point is supported. LocationServices 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Begin checking Alternate Network Configuration LocationServices 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Finished checking Alternate Network Configuration LocationServices 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Sending message body '<ContentLocationRequest SchemaVersion="1.00">
<AssignedSite SiteCode="000"/>
<ClientPackage/>
<ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseInternetDP="0">
<ADSite Name="Default-First-Site-Name"/>
<Forest Name="saxobank.com"/>
<Domain Name="saxobank.com"/>
<IPAddresses>
<IPAddress SubnetAddress="192.168.1.0" Address="192.168.1.13"/>
</IPAddresses>
</ClientLocationInfo>
</ContentLocationRequest>
' ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Sending message header '<Msg SchemaVersion="1.1"><ID>{2AC55E0F-683A-4876-BE85-F565E024302B}</ID><SourceHost>SAXOWKS3</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:SAXOWKS3:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>HTTPS://SYSSCCM1.saxobank.com</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2019-01-09T08:40:18Z</SentTime><Body Type="ByteRange" Offset="0" Length="1126"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>' ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
MapNLMCostDataToCCMCost() returning Cost 0x1 ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
CCM_POST 'HTTPS://SYSSCCM1.saxobank.com/ccm_system/request' ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Begin searching client certificates based on Certificate Issuers ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Completed searching client certificates based on Certificate Issuers ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Begin to select client certificate ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
The 'Certificate Selection Criteria' was not specified, counting number of certificates present in 'MY' store of 'Local Computer'. ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
There are no certificates in the 'MY' store. ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
GetSSLCertificateContext failed with error 0x87d00280 ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Sending Fallback Status Point message to 'SYSSCCM1.SAXOBANK.COM', STATEID='315'. ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
Params to send FSP message '5.0.7958.1000 Deployment Error 0x87d00280' ccmsetup 1/9/2019 2:10:18 PM 4004 (0x0FA4)
State message with TopicType 800 and TopicId {649E7BF2-B213-4363-B6AC-76EC082CA651} has been sent to the FSP FSPStateMessage 1/9/2019 2:10:18 PM 4004 (0x0FA4)
GetHttpRequestObjects failed for verb: 'CCM_POST', url:
 
and is that the last line of the log file. other than the 3rd line of the second post, there isn't anything showing a real failure.
 

Forum statistics

Threads
7,214
Messages
28,141
Members
18,413
Latest member
Vmaldonado

Trending content

Back
Top