locked
Failed to send registration request message. Error: 0x87d00231 RRS feed

  • Question

  • Hey,

    I am facing with a very interesting issue in my environment.
    Some of my clients cannot register themselves to my ManagementPoints (I have 3 of them - all with the same failure).

    The error I am facing in ClientIDManagerStartup & CcmMessaging log is the following:

    RegTask] - Client is not registered. Sending registration request for GUID:45bd46f4-443b-4a1e-b461-7c6fce3763f8 ...	ClientIDManagerStartup	10/21/2015 3:17:27 PM	5028 (0x13A4)
    Using Local System for outbound machine authentication	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    Detecting if client is on the internet.	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    Client is not set to use any webproxy.	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    POST: Host=sccm04.domain.my, Path=/ccm_system_windowsauth/request, Port=80, Protocol=http, Flags=521, Options=224	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    Resending the request by setting the credentials on getting an unauthorized response.	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    Setting autologon policy for integrated auth request.	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    [CCMHTTP] ERROR: URL=http://sccm04.domain.my/ccm_system_windowsauth/request, Port=80, Options=224, Code=12030, Text=ERROR_WINHTTP_CONNECTION_ERROR	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    [CCMHTTP] ERROR INFO: StatusCode=600 StatusText=	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    Raising event:
    instance of CCM_CcmHttp_Status
    {
    	ClientID = "GUID:45bd46f4-443b-4a1e-b461-7c6fce3763f8";
    	DateTime = "20151021131727.763000+000";
    	HostName = "sccm04.domain.my";
    	HRESULT = "0x80072efe";
    	ProcessID = 4932;
    	StatusCode = 600;
    	ThreadID = 5028;
    };
    	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    Successfully submitted event to the Status Agent.	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    Sending location services HTTP failure message.	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    Successfully sent location services HTTP failure message.	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    Post to http://sccm04.domain.my/ccm_system_windowsauth/request failed with 0x87d00231.	CcmMessaging	10/21/2015 3:17:27 PM	5028 (0x13A4)
    RegTask: Failed to send registration request message. Error: 0x87d00231	ClientIDManagerStartup	10/21/2015 3:17:27 PM	5028 (0x13A4)
    RegTask: Failed to send registration request. Error: 0x87d00231	ClientIDManagerStartup	10/21/2015 3:17:27 PM	5028 (0x13A4)
    [RegTask] - Sleeping for 60 seconds ...	ClientIDManagerStartup	10/21/2015 3:17:27 PM	5028 (0x13A4)

    I tested with 4 clients.
    One of these 4 clients unexpectly was able to register itself.
    I do not know what caused this but from any second to the next it worked. - Other 3 are still stuck.
    Here a screenshot of it (sorry for being that small - just zoom in - I do not have the original logs further):

    I in IIS logs and found corresponding entries to the requests.
    (So connection seems to be okay).

    Currently it looks to me like the client cannot recieve the kerberos certificate for MP authentication.
    But I do not know where to have a look if this works or throws an error.

    Does anyone know where to find logs / eventlog entries for the kerberos request or has any other ideas?

    Thanks in advance.



    • Edited by MK-Maddin Wednesday, October 21, 2015 2:06 PM
    Wednesday, October 21, 2015 1:50 PM

Answers

  • 0x80072efe = "The connection with the server was terminated abnormally"

    This basically equates to something somewhere outside of ConfigMgr's control is preventing the full communication from happening. What that something is is something you need to review logs to determine (as mentioned by Torsten) and/or work with the network team to see where the traffic stops at.

    Also, Kerberos doesn't use certs so not sure what evidence is leading you to believe that. It's certainly possible that there's an authentication issue here though but that's something you will have to review on your domain controllers.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by MK-Maddin Wednesday, October 21, 2015 4:48 PM
    Wednesday, October 21, 2015 2:28 PM

All replies

  • The 12030 error caused it somehow. You would have to examine a combination of various logs to get an idea what was happening (CLientIDManagerStartup.log on the client, IIS logs, mpcontrol.log and MP_ClientRegistration.log on the MP).

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

    Wednesday, October 21, 2015 2:13 PM
  • 0x80072efe = "The connection with the server was terminated abnormally"

    This basically equates to something somewhere outside of ConfigMgr's control is preventing the full communication from happening. What that something is is something you need to review logs to determine (as mentioned by Torsten) and/or work with the network team to see where the traffic stops at.

    Also, Kerberos doesn't use certs so not sure what evidence is leading you to believe that. It's certainly possible that there's an authentication issue here though but that's something you will have to review on your domain controllers.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by MK-Maddin Wednesday, October 21, 2015 4:48 PM
    Wednesday, October 21, 2015 2:28 PM
  • Hey thanks for reply.
    The ClientIDManagerStatup.log I already had a look at.
    The IIS logs seem very confused and not very useful to me (anything I can see is that the client seemed to perform the request and the request was successful on MP received)
    I cannot find MP_ClientRegistration.log on my management point - probably you mean "MP_RegistrationManager.log" ?

    In mpcontrol.log I cannot find something that could fit into the request sent..
    (From my point of view it seems like there is something stucking in HTTP traffic. - Not SCCM specific, so nothing in SCCM specific logs..)

    Wednesday, October 21, 2015 2:32 PM
  • Thanks for help.
    I sit together with out network guys and we were able to find out that the problem was related to HTTP header containing information that was interpreted as blocked content.

    Now everything works again :)

    • Proposed as answer by TorstenMMVP Wednesday, October 21, 2015 5:25 PM
    Wednesday, October 21, 2015 4:51 PM
  • We see this only on clients with Windows Server 2008.  Any OSs 2008 R2 and above do not experience this issue.  If I reinstall the ConfigMgr client on the affected server, the communication messages clear up for several days or even a few weeks, but then return eventually.  Software updates work fine, it's that status messages about deployments, etc do not get reported back to the management points.  Most of these servers will be retired soon so I don't want to worry about it too much, but it would be helpful to resolve.  We only have 5 2008 servers left in our environment and 3 will be gone by the end of the month.
    Friday, February 17, 2017 3:54 PM