locked
While installing ccm client we get : Failed to receive ccm message response. Status code = 500 RRS feed

  • Question

  • We have stacked into an issue where repeatly we get the following error :

    Failed to receive ccm message response. Status code = 500 ccmsetup 15/06/2012 08:13:20 1520 (0x05F0)
    GetDPLocations failed with error 0x80004005 ccmsetup 15/06/2012 08:13:20 1520 (0x05F0)
    Failed to get DP locations as the expected version from MP 'HTTPS://cif-sec-05.ikos.com'. Error 0x80004005 ccmsetup 15/06/2012 08:13:20 1520 (0x05F0)

    While installing the ccm client via push installation.

    In addition for the clients with the agent installed we get from CcmMessaging.log, LocationServices.log,ClientIDManagerStartup.log :

    Post to https://server-mp01/ccm_system_windowsauth/request failed with 0x87d00231. CcmMessaging

    Failed to send management point list Location Request Message to cif-sec-05.ikos.com LocationServices

    [RegTask] - Client is not registered. Sending registration request for GUID:4E5A0D21-4E24-4B71-A3E0-BA1E61A262B9 ... ClientIDManagerStartup (0x0E28)
    RegTask: Failed to send registration request message. Error: 0x87d00231 ClientIDManagerStartup  (0x0E28)
    RegTask: Failed to send registration request. Error: 0x87d00231 ClientIDManagerStartup (0x0E28)
    [RegTask] - Sleeping for 1920 seconds ... ClientIDManagerStartup (0x0E28)

    Bearing in mind that our setup have been functioning properly (certificates, shares , settings etc) what could cause the above behavior?
    Any ideas why?

    Many Thanks,
    YV


    • Edited by Cyprus IT Friday, June 15, 2012 11:01 AM
    Friday, June 15, 2012 6:35 AM

Answers

  • Sorry to keep posting...found a work around until I get some help on the Certificate front.

    Site Properties - Client Communications tab - I unchecked the Use PKI client certificate (client authentication capability) when available.

    Friday, June 29, 2012 1:45 PM

