none
CcmSetup failed with error code 0x8004100e RRS feed

  • Question

  • I have problem with installing SCCM agent for some of the server. I keep on getting this error: "CcmSetup failed with error code 0x80070643". After rebuilt the wmi respository running by the below command, I get the different error "CcmSetup failed with error code 0x8004100e". 

    winmgmt /resetrepository

    <![LOG[Running from temp downloaded folder or manifest is not newer than ccmsetup.]LOG]!><time="16:26:44.709-600" date="10-02-2018" component="ccmsetup" context="" type="1" thread="5636" file="ccmsetup.cpp:2316">
    <![LOG[CcmGetOSVersion failed with 0x8004100e]LOG]!><time="16:26:44.709-600" date="10-02-2018" component="ccmsetup" context="" type="2" thread="5636" file="util.cpp:1464">
    <![LOG[Failed to connect to policy namespace. Error 0x8004100e]LOG]!><time="16:26:44.709-600" date="10-02-2018" component="ccmsetup" context="" type="3" thread="5448" file="localpolicy.cpp:367">
    <![LOG[Failed to revoke client upgrade local policy. Error 0x8004100e]LOG]!><time="16:26:44.709-600" date="10-02-2018" component="ccmsetup" context="" type="3" thread="5448" file="localpolicy.cpp:394">
    <![LOG[Failed to get client version for sending state messages. Error 0x8004100e]LOG]!><time="16:26:44.709-600" date="10-02-2018" component="ccmsetup" context="" type="2" thread="5448" file="state.cpp:164">
    <![LOG[[] Params to send '5.0.8458.1007 Deployment Error: 0x8004100e, ']LOG]!><time="16:26:44.709-600" date="10-02-2018" component="ccmsetup" context="" type="0" thread="5448" file="state.cpp:209">
    <![LOG[A Fallback Status Point has not been specified and no client was installed.  Message with STATEID='301' will not be sent.]LOG]!><time="16:26:44.709-600" date="10-02-2018" component="ccmsetup" context="" type="1" thread="5448" file="state.cpp:240">
    <![LOG[Failed to send status 301. Error (87D00215)]LOG]!><time="16:26:44.709-600" date="10-02-2018" component="ccmsetup" context="" type="3" thread="5448" file="state.cpp:253">
    <![LOG['Configuration Manager Client Retry Task' is scheduled to run at 10/02/2018 09:26:44 PM (local) 10/02/2018 11:26:44 AM (UTC) time with arguments '  "/mp:asacmpprd01.apac.msh.local" SMSSITECODE="ASA" /RetryWinTask:1'.]LOG]!><time="16:26:44.709-600" date="10-02-2018" component="ccmsetup" context="" type="1" thread="5448" file="wintask.cpp:327">
    <![LOG[Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist.]LOG]!><time="16:26:44.709-600" date="10-02-2018" component="ccmsetup" context="" type="0" thread="5448" file="wintask.cpp:648">
    <![LOG[Successfully created task 'Configuration Manager Client Retry Task']LOG]!><time="16:26:44.864-600" date="10-02-2018" component="ccmsetup" context="" type="1" thread="5448" file="wintask.cpp:345">
    <![LOG[CcmSetup failed with error code 0x8004100e]LOG]!><time="16:26:44.864-600" date="10-02-2018" component="ccmsetup" context="" type="1" thread="5448" file="ccmsetup.cpp:10711">

    Tuesday, October 2, 2018 8:30 AM

All replies

  • > "After rebuilt the wmirespository"

    Why would you do this? Just because you get an error code doesn't mean that you should rebuild or reset the WMI repository. Rebuilding or resetting WMI is a last resort and not something you should ever do just because you get an error message. You need to troubleshoot and investigate before simply doing something destructive like this.

    Your initial error code was simply an unknown error to ccmsetup that means you needed to investigate the verbose Windows Installer log: client.msi.log.

    By resetting the repository, you've made things worse in the short term. At this point, you need to let the repository rebuild itself (which has probably happened by now).

    Have you manually tried to connect to and query WMI? The Win32_OperatingSystem class would be a good place to start. Once you can do this, then you can restart ccmsetup. This won't fix your original issue though because, as noted, it had nothing to do with your original issue. (Sorry, I know I'm being a bit harsh here, but I'm trying to really drive home the point that resetting the WMI repository is not an acceptable fix for an unknown issue.)



    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, October 2, 2018 2:44 PM
    Moderator
  • Thanks for replying, some of the blog & forum mentioned to reset the WMI repository due to the same error code and fixed it. That is why I did run if it could resolve it.
    Tuesday, October 2, 2018 3:09 PM
  • Not everything you read on the Internet is true :-) and in this case, it's *very* bad advice.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, October 2, 2018 4:34 PM
    Moderator