none
Failed to open namespace '\\.\root\ccm\policy\S_1_1_0\RequestedConfig'. Error 0x8004100e RRS feed

  • Question

  • Hi

    Recently I migrated SCCM to a new server. I have about 2000 clients and 80% work ok. But I got like 300 PC with problems. When I go to control panel -> conf manager -> Actions, I see only two actions "download computer policy" and "download user policy". From the console I see these computers with the question mark on the icon columns.

    Checking the logs I see the errors  below on "policyEvaluator.log":

    Failed to open namespace '\\.\root\ccm\policy\S_1_1_0\RequestedConfig'. Error 0x8004100e

    Failed to initialize global objects. Error 0x8004100e

    In "PolicyAgentProvider.log" I see that the agent creates a namespace, but not the one mentioned before:

    <![LOG[Creating S_1_5_21_414860862_367930111_1963001494_263184\RequestedConfig]LOG]!><time="17:02:20.669-60" date="03-19-2020" component="PolicyAgentProvider" context="" type="1" thread="15308" file="replicationeventconsumer.cpp:752">
    <![LOG[Creating S_1_5_21_414860862_367930111_1963001494_263184\ActualConfig]LOG]!><time="17:02:20.794-60" date="03-19-2020" component="PolicyAgentProvider" context="" type="1" thread="15308" file="replicationeventconsumer.cpp:765">
    <![LOG[Creating S_1_5_21_414860862_367930111_1963001494_263184]LOG]!><time="17:02:20.919-60" date="03-19-2020" component="PolicyAgentProvider" context="" type="1" thread="15308" file="replicationeventconsumer.cpp:781">
    <![LOG[Successfully initialized namespace 'S_1_5_21_414860862_367930111_1963001494_263184']LOG]!><time="17:02:21.060-60" date="03-19-2020" component="PolicyAgentProvider" context="" type="1" thread="15308" file="replicationeventconsumer.cpp:905">
    <![LOG[**********>> ENTERING: InitiatePolicyUpdateThread]LOG]!><time="17:02:21.060-60" date="03-19-2020" component="PolicyAgentProvider" context="" type="1" thread="20976" file="replicationeventconsumer.cpp:177">
    <![LOG[**********>> Namespace = \\.\ROOT\CCM\Policy\S_1_5_21_414860862_367930111_1963001494_263184]LOG]!><time="17:02:21.060-60" date="03-19-2020" component="PolicyAgentProvider" context="" type="1" thread="20976" file="replicationeventconsumer.cpp:178">
    <![LOG[**********>> Initializing COM]LOG]!><time="17:02:21.060-60" date="03-19-2020" component="PolicyAgentProvider" context="" type="1" thread="20976" file="replicationeventconsumer.cpp:180">
    <![LOG[**********>> Creating CcmMessaging]LOG]!><time="17:02:21.060-60" date="03-19-2020" component="PolicyAgentProvider" context="" type="1" thread="20976" file="replicationeventconsumer.cpp:185">
    <![LOG[**********>> Creating message]LOG]!><time="17:02:21.060-60" date="03-19-2020" component="PolicyAgentProvider" context="" type="1" thread="20976" file="replicationeventconsumer.cpp:192">
    <![LOG[**********>> Sending message]LOG]!><time="17:02:21.060-60" date="03-19-2020" component="PolicyAgentProvider" context="" type="1" thread="20976" file="replicationeventconsumer.cpp:209">
    <![LOG[**********>> EXITING: InitiatePolicyUpdateThread]LOG]!><time="17:02:21.060-60" date="03-19-2020" component="PolicyAgentProvider" context="" type="1" thread="20976" file="replicationeventconsumer.cpp:235">

    During the agent installation I see lots of errors like this in "ccmsetup.log":

    Failed to connect to machine policy namespace. 0x8004100e

    I have tried to uninstall the agent, clean the registry, the wmi namespace, rebuild the WMI repository with no luck

    I can access the computer WMI repository from the SCCM server. I connect to \root\ccm\policy but if add the string "S_1_1_0" then I can verify that the namespace doesn't exist. I checked other computers working fine and they have the namespace root\ccm\policy\S_1_1_0



    • Edited by Antuanfff Thursday, March 19, 2020 4:32 PM
    Thursday, March 19, 2020 4:30 PM

