Home > MS Technologies, SCCM > Resolving “RegTask: Failed to send registration request message. Error: 0x87d00231” by repairing the Management Point

Resolving “RegTask: Failed to send registration request message. Error: 0x87d00231” by repairing the Management Point


Hi again!

When you install a new SCCM 2012 agent you can easily be a victim of this well known error “RegTask: Failed to send registration request message. Error: 0x87d00231”.

 

So, the client is installed successfully, but no information is collected on the SCCM console. This problem can cause another issue; the inactivity of the agents that were installed previously.

Searching for the right solution is not a so easy way because it depends on your case. In some posts or forums, they are speaking about certificates. However, in my case, the MP is configured to communicate using HTTP protocol.

In this article, I will describe the steps to follow in order to solve the problem. In my case the windows authentication module used by the MP was my issue. This article is not just applied on the case of the windows authentication module, you can try it to ensure that your MP is repaired correctly.

First of all, you have to understand the protocol of registering a new client :

  • The new client performs a CCM_POST to CCM_System_WindowsAuth on the MP.
  • The MP responds with a 401 as the request is anonymous and contains no security data.
  • The client requests a Kerberos ticket for http://MP_FQDN from Active Directory (e.g.http://SCCMMP.Contoso.com).
  • On obtaining the Kerberos ticket, the client performs another CCM_POST including the security data.
  • If the MP accepts the ticket then the client is authenticated and is considered to be trusted.
  • Whether the client is trusted or not, the MP executes the spUpdateClientRegistration stored procedure to update the database. If the client has authenticated properly, both the @ApprovalMethod and @IsIntegratedAuth parameters will be set to 1. If not, they are both set to 0. 

All these steps were described in this great article.

So I have tried to test the following request  http://mysccmserver/ccm_system_windowsauth/request  and bingo 403 error!

To have more details, I have consulted the IIS logs at %systemdrive%\Inetpub\Logs\LogFiles\W3SVC1\.

I have consulted my IIS manager and the SMS_MP_WindowsAuth Application under the default site was corrupted. In my case, this application was not associated to an application pool. I have created a new one but that does not solve my problem.

So, I have tried to uninstall and reinstall my MP. Unfortunately, the problem is still existing and the application is not repaired.

How to repair an MP? that is the question. Here you are a method that worked for me:

  • On the SCCM console select Administration Section
  • Select Site Configuration Group
  • Select Servers and Site System Roles
  • Select your Site System containing the right MP
  • Right Click on the MP role and select Properties
  • On General Tab, Select HTTPS Client Connection

This action will reinstall the MP and repair it. Please check the right SMS_MP_CONTROL_MANAGER log to verify if it is successfully repaired. If it is done, you have to redo the above steps to select HTTP as the Client Connection Protocol. This action will also reinstall and repair the MP.

Finally, I have Checked all Web Applications and the issue is solved. The Clients are registered and the inactive clients become active.