All replies

  • Is the site published in AD? Or do you use severall parameters in the client installation properties to let the client know where his Management Point is?


    Dennis de Roo

    Monday, June 18, 2012 10:25 AM
  • Also, how about the boundary assignment ?

    Anoop C Nair - @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    User Group:  ConfigMgr Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Monday, June 18, 2012 11:05 AM
  • I am actually having the same issue.  The site is published in AD. The boundary assignments are setup as IP Ranges, and they appear correct.  I have about 30 to 40 percent of my PC's that show as having active Clients.  The rest seemed to have CCMExec running but don't seem to be talking back to the MP or even FSP. It doesn't seem to be tied to any 1 boundary either.  It is fairly random.  This is not an upgrade from previous SCCM versions. In the client push installation properties I don't have it setting where the MP is, should I try that and then push the installation again to the clients that aren't registering (SMSMP=MPSERVER)? I do have the parameters in there to tell the client where the FSP is.

    Here is the ClientIDManagerStartupLog:

    <![LOG[GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE]LOG]!><time="08:28:11.444+300" date="06-28-2012" component="ClientIDManagerStartup" context="" type="1" thread="3896" file="ccmid.cpp:210">
    <![LOG[Computed HardwareID=2:82B76386318F9DF77104796A9800139C0BDEE4A1
        Win32_SystemEnclosure.SerialNumber=FJVNY11                        
        Win32_SystemEnclosure.SMBIOSAssetTag=                               
        Win32_BaseBoard.SerialNumber=CN02P997481112990192           
        Win32_BIOS.SerialNumber=                               
        Win32_NetworkAdapterConfiguration.MACAddress=00:01:03:E0:8C:DC]LOG]!><time="08:28:11.490+300" date="06-28-2012" component="ClientIDManagerStartup" context="" type="1" thread="3896" file="ccmid.cpp:449">
    <![LOG[[RegTask] - Client is not registered. Sending registration request for GUID:68CF8909-B750-433C-AA76-31A84D0FC2F5 ...]LOG]!><time="08:28:11.522+300" date="06-28-2012" component="ClientIDManagerStartup" context="" type="1" thread="3896" file="regtask.cpp:1595">
    <![LOG[[RegTask] - Server rejected registration request: 3]LOG]!><time="08:28:11.647+300" date="06-28-2012" component="ClientIDManagerStartup" context="" type="3" thread="3896" file="regtask.cpp:1662">
    <![LOG[Sleeping for 292 seconds before refreshing location services.]LOG]!><time="08:28:17.645+300" date="06-28-2012" component="ClientIDManagerStartup" context="" type="1" thread="3896" file="regtask.cpp:192">

    Thursday, June 28, 2012 1:57 PM
  • <![LOG[[RegTask] - Server rejected registration request: 3]LOG]!><time="08:28:11.647+300" date="06-28-2012" component="ClientIDManagerStartup" context="" type="3" thread="3896" file="regtask.cpp:1662">

    See MP_Registration.log on the MP.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, June 28, 2012 3:05 PM
  • MP Reg: Client in-band certificate is not valid due to failures in certificate chain validation, Raising status event. Failure HR = 0x800b010a, In-band Cert SubjectName = OHTBRIDGEINTERFACECLIENT    MP_RegistrationManager    6/28/2012 10:51:01 AM    5328 (0x14D0)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of MpEvent_CertInvalidChain
    {
        ClientID = "GUID:E8C206FB-0D93-4184-B4CF-46735DFBDD9A";
        DateTime = "20120628155101.410000+000";
        MachineName = "MCBSCCM.mcbride.local";
        ProcessID = 1896;
        SiteCode = "MCB";
        SubjectName = "OHTBRIDGEINTERFACECLIENT";
        ThreadID = 5328;
        Win32ErrorCode = 2148204810;
    };
        MP_RegistrationManager    6/28/2012 10:51:01 AM    5328 (0x14D0)
    MP Reg: Registration request body is invalid.    MP_RegistrationManager    6/28/2012 10:51:01 AM    5328 (0x14D0)
    MP Reg: Registration failed.    MP_RegistrationManager    6/28/2012 10:51:01 AM    5328 (0x14D0)
    Thursday, June 28, 2012 3:51 PM
  • Here is the CCMSetup Log file for a client that supposedly has it installed but isn't checking back in with the MP.

    CcmSetup version: 5.0.7711.0000    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    Running on OS (5.1.2600). Service Pack (3.0). SuiteMask = 256. Product Type = 1    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    Ccmsetup command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    Command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    SslState value: 224    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    Invalid argument: MPSERVER    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    LoadConfigFile failed with error 0x80070057    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    Invalid ccmsetup command line:     ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    Sending Fallback Status Point message to 'FSPSERVER', STATEID='100'.    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    Params to send FSP message '5.0.7711.0000 Deployment '    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    State message with TopicType 800 and TopicId {4D1A1C4D-FB51-4C14-8CDE-995DB550AC54} has been sent to the FSP    FSPStateMessage    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    Sending Fallback Status Point message to 'FSPSERVER', STATEID='307'.    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    Params to send FSP message '5.0.7711.0000 Deployment '    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    State message with TopicType 800 and TopicId {6DAC06E5-7D43-4496-8E48-C9F44E56E22A} has been sent to the FSP    FSPStateMessage    6/28/2012 2:03:19 PM    3508 (0x0DB4)
    CcmSetup failed with error code 0x80070057    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)

    I am wondering why or where its getting the /config:MobileClient.tcf they are not mobile clients.
    • Edited by Zeptrey Thursday, June 28, 2012 7:48 PM
    Thursday, June 28, 2012 7:40 PM
  • Invalid argument: MPSERVER    ccmsetup    6/28/2012 2:03:19 PM    3508 (0x0DB4)

    MobileClient.tcf is ok, but it seems that you provided a wrong parameter. The client push properties are listed here: http://technet.microsoft.com/en-us/library/gg699356.aspx

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, June 29, 2012 7:00 AM
  • That's not it.  I set the Installation properties back to default and did a test, and I am still getting the same error in the ClientIDManagerStartup:

    GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE    ClientIDManagerStartup    6/29/2012 7:22:16 AM    2604 (0x0A2C)
    Computed HardwareID=2:2D748C0BF9D9D80DB8A3249297126A35FD9A7683
        Win32_SystemEnclosure.SerialNumber=5H67KN1
        Win32_SystemEnclosure.SMBIOSAssetTag=          
        Win32_BaseBoard.SerialNumber=..CN1374007R03O7.
        Win32_BIOS.SerialNumber=5H67KN1
        Win32_NetworkAdapterConfiguration.MACAddress=F0:4D:A2:22:28:80    ClientIDManagerStartup    6/29/2012 7:22:16 AM    2604 (0x0A2C)
    [RegTask] - Client is not registered. Sending registration request for GUID:A69BA2B0-F953-45CA-8A24-9A095EC2E104 ...    ClientIDManagerStartup    6/29/2012 7:22:16 AM    2604 (0x0A2C)
    [RegTask] - Server rejected registration request: 3    ClientIDManagerStartup    6/29/2012 7:22:16 AM    2604 (0x0A2C)

    Its a Cert issue, but not sure where to start.  I found this in the ClientIDManagerStartup Log as well:

    Begin to select client certificate    ClientIDManagerStartup    6/29/2012 7:33:29 AM    3032 (0x0BD8)
    Begin validation of Certificate [Thumbprint CEA8517F3CCAC97E221D2AE97B768D6D8F11C78F] issued to 'OHTBridgeInterfaceClient'    ClientIDManagerStartup    6/29/2012 7:33:29 AM    3032 (0x0BD8)
    Completed validation of Certificate [Thumbprint CEA8517F3CCAC97E221D2AE97B768D6D8F11C78F] issued to 'OHTBridgeInterfaceClient'    ClientIDManagerStartup    6/29/2012 7:33:29 AM    3032 (0x0BD8)
    >>> Client selected the PKI Certificate [Thumbprint CEA8517F3CCAC97E221D2AE97B768D6D8F11C78F] issued to 'OHTBridgeInterfaceClient'    ClientIDManagerStartup    6/29/2012 7:33:29 AM    3032 (0x0BD8)
    Raising event:

    instance of CCM_ServiceHost_CertRetrieval_Status
    {
        ClientID = "GUID:A69BA2B0-F953-45CA-8A24-9A095EC2E104";
        DateTime = "20120629123329.268000+000";
        HRESULT = "0x00000000";
        ProcessID = 2988;
        ThreadID = 3032;
    };
        ClientIDManagerStartup    6/29/2012 7:33:29 AM    3032 (0x0BD8)
    Failed to submit event to the Status Agent. Attempting to create pending event.    ClientIDManagerStartup    6/29/2012 7:33:29 AM    3032 (0x0BD8)
    Raising pending event:

    instance of CCM_ServiceHost_CertRetrieval_Status
    {
        ClientID = "GUID:A69BA2B0-F953-45CA-8A24-9A095EC2E104";
        DateTime = "20120629123329.268000+000";
        HRESULT = "0x00000000";
        ProcessID = 2988;
        ThreadID = 3032;
    };
        ClientIDManagerStartup    6/29/2012 7:33:29 AM    3032 (0x0BD8)
    Client PKI cert is available.    ClientIDManagerStartup    6/29/2012 7:33:29 AM    3032 (0x0BD8)
    Initializing registration renewal for potential PKI issued certificate changes.    ClientIDManagerStartup    6/29/2012 7:33:39 AM    3584 (0x0E00)

    Friday, June 29, 2012 12:36 PM
  • I am seeing this over and over in the Component Status Message for SMS_MP_CONTROL_MANAGER:

    MP has rejected registration request due to failure in client certificate (Subject Name: OHTBRIDGEINTERFACECLIENT) chain validation. If this is a valid client, Configuration Manager Administrator needs to place the Root Certification Authority and Intermediate Certificate Authorities in the MPÆs Certificate store or configure Trusted Root Certification Authorities in primary site settings. The operating system reported error 2148204810: A certificate chain could not be built to a trusted root authority.

    Friday, June 29, 2012 12:37 PM
  • Sorry to keep posting...found a work around until I get some help on the Certificate front.

    Site Properties - Client Communications tab - I unchecked the Use PKI client certificate (client authentication capability) when available.

    Friday, June 29, 2012 1:45 PM