All replies

  • Hi

    I would like to add that I fixed the issue in one PC by copying the folder c:\windows\system32\wbem\Repository from other computer where the agent is working fine. But I don't think this is a reasonable solution for 300 computers in a production environment...

    Thursday, March 19, 2020 4:59 PM
  • Hi,

    Firstly, I would like to check the boundaries and boundary groups are configured correctly.

    Regards,
    Allen

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, March 20, 2020 6:41 AM
  • Hi,

    Firstly, I would like to check the boundaries and boundary groups are configured correctly.

    Regards,
    Allen

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Hi

    I have one boundary for each Active Directory Site. The subnets are added to the AD Site. 

    Most of the PC with issues are in the subnet 172.16.32.0/20. But there are also many PC on the same subnet working fine. I attach the BG. It has 2 boundaries, one for the AD site and one for the subnet(I added this one because of the problems, it shouldn't be necessary though)


    • Edited by Antuanfff Friday, March 20, 2020 8:12 AM
    Friday, March 20, 2020 8:06 AM
  • Hi,

    It is recommend to use IP address range instead of IP subnet, see Jason's article:
    https://home.configmgrftw.com/ip-subnet-boundaries-are-evil/

    Regards,
    Allen

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, March 20, 2020 9:02 AM
  • Hi There ,

    Failed to connect to machine policy namespace. 0x8004100e

    Are you configured boundary correctly ? I could see you are created boundary based on Subnet , i would recommend to create boundary based on IP RANGE. Ensure file and Printer and WMI is opened on the clients to allow the client push work .

    Regards 

    Gokul


    • Edited by Gokul T.G Friday, March 20, 2020 10:01 AM
    Friday, March 20, 2020 10:00 AM
  • I created a new boundary based on IP RANGE but still the same problem:

    <![LOG[Failed to open namespace '\\.\root\ccm\policy\S_1_1_0\RequestedConfig'. Error 0x8004100e]LOG]!><time="11:14:37.363-60" date="03-20-2020" component="PolicyAgent_RequestAssignments" context="" type="3" thread="11592" file="PolicyNamespaceCache.cpp:269">
    <![LOG[Failed to initialize global objects. Error 0x8004100e]LOG]!><time="11:14:37.363-60" date="03-20-2020" component="PolicyAgent_RequestAssignments" context="" type="3" thread="11592" file="globals.cpp:164">
    <![LOG[Failed to open namespace '\\.\root\ccm\policy\S_1_1_0\RequestedConfig'. Error 0x8004100e]LOG]!><time="11:15:37.193-60" date="03-20-2020" component="PolicyAgent_RequestAssignments" context="" type="3" thread="11976" file="PolicyNamespaceCache.cpp:269">
    <![LOG[Failed to initialize global objects. Error 0x8004100e]LOG]!><time="11:15:37.193-60" date="03-20-2020" component="PolicyAgent_RequestAssignments" context="" type="3" thread="11976" file="globals.cpp:164">
    <![LOG[Assignment request will be retried later.]LOG]!><time="11:15:37.193-60" date="03-20-2020" component="PolicyAgent_RequestAssignments" context="" type="1" thread="11976" file="requestassignmentstask.cpp:1585">

     
    Friday, March 20, 2020 10:17 AM
  • Hi There ,

    Failed to connect to machine policy namespace. 0x8004100e

    Are you configured boundary correctly ? I could see you are created boundary based on Subnet , i would recommend to create boundary based on IP RANGE. Ensure file and Printer and WMI is opened on the clients to allow the client push work .

    Regards 

    Gokul


    File and printer and wmi opened ? Share the ccmsetup log too 
    Friday, March 20, 2020 11:05 AM
  • Check the ccmsetup.log and ensure file ,printer and wmi has been opened in client 
    Friday, March 20, 2020 11:06 AM
  • Hi,

    I attach ccmsetup.log.

    WMI and file printer sharing is opened. The client installs ok. Besides, I can connect to the WMI namespace from the sccm server using wbemtest

    https://1drv.ms/u/s!AoRM6vv8e9S1jqgg3n92fPG472owiA

    Friday, March 20, 2020 11:13 AM
  • Hi

    I would like to add that I fixed the issue in one PC by copying the folder c:\windows\system32\wbem\Repository from other computer where the agent is working fine. But I don't think this is a reasonable solution for 300 computers in a production environment...

    It will NOT be supported to do this. 

    How exactly are you querying WMI? On a Working compute does querying WMI work? 


    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Friday, March 20, 2020 9:02 PM
  • From ccmsetup I could see wmi error .reverify your wmi .let me know how are you checking wmi .
    Saturday, March 21, 2020 4:00 AM
  • I connect to the client computers from the SCCM server using wbemtest. And"Enum clasess" for instance.
    I can connect to the namespace "\\[hostname]\root\ccm\policy\S_1_1_0" of a working computer but I cannot connect to the same namespace of a non working computer. I get the error:

    Sunday, March 22, 2020 11:13 AM
  • Hi

    I would like to add that I fixed the issue in one PC by copying the folder c:\windows\system32\wbem\Repository from other computer where the agent is working fine. But I don't think this is a reasonable solution for 300 computers in a production environment...

    It will NOT be supported to do this. 

    How exactly are you querying WMI? On a Working compute does querying WMI work? 


    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Actually it didn't work. I got all the Actions on the Configuration Manager console "Actions" tab, but when I checked the status of the client from the SCCM console, it still had the question mark on the "Icon" column.
    Sunday, March 22, 2020 11:15 AM
  • I connect to the client computers from the SCCM server using wbemtest. And"Enum clasess" for instance.
    I can connect to the namespace "\\[hostname]\root\ccm\policy\S_1_1_0" of a working computer but I cannot connect to the same namespace of a non working computer. I get the error:

    Have you reviewed the wmi permissions on this class for both a working and non working computer?

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Sunday, March 22, 2020 12:52 PM
  • Hi

    The class is missing in a non working computer(right) On the left a working computer:

    Sunday, March 22, 2020 6:22 PM
  • Hi

    I just found out that if I re-install the agent on a working computer, the computer stops working. it gets the same problem, missing namespace and only two actions available on the Actions tab from control panel->conf manager.

    Monday, March 23, 2020 11:58 AM
  • I think you are at a point where you need to contact Microsoft Support directly. my only remaining guess is that you have a GPO or security policy that is blocking things. 

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Monday, March 23, 2020 2:04 PM
  • I think you are at a point where you need to contact Microsoft Support directly. my only remaining guess is that you have a GPO or security policy that is blocking things. 

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Yes, some GPO is my only guess. But I tried adding the Everyone group to DCOM Users and even Administratros group with no luck. 
    Monday, March 23, 2020 4:41 PM
  • wouldn't it be just easier to remove them from all GPO and confirm that the problem doesn't exist anymore? then add each GPO back one at a time until you find the GPO causing the problem? 

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Monday, March 23, 2020 5:34 PM
  • Hi

    I have been doing more tests and I found a funny thing. As I said I migrated my sccm to a new server with a new site code.

    I installed the agent from the old sccm server (I think it was SCCM CB 1803.) in a computer with the problem mentioned here. The old site has no boundaries so the agent cannot communicate with sccm. But I checked the logs and right after the SMS service starts, the namespace ccm\policy\S_1_1_0 is created. Even thouth there is no communication with the site server. Then I pushed the agent from the new server and it worked.

    So if I install the old agent first and then push the new one from the console, it fixes the problem...

    Wednesday, March 25, 2020 3:46 PM