Sign in

ccmsetup.log ends with 0x80004005. what does it want from me??

Solvedclientconfigmgrsccm11 replies · 168 views · started
Reply
Accepted solution by Cleo Banerjee — exit code 1603 is a generic MSI faiulre. common causes: a broken WMI repository (check with winmgmt /verifyrepository), a leftover broken…
  1. Zane Castillo
    @zane.castillo

    long time lurker first post lol rolling out 40 laptops. the client install via the task sequence fails over and over:

    Log viewer - C:\Windows\ccmsetup\Logs\ccmsetup.log

    Log viewer - C:\Windows\ccmsetup\Logs\ccmsetup.log
Running as user "SYSTEM"
Detected 120318 MB free disk space on system drive.
Checking Write Filter Status.
Downloading file client.msi
Download complete.
Running installation package
  Package:     C:\WINDOWS\ccmsetup\client.msi
  Log:         C:\WINDOWS\ccmsetup\Logs\client.msi.log
MSI: Setup was unable to compile the file DiscoveryStatus.mof.
MSI: The error code is 80041002
Installation failed with error code 1603
A Fallback Status Point has not been specified.

    the error is 0x80004005 😂 our consultant set this up years ago and left... i know just enough ConfigMgr to be dagnerous... where should i start?

    we have a single primary site, a management point and a coulpe of distribution points. nothing exotic. im trying to find a methodical approach to this so i can fix it once rather than device by device.

    10
  2. Cleo Banerjee
    @thread_bench546

    hmmmm quick q what does ccm.log on the site server show for one of the failed devices?? ?

    0 2 helpful
  3. Rhea Bauer
    @rhea_proxy

    make a backup before u touch the firmware, learned that teh hard way hope that helps :)

    1 3 helpful
  5. Tariq W.
    @tariqw820
    in reply to @zane.castillo

    Read the logs in order. On the site server: ccm.log (client push attempts), on the client: C:\Windows\ccmsetup\Logs\ccmsetup.log, then client.msi.log for MSI errors. Search client.msi.log for return value 3 to find the actual failing action. fingers crossed 🤞

    0 1 helpful
  6. Ibrahim
    @pixel_fox-3ta

    yeahhh 0x80070005 (access denied) during client push usually means teh push account isnt a local administrator on the target, or ADMIN$ isn't reachable. 0x800706ba (RPC server unavailable) means teh firewall blocks WMI/RPC or the device is offline. allow File and Printer Sharing and WMI inbound for the site server.

    31 0 helpful
  8. Bea A.
    @uplinkgremlin
    in reply to @zoe.thorne72

    check prerequisites: ccmsetup downloads from the management point or a distribution point... if teh device isnt in a boundary group with a reachable DP, the download fails, also verify /mp: and SMSSITECODE= if you install manually. fingers crossed 🤞

    thinking

    15 0 helpful
  9. Cleo Banerjee
    @thread_bench546
    Accepted solution

    exit code 1603 is a generic MSI faiulre. common causes: a broken WMI repository (check with winmgmt /verifyrepository), a leftover broken client (run ccmsetup.exe /uninstall first), or a pending reboot blocking teh install. fingers crossed 🤞

    2 5 helpful
  10. Cleo Thorne
    @voxeldeck

    hmmmm quick q is configmgr even worth bothering with or should i just leave it ??

    5 0 helpful
  11. Ibrahim
    @pixel_fox-3ta

    @thread_bench546 did u ever fix it?. told my boss it would take 10 mintues. its been all weekend

    0 2 helpful
  12. Zane Castillo
    @zane.castillo
    in reply to @thread_bench546

    @thread_bench546 Added teh missing subnet to a boundary group. Clients downloaded content and installed. Huge thanks! cant believe it was that simple lol

    2 0 helpful

Reply to this topic

Sign in or create an account to reply.