Advertisements
  1. Thiago
    April 23, 2013 at 2:25 pm

    Very good man! You save my life! lol… Now my MP is working fine on SCCM 2012.

  2. April 28, 2013 at 12:50 pm

    Hi Thiago, I am very happy for you.

  3. January 30, 2014 at 4:46 pm

    Hi ramzibot,

    I have been having very similar issues, as you have had here in this thread with SCCM 2k12. All the problems i’ve seen though seem to be pointing to an IIS issue. I tried the fix you posted here, by removing the MP, and reinstalling the MP role and restarting the server after each time, just to make sure that the changes to the MP role had taken place and to no avail, I still am having the same issues :/ Here is just the tail end of my ccmmessaging.log file – Any help with this would be appreciated – if you need other logfiles just ask..

    —————————————————————————————————–

    OutgoingMessage(Queue=’mp_[http]mp_policymanager’, ID={C04BD807-C534-4623-99C9-C63894D738BD}): Will be discarded (expired). CcmMessaging 1/29/2014 9:16:53 AM 5564 (0x15BC)
    [CCMHTTP] ERROR: URL=http://MW01-SCCM2.MWA.LOCAL/ccm_system/request, Port=80, Options=480, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE CcmMessaging 1/29/2014 9:16:53 AM 3752 (0x0EA8)
    Raising event:
    instance of CCM_CcmHttp_Status
    {
    ClientID = “GUID:69EE1D43-78BF-4551-BD15-67ECC83E3E89”;
    DateTime = “20140129151653.835000+000”;
    HostName = “MW01-SCCM2.MWA.LOCAL”;
    HRESULT = “0x87d0027e”;
    ProcessID = 2108;
    StatusCode = 500;
    ThreadID = 3752;
    };
    CcmMessaging 1/29/2014 9:16:53 AM 3752 (0x0EA8)
    Successfully sent location services HTTP failure message. CcmMessaging 1/29/2014 9:16:54 AM 3752 (0x0EA8)
    Post to http://MW01-SCCM2.MWA.LOCAL/ccm_system/request failed with 0x87d00231. CcmMessaging 1/29/2014 9:16:54 AM 3752 (0x0EA8)
    [CCMHTTP] ERROR: URL=http://MW01-SCCM2.MWA.LOCAL/ccm_system/request, Port=80, Options=480, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE CcmMessaging 1/29/2014 9:18:04 AM 4104 (0x1008)
    Raising event:
    instance of CCM_CcmHttp_Status
    {
    ClientID = “GUID:69EE1D43-78BF-4551-BD15-67ECC83E3E89”;
    DateTime = “20140129151804.563000+000”;
    HostName = “MW01-SCCM2.MWA.LOCAL”;
    HRESULT = “0x87d0027e”;
    ProcessID = 2108;
    StatusCode = 500;
    ThreadID = 4104;
    };
    CcmMessaging 1/29/2014 9:18:04 AM 4104 (0x1008)
    Successfully sent location services HTTP failure message. CcmMessaging 1/29/2014 9:18:04 AM 4104 (0x1008)
    Post to http://MW01-SCCM2.MWA.LOCAL/ccm_system/request failed with 0x87d00231. CcmMessaging 1/29/2014 9:18:04 AM 4104 (0x1008)
    [CCMHTTP] ERROR: URL=http://MW01-SCCM2.MWA.LOCAL/ccm_system/request, Port=80, Options=480, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE CcmMessaging 1/29/2014 9:19:44 AM 3752 (0x0EA8)
    Raising event:
    instance of CCM_CcmHttp_Status
    {
    ClientID = “GUID:69EE1D43-78BF-4551-BD15-67ECC83E3E89”;
    DateTime = “20140129151944.949000+000”;
    HostName = “MW01-SCCM2.MWA.LOCAL”;
    HRESULT = “0x87d0027e”;
    ProcessID = 2108;
    StatusCode = 500;
    ThreadID = 3752;
    };
    CcmMessaging 1/29/2014 9:19:44 AM 3752 (0x0EA8)
    Successfully sent location services HTTP failure message. CcmMessaging 1/29/2014 9:19:45 AM 3752 (0x0EA8)
    Post to http://MW01-SCCM2.MWA.LOCAL/ccm_system/request failed with 0x87d00231. CcmMessaging 1/29/2014 9:19:45 AM 3752 (0x0EA8)
    [CCMHTTP] ERROR: URL=http://MW01-SCCM2.MWA.LOCAL/ccm_system/request, Port=80, Options=480, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE CcmMessaging 1/29/2014 9:20:19 AM 3116 (0x0C2C)
    Raising event:
    instance of CCM_CcmHttp_Status
    {
    ClientID = “GUID:69EE1D43-78BF-4551-BD15-67ECC83E3E89”;
    DateTime = “20140129152019.689000+000”;
    HostName = “MW01-SCCM2.MWA.LOCAL”;
    HRESULT = “0x87d0027e”;
    ProcessID = 2108;
    StatusCode = 500;
    ThreadID = 3116;
    };
    CcmMessaging 1/29/2014 9:20:19 AM 3116 (0x0C2C)
    Successfully sent location services HTTP failure message. CcmMessaging 1/29/2014 9:20:20 AM 3116 (0x0C2C)
    Post to http://MW01-SCCM2.MWA.LOCAL/ccm_system/request failed with 0x87d00231. CcmMessaging 1/29/2014 9:20:20 AM 3116 (0x0C2C)

  4. January 31, 2014 at 7:36 am

    Hi Steve,

    Would you like to send me an IIS log, mpcontrol. log (on the server) and ClientIDManagerStartup.log (on the client) please?

  5. January 31, 2014 at 1:47 pm

    here’s the MPControl.log —–

    Successfully performed Management Point availability check against local computer. SMS_MP_CONTROL_MANAGER 1/29/2014 1:02:53 PM 5456 (0x1550)
    Initialization still in progress. SMS_MP_CONTROL_MANAGER 1/29/2014 1:02:53 PM 5456 (0x1550)
    SSL is not enabled. SMS_MP_CONTROL_MANAGER 1/29/2014 1:03:23 PM 5456 (0x1550)
    Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 1/29/2014 1:03:23 PM 5456 (0x1550)
    Sent summary record of SMS Management Point on [“Display=\\MW01-SCCM2.MWA.LOCAL\”]MSWNET:[“SMS_SITE=S01”]\\MW01-SCCM2.MWA.LOCAL\ to \\MW01-SCCM2.MWA.LOCAL\SMS_S01\inboxes\sitestat.box\k4yydfbx.SUM, Availability 1, 209712124 KB total disk space , 198736488 KB free disk space, installation state 0. SMS_MP_CONTROL_MANAGER 1/29/2014 1:03:23 PM 5456 (0x1550)
    Successfully performed Management Point availability check against local computer. SMS_MP_CONTROL_MANAGER 1/29/2014 1:03:23 PM 5456 (0x1550)
    Initialization still in progress. SMS_MP_CONTROL_MANAGER 1/29/2014 1:03:23 PM 5456 (0x1550)
    SSL is not enabled. SMS_MP_CONTROL_MANAGER 1/29/2014 1:03:53 PM 5456 (0x1550)
    Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 1/29/2014 1:03:53 PM 5456 (0x1550)
    Sent summary record of SMS Management Point on [“Display=\\MW01-SCCM2.MWA.LOCAL\”]MSWNET:[“SMS_SITE=S01”]\\MW01-SCCM2.MWA.LOCAL\ to \\MW01-SCCM2.MWA.LOCAL\SMS_S01\inboxes\sitestat.box\hdjcoh11.SUM, Availability 1, 209712124 KB total disk space , 198736452 KB free disk space, installation state 0. SMS_MP_CONTROL_MANAGER 1/29/2014 1:03:53 PM 5456 (0x1550)
    Successfully performed Management Point availability check against local computer. SMS_MP_CONTROL_MANAGER 1/29/2014 1:03:53 PM 5456 (0x1550)
    Initialization still in progress. SMS_MP_CONTROL_MANAGER 1/29/2014 1:03:53 PM 5456 (0x1550)
    SSL is not enabled. SMS_MP_CONTROL_MANAGER 1/29/2014 1:04:23 PM 5456 (0x1550)
    Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 1/29/2014 1:04:23 PM 5456 (0x1550)
    Sent summary record of SMS Management Point on [“Display=\\MW01-SCCM2.MWA.LOCAL\”]MSWNET:[“SMS_SITE=S01”]\\MW01-SCCM2.MWA.LOCAL\ to \\MW01-SCCM2.MWA.LOCAL\SMS_S01\inboxes\sitestat.box\4s634r18.SUM, Availability 1, 209712124 KB total disk space , 198736424 KB free disk space, installation state 0. SMS_MP_CONTROL_MANAGER 1/29/2014 1:04:23 PM 5456 (0x1550)
    Successfully performed Management Point availability check against local computer. SMS_MP_CONTROL_MANAGER 1/29/2014 1:04:23 PM 5456 (0x1550)
    Initialization still in progress. SMS_MP_CONTROL_MANAGER 1/29/2014 1:04:23 PM 5456 (0x1550)
    SSL is not enabled. SMS_MP_CONTROL_MANAGER 1/29/2014 1:04:53 PM 5456 (0x1550)
    Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 1/29/2014 1:04:53 PM 5456 (0x1550)
    Sent summary record of SMS Management Point on [“Display=\\MW01-SCCM2.MWA.LOCAL\”]MSWNET:[“SMS_SITE=S01”]\\MW01-SCCM2.MWA.LOCAL\ to \\MW01-SCCM2.MWA.LOCAL\SMS_S01\inboxes\sitestat.box1lvj71z.SUM, Availability 1, 209712124 KB total disk space , 198736384 KB free disk space, installation state 0. SMS_MP_CONTROL_MANAGER 1/29/2014 1:04:53 PM 5456 (0x1550)
    Successfully performed Management Point availability check against local computer. SMS_MP_CONTROL_MANAGER 1/29/2014 1:04:53 PM 5456 (0x1550)
    Initialization still in progress. SMS_MP_CONTROL_MANAGER 1/29/2014 1:04:53 PM 5456 (0x1550)
    SSL is not enabled. SMS_MP_CONTROL_MANAGER 1/29/2014 1:05:23 PM 5456 (0x1550)
    Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 1/29/2014 1:05:23 PM 5456 (0x1550)
    Sent summary record of SMS Management Point on [“Display=\\MW01-SCCM2.MWA.LOCAL\”]MSWNET:[“SMS_SITE=S01”]\\MW01-SCCM2.MWA.LOCAL\ to \\MW01-SCCM2.MWA.LOCA

  6. January 31, 2014 at 1:51 pm

    [—– STARTUP —–] ClientIDManagerStartup 1/22/2014 3:00:05 PM 4984 (0x1378)
    HTTP is selected for Client. The current state is 0. ClientIDManagerStartup 1/22/2014 3:00:05 PM 4984 (0x1378)
    Generated a new Signing certificate ClientIDManagerStartup 1/22/2014 3:00:08 PM 4984 (0x1378)
    Generated a new Encryption certificate ClientIDManagerStartup 1/22/2014 3:00:08 PM 4984 (0x1378)
    Evaluated SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000630034002000310038002000390063002000390066002000390030002000390037002D0065006500200032003300200061006600200036003100200066003100200030006100200061003600200064006100 ClientIDManagerStartup 1/22/2014 3:00:16 PM 5024 (0x13A0)
    SMBIOS unchanged ClientIDManagerStartup 1/22/2014 3:00:16 PM 5024 (0x13A0)
    SID unchanged ClientIDManagerStartup 1/22/2014 3:00:16 PM 5024 (0x13A0)
    HWID unchanged ClientIDManagerStartup 1/22/2014 3:00:19 PM 5024 (0x13A0)
    Generating a new SMSID GUID:69EE1D43-78BF-4551-BD15-67ECC83E3E89 on a clientless install at time 01/22/2014 21:00:19. ClientIDManagerStartup 1/22/2014 3:00:19 PM 5024 (0x13A0)
    Raising pending event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SMS_RemoteClient_ClientIdUpdated
    {
    ClientID = “GUID:69EE1D43-78BF-4551-BD15-67ECC83E3E89”;
    DateTime = “20140122210019.113000+000”;
    MachineName = “MW01-SCCM2”;
    NewClientId = “GUID:69EE1D43-78BF-4551-BD15-67ECC83E3E89”;
    PreviousClientId = “”;
    ProcessID = 4772;
    ThreadID = 5024;
    };
    ClientIDManagerStartup 1/22/2014 3:00:19 PM 5024 (0x13A0)
    GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE ClientIDManagerStartup 1/22/2014 3:00:19 PM 5024 (0x13A0)
    Computed HardwareID=2:D54CD4B9AEEE3DCF3769BEE94B0A77BF9A2DBD52
    Win32_SystemEnclosure.SerialNumber=
    Win32_SystemEnclosure.SMBIOSAssetTag=
    Win32_BaseBoard.SerialNumber=None
    Win32_BIOS.SerialNumber=VMware-56 4d c4 18 9c 9f 90 97-ee 23 af 61 f1 0a a6 da
    Win32_NetworkAdapterConfiguration.MACAddress=00:50:56:85:0D:EE ClientIDManagerStartup 1/22/2014 3:00:19 PM 5024 (0x13A0)
    Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
    HardwareID1=2:D54CD4B9AEEE3DCF3769BEE94B0A77BF9A2DBD52
    HardwareID2=DAF80600010000F4 ClientIDManagerStartup 1/22/2014 3:00:19 PM 5024 (0x13A0)
    [—– SHUTDOWN —–] ClientIDManagerStartup 1/23/2014 8:30:09 AM 4984 (0x1378)
    [—– STARTUP —–] ClientIDManagerStartup 1/23/2014 8:32:54 AM 1196 (0x04AC)
    HTTP is selected for Client. The current state is 0. ClientIDManagerStartup 1/23/2014 8:32:54 AM 1196 (0x04AC)
    Read SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000630034002000310038002000390063002000390066002000390030002000390037002D0065006500200032003300200061006600200036003100200066003100200030006100200061003600200064006100 ClientIDManagerStartup 1/23/2014 8:32:55 AM 36 (0x0024)
    Evaluated SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000630034002000310038002000390063002000390066002000390030002000390037002D0065006500200032003300200061006600200036003100200066003100200030006100200061003600200064006100 ClientIDManagerStartup 1/23/2014 8:32:55 AM 36 (0x0024)
    No SMBIOS Changed ClientIDManagerStartup 1/23/2014 8:32:55 AM 36 (0x0024)
    SMBIOS unchanged ClientIDManagerStartup 1/23/2014 8:32:55 AM 36 (0x0024)
    SID unchanged ClientIDManagerStartup 1/23/2014 8:32:55 AM 36 (0x0024)
    HWID unchanged ClientIDManagerStartup 1/23/2014 8:32:57 AM 36 (0x0024)
    GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE ClientIDManagerStartup 1/23/2014 8:32:57 AM 36 (0x0024)
    Computed HardwareID=2:D54CD4B9AEEE3DCF3769BEE94B0A77BF9A2DBD52
    Win32_SystemEnclosure.SerialNumber=
    Win32_SystemEnclosure.SMBIOSAssetTag=
    Win32_BaseBoard.SerialNumber=None
    Win32_BIOS.SerialNumber=VMware-56 4d c4 18 9c 9f 90 97-ee 23 af 61 f1 0a a6 da
    Win32_NetworkAdapterConfiguration.MACAddress=00:50:56:85:0D:EE ClientIDManagerStartup 1/23/2014 8:32:57 AM 36 (0x0024)
    Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
    HardwareID1=2:D54CD4B9AEEE3DCF3769BEE94B0A77BF9A2DBD52
    HardwareID2=DAF80600010000F4 ClientIDManagerStartup 1/23/2014 8:32:57 AM 36 (0x0024)
    [—– SHUTDOWN —–] ClientIDManagerStartup 1/23/2014 9:11:38 AM 1196 (0x04AC)
    [—– STARTUP —–] ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Running query ‘SELECT * FROM CCM_Service_HostedApplication WHERE Type=”Server”‘ against namespace: ‘\\MW01-SCCM2\ROOT\ccm\Policy\Machine’ ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    CCMExec is currently hosting a server application. ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    PopulateRegistrationHint: Client has an SMSID, certificates, and has never set the hint in the current version, setting the hint. ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Retrieved Certificate ID from registry successfully ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    PopulateRegistrationHint: Using the Certificate selected by the current version of SCCM to set the hint. ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Client is set to use HTTPS when available. The current state is 480. ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    PopulateRegistrationHint: Registration hint successfully populated. ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Deleted Certificate ID from registry successfully ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Begin searching client certificates based on Certificate Issuers ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Completed searching client certificates based on Certificate Issuers ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Begin to select client certificate ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Begin validation of Certificate [Thumbprint 2AF9E883770A4F62B372DD5701F26B46C96BCF42] issued to ‘MW01-SCCM2.MWA.LOCAL’ ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Completed validation of Certificate [Thumbprint 2AF9E883770A4F62B372DD5701F26B46C96BCF42] issued to ‘MW01-SCCM2.MWA.LOCAL’ ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Raising event:
    instance of CCM_ServiceHost_CertRetrieval_Status
    {
    ClientID = “GUID:69EE1D43-78BF-4551-BD15-67ECC83E3E89”;
    DateTime = “20140123152427.111000+000”;
    HRESULT = “0x800b0110”;
    ProcessID = 5464;
    ThreadID = 3820;
    };
    ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Failed to submit event to the Status Agent. Attempting to create pending event. ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Raising pending event:
    instance of CCM_ServiceHost_CertRetrieval_Status
    {
    ClientID = “GUID:69EE1D43-78BF-4551-BD15-67ECC83E3E89”;
    DateTime = “20140123152427.111000+000”;
    HRESULT = “0x800b0110”;
    ProcessID = 5464;
    ThreadID = 3820;
    };
    ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Unable to find PKI Certificate matching SCCM certificate selection criteria. 0x800b0110 ClientIDManagerStartup 1/23/2014 9:24:27 AM 3820 (0x0EEC)
    Initializing registration renewal for potential PKI issued certificate changes. ClientIDManagerStartup 1/23/2014 9:24:37 AM 6064 (0x17B0)
    Succesfully intialized registration renewal. ClientIDManagerStartup 1/23/2014 9:24:37 AM 6064 (0x17B0)
    [RegTask] – On co-located client and site role. Posting async registration task. ClientIDManagerStartup 1/23/2014 9:24:37 AM 6064 (0x17B0)
    [RegTask] – Co-located with site role. Waiting for full service startup before registering. ClientIDManagerStartup 1/23/2014 9:24:37 AM 3208 (0x0C88)
    Read SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000630034002000310038002000390063002000390066002000390030002000390037002D0065006500200032003300200061006600200036003100200066003100200030006100200061003600200064006100 ClientIDManagerStartup 1/23/2014 9:24:38 AM 6064 (0x17B0)
    Evaluated SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000630034002000310038002000390063002000390066002000390030002000390037002D0065006500200032003300200061006600200036003100200066003100200030006100200061003600200064006100 ClientIDManagerStartup 1/23/2014 9:24:38 AM 6064 (0x17B0)
    No SMBIOS Changed ClientIDManagerStartup 1/23/2014 9:24:38 AM 6064 (0x17B0)
    SMBIOS unchanged ClientIDManagerStartup 1/23/2014 9:24:38 AM 6064 (0x17B0)
    SID unchanged ClientIDManagerStartup 1/23/2014 9:24:38 AM 6064 (0x17B0)
    HWID unchanged ClientIDManagerStartup 1/23/2014 9:24:40 AM 6064 (0x17B0)
    GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE ClientIDManagerStartup 1/23/2014 9:24:40 AM 6064 (0x17B0)
    Computed HardwareID=2:D54CD4B9AEEE3DCF3769BEE94B0A77BF9A2DBD52
    Win32_SystemEnclosure.SerialNumber=
    Win32_SystemEnclosure.SMBIOSAssetTag=
    Win32_BaseBoard.SerialNumber=None
    Win32_BIOS.SerialNumber=VMware-56 4d c4 18 9c 9f 90 97-ee 23 af 61 f1 0a a6 da
    Win32_NetworkAdapterConfiguration.MACAddress=00:50:56:85:0D:EE ClientIDManagerStartup 1/23/2014 9:24:41 AM 6064 (0x17B0)
    Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
    HardwareID1=2:D54CD4B9AEEE3DCF3769BEE94B0A77BF9A2DBD52
    HardwareID2=DAF80600010000F4 ClientIDManagerStartup 1/23/2014 9:24:41 AM 6064 (0x17B0)
    RenewalTask: Executing renewal task. ClientIDManagerStartup 1/23/2014 9:24:42 AM 6064 (0x17B0)
    Begin searching client certificates based on Certificate Issuers ClientIDManagerStartup 1/23/2014 9:24:42 AM 6064 (0x17B0)
    Completed searching client certificates based on Certificate Issuers ClientIDManagerStartup 1/23/2014 9:24:42 AM 6064 (0x17B0)
    Begin to select client certificate ClientIDManagerStartup 1/23/2014 9:24:42 AM 6064 (0x17B0)
    Begin validation of Certificate [Thumbprint 2AF9E883770A4F62B372DD5701F26B46C96BCF42] issued to ‘MW01-SCCM2.MWA.LOCAL’ ClientIDManagerStartup 1/23/2014 9:24:42 AM 6064 (0x17B0)
    Completed validation of Certificate [Thumbprint 2AF9E883770A4F62B372DD5701F26B46C96BCF42] issued to ‘MW01-SCCM2.MWA.LOCAL’ ClientIDManagerStartup 1/23/2014 9:24:42 AM 6064 (0x17B0)
    Raising event:
    instance of CCM_ServiceHost_CertRetrieval_Status
    {
    ClientID = “GUID:69EE1D43-78BF-4551-BD15-67ECC83E3E89”;
    DateTime = “20140123152442.822000+000”;
    HRESULT = “0x800b0110″;
    ProcessID = 5464;
    ThreadID = 6064;
    };
    ClientIDManagerStartup 1/23/2014 9:24:42 AM 6064 (0x17B0)
    Unable to find PKI Certificate matching SCCM certificate selection criteria. 0x800b0110 ClientIDManagerStartup 1/23/2014 9:24:42 AM 6064 (0x17B0)
    RenewalTask: Certificate has changed, initiating a renewal. ClientIDManagerStartup 1/23/2014 9:24:42 AM 6064 (0x17B0)
    Aborting any pending registration. ClientIDManagerStartup 1/23/2014 9:24:42 AM 6064 (0x17B0)
    Re-registration/renewal initiated. Restarting the service. ClientIDManagerStartup 1/23/2014 9:24:42 AM 6064 (0x17B0)
    RegEndPoint: Event notification: CCM_RemoteClient_Reassigned ClientIDManagerStartup 1/23/2014 9:24:42 AM 5988 (0x1764)
    RegEndPoint: Received notification for site assignment change from ” to ‘S01’. ClientIDManagerStartup 1/23/2014 9:24:42 AM 5988 (0x1764)
    [—– SHUTDOWN —–] ClientIDManagerStartup 1/23/2014 9:24:44 AM 3820 (0x0EEC)
    [—– STARTUP —–] ClientIDManagerStartup 1/23/2014 9:24:45 AM 6232 (0x1858)
    Client is set to use HTTPS when available. The current state is 480. ClientIDManagerStartup 1/23/2014 9:24:45 AM 6232 (0x1858)
    Begin searching client certificates based on Certificate Issuers ClientIDManagerStartup 1/23/2014 9:24:45 AM 6232 (0x1858)
    Completed searching client certificates based on Certificate Issuers ClientIDManagerStartup 1/23/2014 9:24:45 AM 6232 (0x1858)
    Begin to select client certificate ClientIDManagerStartup 1/23/2014 9:24:45 AM 6232 (0x1858)
    Begin validation of Certificate [Thumbprint 2AF9E883770A4F62B372DD5701F26B46C96BCF42] issued to ‘MW01-SCCM2.MWA.LOCAL’ ClientIDManagerStartup 1/23/2014 9:24:45 AM 6232 (0x1858)
    Completed validation of Certificate [Thumbprint 2AF9E883770A4F62B372DD5701F26B46C96BCF42] issued to ‘MW01-SCCM2.MWA.LOCAL’ ClientIDManagerStartup 1/23/2014 9:24:45 AM 6232 (0x1858)
    Raising event:
    instance of CCM_ServiceHost_CertRetrieval_Status
    {
    ClientID = “GUID:69EE1D43-78BF-4551-BD15-67ECC83E3E89”;
    DateTime = “20140123152445.564000+000”;
    HRESULT = “0x800b0110”;
    ProcessID = 6216;
    ThreadID = 6232;
    };
    ClientIDManagerStartup 1/23/2014 9:24:45 AM 6232 (0x1858)
    Failed to submit event to the Status Agent. Attempting to create pending event. ClientIDManagerStartup 1/23/2014 9:24:45 AM 6232 (0x1858)
    Raising pending event:
    instance of CCM_ServiceHost_CertRetrieval_Status
    {
    ClientID = “GUID:69EE1D43-78BF-4551-BD15-67ECC83E3E89”;
    DateTime = “20140123152445.564000+000”;
    HRESULT = “0x800b0110”;
    ProcessID = 6216;
    ThreadID = 6232;
    };
    ClientIDManagerStartup 1/23/2014 9:24:45 AM 6232 (0x1858)
    Unable to find PKI Certificate matching SCCM certificate selection criteria. 0x800b0110 ClientIDManagerStartup 1/23/2014 9:24:45 AM 6232 (0x1858)
    Initializing registration renewal for potential PKI issued certificate changes. ClientIDManagerStartup 1/23/2014 9:24:47 AM 6276 (0x1884)
    Succesfully intialized registration renewal. ClientIDManagerStartup 1/23/2014 9:24:47 AM 6276 (0x1884)
    [RegTask] – On co-located client and site role. Posting async registration task. ClientIDManagerStartup 1/23/2014 9:24:47 AM 6276 (0x1884)
    [RegTask] – Co-located with site role. Waiting for full service startup before registering. ClientIDManagerStartup 1/23/2014 9:24:47 AM 6304 (0x18A0)
    Read SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000630034002000310038002000390063002000390066002000390030002000390037002D0065006500200032003300200061006600200036003100200066003100200030006100200061003600200064006100 ClientIDManagerStartup 1/23/2014 9:24:48 AM 6276 (0x1884)
    Evaluated SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000630034002000310038002000390063002000390066002000390030002000390037002D0065006500200032003300200061006600200036003100200066003100200030006100200061003600200064006100 ClientIDManagerStartup 1/23/2014 9:24:48 AM 6276 (0x1884)
    No SMBIOS Changed ClientIDManagerStartup 1/23/2014 9:24:48 AM 6276 (0x1884)
    SMBIOS unchanged ClientIDManagerStartup 1/23/2014 9:24:48 AM 6276 (0x1884)
    SID unchanged ClientIDManagerStartup 1/23/2014 9:24:48 AM 6276 (0x1884)
    HWID unchanged ClientIDManagerStartup 1/23/2014 9:24:50 AM 6276 (0x1884)
    GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE ClientIDManagerStartup 1/23/2014 9:24:50 AM 6276 (0x1884)
    Computed HardwareID=2:D54CD4B9AEEE3DCF3769BEE94B0A77BF9A2DBD52
    Win32_SystemEnclosure.SerialNumber=
    Win32_SystemEnclosure.SMBIOSAssetTag=
    Win32_BaseBoard.SerialNumber=None
    Win32_BIOS.SerialNumber=VMware-56 4d c4 18 9c 9f 90 97-ee 23 af 61 f1 0a a6 da
    Win32_NetworkAdapterConfiguration.MACAddress=00:50:56:85:0D:EE ClientIDManagerStartup 1/23/2014 9:24:50 AM 6276 (0x1884)
    Here is the ClientIDmanagerstartup.log—-

    Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
    HardwareID1=2:D54CD4B9AEEE3DCF3769BEE94B0A77BF9A2DBD52
    HardwareID2=DAF80600010000F4 ClientIDManagerStartup 1/23/2014 9:24:50 AM 6276 (0x1884)
    [RegTask] – Service has started, continuing registration. ClientIDManagerStartup 1/23/2014 9:25:03 AM 6304 (0x18A0)
    Read SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000630034002000310038002000390063002000390066002000390030002000390037002D0065006500200032003300200061006600200036003100200066003100200030006100200061003600200064006100 ClientIDManagerStartup 1/23/2014 9:25:03 AM 6304 (0x18A0)
    Evaluated SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000630034002000310038002000390063002000390066002000390030002000390037002D0065006500200032003300200061006600200036003100200066003100200030006100200061003600200064006100 ClientIDManagerStartup 1/23/2014 9:25:03 AM 6304 (0x18A0)
    No SMBIOS Changed ClientIDManagerStartup 1/23/2014 9:25:03 AM 6304 (0x18A0)
    SMBIOS unchanged ClientIDManagerStartup 1/23/2014 9:25:03 AM 6304 (0x18A0)
    SID unchanged ClientIDManagerStartup 1/23/2014 9:25:03 AM 6304 (0x18A0)
    HWID unchanged ClientIDManagerStartup 1/23/2014 9:25:03 AM 6304 (0x18A0)
    GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE ClientIDManagerStartup 1/23/2014 9:25:08 AM 6304 (0x18A0)
    Computed HardwareID=2:D54CD4B9AEEE3DCF3769BEE94B0A77BF9A2DBD52
    Win32_SystemEnclosure.SerialNumber=
    Win32_SystemEnclosure.SMBIOSAssetTag=<em

  7. January 31, 2014 at 2:46 pm

    Hi Steve,

    Just to be sure, please, try this URL “http://sccmservername/sms_mp/.sms_aut?mplist” on your browser. If the returned code is 500 and your Management Point Role is installed on Windows 2008 R2 or Windows 2008, please try this : “cd /d %windir%\Microsoft.Net\Framework64\v4*
    aspnet_regiis –i –enable” , using elevated privilges when lauching your cmd console.

    Let me know if the issue is solved please.

  8. January 31, 2014 at 2:52 pm

    I’m using Server 2012 for this.. and just received the 500 error.

  9. milo
    November 27, 2014 at 1:09 pm

    Thx man, that was very helpfull

  10. February 2, 2015 at 2:33 am

    Thank you so much! The amount of time I wasted trying to work out what was going on with this…

  11. Jesper
    October 15, 2015 at 1:27 pm

    Fantastic – you have saved one more life 🙂
    Thank you!

    • October 16, 2015 at 9:46 pm

      Hi Jesper, so happy for you!

  12. Harro
    June 1, 2016 at 7:12 am

    Thanks for your post which helped me in solving my problem.

    While I had the same error, the cause was slightly different:
    I removed WindowsFeature WSUS after deciding it was no longer needed, but I assume the removal had failed. IIS gave, after a while, status error 500 and clients were marked inactive.
    Re-adding the WSUS feature solved my problem:
    Add-WindowsFeature UpdateServices -IncludeManagementTools

  13. upendar
    June 17, 2016 at 9:43 am

    Hi Ramzi,

    I done the above mentioned settings, repairing mp , but still am getting same error.

    Regards,
    upendar.

  14. June 17, 2016 at 9:45 am

    Hi Ramzi,

    Still am getting the same error. Mp repairing has been done. still getting 0x87d00231 error.

    In client went to sleep mode for 1920 seconds.

    Regards,
    Upendar.

  15. June 18, 2016 at 5:02 pm

    Hi upendar,

    After repairing your MP, are you able to join new sccm clients to your MP? If it s true, for the existing clients, you need some time to see the results. So try to install a new client to see if it s fixed.

    Hope it helps.

    Ramzi.

  16. June 22, 2016 at 10:05 am

    Hi Ramzi,

    After repairing the MP, still am unable to join the new clients to MP. Getting same error
    0x87d00231

    Regards,
    upendar.

  17. June 23, 2016 at 6:19 pm

    Hi upendar,

    What about IIS logs? Are all your MP modules (like authentication) ok? Please check your sscm logs, you can find interesting things. Now if there is no solution to repair the MP, you have to install a new one and delete the faulted. All your clients will be joined automatically to the new MP. Generally, as the MP is important, it is advised to have more than one MP to ensure the availability of the sccm. The load balancing is supported natively by sccm.

  18. SCCM
    October 15, 2016 at 12:41 pm

    Ramzibot, I repaired the MP as mentioned in your instructions, my clients are still not healthy.

    [RegTask] – Client is not registered. Sending registration request for GUID:0F4169CB-F886-470C-A044-998AB22CDEE7 …]LOG]!>
    <time="12:40:14.211

    LocationServices Log

    No Location Reply received from
    Failed to create Location Request Message body

    CCMMessaging Log

    Failed in WinHttpSendRequest API, ErrorCode = 0x2efd

    BGBServer log on MP

    ERROR: Error in FirewallDetection. Exception: Creating an instance of the COM component with CLSID {304CE942-6E39-40D8-943A-B913C40C9CD4} from the IClassFactory failed due to the following error: 800706d9 There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9).

    ERROR: Exception: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

    • April 7, 2017 at 1:20 am

      Hi SCCM, Sorry to be late. It seems that you have a firewall or proxy problem. My question is, do you have a proxy?(please add MP addresses as exceptions). Are you able to retrieve MPs from an unhealthy client?

  19. October 24, 2016 at 2:39 pm

    Hi
    I am having the same problem with two servers installation is successfull but it’s is not able to send registration request, error as below. Whenever I am installing client on any other server as well as workstations then client is able to register howevber the problem persists only for two servers. Tried un-installing and re-installing and tried deleteing and re-adding the certificate but no luck.

    [RegTask] – Client is not registered. Sending registration request for GUID:B2DC444D-081B-4E9A-83B4-CA8615C6031F … ClientIDManagerStartup 24/10/2016 14:47:39 3864 (0x0F18)
    RegTask: Failed to send registration request message. Error: 0x87d00231 ClientIDManagerStartup 24/10/2016 14:48:01 3864 (0x0F18)
    RegTask: Failed to send registration request. Error: 0x87d00231 ClientIDManagerStartup 24/10/2016 14:48:01 3864 (0x0F18)

    In this case I don’t think the problem is for MP.Could you please suggest anything more.

    Thanks in advance.

    • April 7, 2017 at 1:22 am

      Hi biswalb,

      Sorry to be late!

      Are you using https endpoint?

      Regards.

      • June 20, 2017 at 5:25 pm

        Hi,
        Thanks for your reply. This issue has been resolved by installing latest (CU3) sccm client.(Suggested by MS)

  1. June 19, 2016 at 11:34 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: