locked
IBCM Clients Failure 0x87d00231 RRS feed

  • Question

  • Hi, 

    we have a SCCM 2012R2SP1CU1 Infrastructure with one Primary Site. 

    Weve set up a new IBCM (MP & DP) 

    This IBCM seems to be working. Everything should be fine with Certs and Firewall...

    BUT the Clients can't connect. I have found some Solution to my Error, but they didnt helped :( 

    Like this: https://social.technet.microsoft.com/Forums/de-DE/1df084db-fb60-4b06-bb57-306fd1b3b878/ibcm-requests-fail-with-0x87d00231?forum=configmanagergeneral


    Here are some of my Log entries

    ClientIDManagerStartup.log 

    [RegTask] - Client is already registered. Exiting.	ClientIDManagerStartup	20.11.2015 12:01:58	148 (0x0094)

    ClientLocation.log

    Unable to retrieve AD forest + domain membership. Error 0x8007054b	ClientLocation	20.11.2015 12:02:25	1808 (0x0710)
    Failed to send request to  at host internalsiteServer.dom.de, error 0x2ee7	ClientLocation	20.11.2015 12:02:25	1808 (0x0710)
    [CCMHTTP] ERROR: URL=http://internalsiteServer.dom.de, Port=80, Options=480, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED	ClientLocation	20.11.2015 12:02:25	1808 (0x0710)
    Raising event:
    instance of CCM_CcmHttp_Status
    {
    	ClientID = "GUID:6EC604D6-D5E4-49BF-A092-5E269ADBDC36";
    	DateTime = "20151120110225.323000+000";
    	HostName = "internalsiteServer.dom.de";
    	HRESULT = "0x80072ee7";
    	ProcessID = 5052;
    	StatusCode = 600;
    	ThreadID = 1808;
    };
    	ClientLocation	20.11.2015 12:02:25	1808 (0x0710)
    Successfully sent location services HTTP failure message.	ClientLocation	20.11.2015 12:02:25	1808 (0x0710)
    Error sending HEAD request. HTTP code 600, status ''	ClientLocation	20.11.2015 12:02:25	1808 (0x0710)
    Raising event:
    instance of CCM_CcmHttp_Status
    {
    	ClientID = "GUID:6EC604D6-D5E4-49BF-A092-5E269ADBDC36";
    	DateTime = "20151120110225.635000+000";
    	HostName = "cm.dom.de";
    	HRESULT = "0x00000000";
    	ProcessID = 5052;
    	StatusCode = 0;
    	ThreadID = 1808;
    };
    	ClientLocation	20.11.2015 12:02:25	1808 (0x0710)
    Domain joined client is in Internet	ClientLocation	20.11.2015 12:02:25	1808 (0x0710)
    Current internet management point is the only internet management point.	ClientLocation	20.11.2015 12:05:17	3616 (0x0E20)

    CcmMessaging.log

    Successfully sent location services HTTPS failure message.	CcmMessaging	20.11.2015 12:05:17	3376 (0x0D30)
    Post to https://cm.dom.de/ccm_system/request failed with 0x87d00231.	CcmMessaging	20.11.2015 12:05:17	1808 (0x0710)

    CcmMessaging.log ADDITION!

    [CCMHTTP] ERROR: URL=https://cm.dom.de/ccm_system/request, Port=443, Options=480, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE	CcmMessaging	20.11.2015 12:03:35	3376 (0x0D30)
    Raising event:
    instance of CCM_CcmHttp_Status
    {
    	ClientID = "GUID:6EC604D6-D5E4-49BF-A092-5E269ADBDC36";
    	DateTime = "20151120110335.997000+000";
    	HostName = "cm.dom.de";
    	HRESULT = "0x87d0027e";
    	ProcessID = 5052;
    	StatusCode = 403;
    	ThreadID = 3376;
    };
    	CcmMessaging	20.11.2015 12:03:35	3376 (0x0D30)
    Successfully sent security settings refresh message.	CcmMessaging	20.11.2015 12:03:36	3376 (0x0D30)
    Successfully sent location services HTTPS failure message.	CcmMessaging	20.11.2015 12:03:36	3376 (0x0D30)
    Post to https://cm.dom.de/ccm_system/request failed with 0x87d00231.	CcmMessaging	20.11.2015 12:03:36	3376 (0x0D30)

    I don't know where to look or change settings. 

    Any ideas? 



    • Edited by SeSei Friday, November 20, 2015 12:27 PM
    Friday, November 20, 2015 11:20 AM

Answers

  • 0x87d00231 = "Transient Error".

    This means, in this context, that ConfigMgr has no idea what's wrong, just that the traffic being sent by the client is not being properly returned.

    Have you checked the IIS logs on the Internet MP to see if the traffic is making it? I would say that it's not which means your reverse proxy is not set up to properly forward traffic on 443 to 443 on your Internet facing MP.


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

    • Marked as answer by SeSei Friday, November 20, 2015 2:34 PM
    Friday, November 20, 2015 2:24 PM

All replies

  • Based on the name you've changed in the log files, it seems to be connecting to the internal name of your management point, which, of course, failes with ERROR_WINHTTP_NAME_NOT_RESOLVED. Make sure that you've configured the correct Internet FQDN in the site system.

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Friday, November 20, 2015 11:41 AM
  • Yep,

    the Server in the 3rd line of the ClientLocation.log and in the block below ist the Internal Primary Site Server. 

    In the second block is the Correct FQDN (Public DNS name from the IBCM)

    These are my Site System Properties:

    http://1drv.ms/1QxZ9Cy

    CcmMessaging.log ADDITION!

    [CCMHTTP] ERROR: URL=https://cm.dom.de/ccm_system/request, Port=443, Options=480, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE	CcmMessaging	20.11.2015 12:03:35	3376 (0x0D30)
    Raising event:
    instance of CCM_CcmHttp_Status
    {
    	ClientID = "GUID:6EC604D6-D5E4-49BF-A092-5E269ADBDC36";
    	DateTime = "20151120110335.997000+000";
    	HostName = "cm.dom.de";
    	HRESULT = "0x87d0027e";
    	ProcessID = 5052;
    	StatusCode = 403;
    	ThreadID = 3376;
    };
    	CcmMessaging	20.11.2015 12:03:35	3376 (0x0D30)
    Successfully sent security settings refresh message.	CcmMessaging	20.11.2015 12:03:36	3376 (0x0D30)
    Successfully sent location services HTTPS failure message.	CcmMessaging	20.11.2015 12:03:36	3376 (0x0D30)
    Post to https://cm.dom.de/ccm_system/request failed with 0x87d00231.	CcmMessaging	20.11.2015 12:03:36	3376 (0x0D30)



    • Edited by SeSei Friday, November 20, 2015 12:26 PM
    Friday, November 20, 2015 12:08 PM
  • Hi,

    From the client system, try to ping Internet FQDN and check which IP address are returning ?


    Kannan.CS | http://kannancs.wix.com/blog | Please remember to click “Mark as Answer” on the post that helps you. This can be beneficial to other community members reading the thread.

    Friday, November 20, 2015 1:06 PM
  • I am getting the IP from our Firewall, which is the reversed Proxy for the IBCM. 
    Friday, November 20, 2015 1:10 PM
  • its not public IP right?


    Kannan.CS | http://kannancs.wix.com/blog | Please remember to click “Mark as Answer” on the post that helps you. This can be beneficial to other community members reading the thread.

    Friday, November 20, 2015 1:39 PM
  • The Firewall IP is public. The IBCM Server doesnt have a public IP. 

    Friday, November 20, 2015 1:42 PM
  • Hi from yoru client,

    are you able access the MP IIS server ?

    http://internalsiteServer.dom.de


    Kannan.CS | http://kannancs.wix.com/blog | Please remember to click “Mark as Answer” on the post that helps you. This can be beneficial to other community members reading the thread.

    Friday, November 20, 2015 2:08 PM
  • 0x87d00231 = "Transient Error".

    This means, in this context, that ConfigMgr has no idea what's wrong, just that the traffic being sent by the client is not being properly returned.

    Have you checked the IIS logs on the Internet MP to see if the traffic is making it? I would say that it's not which means your reverse proxy is not set up to properly forward traffic on 443 to 443 on your Internet facing MP.


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

    • Marked as answer by SeSei Friday, November 20, 2015 2:34 PM
    Friday, November 20, 2015 2:24 PM
  • NO, because thats my internal Primary Site Server. 

    I just want to connect to my IBCM site server (cm.dom.de)

    Friday, November 20, 2015 2:32 PM
  • We have taken the server temporary in the DMZ without reversed proxy... AND NOW IT WORKS! 

    There has to be any failure at the firewall. So i have to check this! Because the IBCM should not be in the DMZ

    Thanks to all, have a nice weekend!! 
    • Edited by SeSei Friday, November 20, 2015 3:39 PM
    Friday, November 20, 2015 2:34 PM