locked
After SCCM upgrade to 1906 - CCMSetup failing to install in the client machines RRS feed

  • Question

  • Hi All, 

    Could help while installing the CCMSetup failing to install in the client machines. 

    CCMSETUP.log 

    MSI: Action 16:58:04: CcmCreateWmiNamespacesRollback. Calls CcmRemoveWmiNamespaces. Deletes the WMI namespaces. ccmsetup 11/12/2019 16:58:04 12112 (0x2F50)
    MSI: Action 16:58:04: CcmCreateWmiNamespaces. Creates the WMI namespaces found in the CcmWmiNamespace table ccmsetup 11/12/2019 16:58:04 12112 (0x2F50)
    MSI: Action 16:58:04: CcmWmiRollback. Deletes the existing site policy config and then recompiles MOF to restore old WMI instances. ccmsetup 11/12/2019 16:58:04 12112 (0x2F50)
    MSI: Action 16:58:04: CcmDeleteWmiBackup. Deletes the back up mof of the wmi namespace created for rolling back purposes. ccmsetup 11/12/2019 16:58:04 12112 (0x2F50)
    MSI: Action 16:58:04: CcmRemoveWmiObjectsRollback. Calls CcmRemoveWmiObjects. Removes WMI objects found by CcmRemoveWmiObjectsInit. ccmsetup 11/12/2019 16:58:04 12112 (0x2F50)
    MSI: Action 16:58:04: CcmRegisterWmiMofFile. Compiles MOF files that were queued by CcmRegisterWmiMofFilesInit. ccmsetup 11/12/2019 16:58:04 12112 (0x2F50)

    Clientmsi.log

    [16:58:34] Compiled 'C:\WINDOWS\CCM\BGBPolicy.mof'
    MSI (s) (AC!18) [16:58:34:863]: Closing MSIHANDLE (12857) of type 790531 for thread 13080
    MSI (s) (AC!18) [16:58:34:863]: Creating MSIHANDLE (12858) of type 790531 for thread 13080
    MSI (s) (AC!18) [16:58:34:863]: Closing MSIHANDLE (12858) of type 790531 for thread 13080
    MSI (s) (AC!18) [16:58:35:004]: Creating MSIHANDLE (12859) of type 790531 for thread 13080
    MSI (s) (AC!18) [16:58:35:004]: Closing MSIHANDLE (12859) of type 790531 for thread 13080
    MSI (s) (AC!18) [16:58:35:004]: Creating MSIHANDLE (12860) of type 790531 for thread 13080
    [16:58:35] Compiled 'C:\WINDOWS\CCM\CARelayHelper.mof'
    MSI (s) (AC!18) [16:58:35:004]: Closing MSIHANDLE (12860) of type 790531 for thread 13080
    MSI (s) (AC!18) [16:58:35:004]: Creating MSIHANDLE (12861) of type 790531 for thread 13080
    MSI (s) (AC!18) [16:58:35:004]: Closing MSIHANDLE (12861) of type 790531 for thread 13080
    MSI (s) (AC!18) [16:58:35:129]: Creating MSIHANDLE (12862) of type 790531 for thread 13080
    MSI (s) (AC!18) [16:58:35:129]: Closing MSIHANDLE (12862) of type 790531 for thread 13080
    MSI (s) (AC!18) [16:58:35:129]: Creating MSIHANDLE (12863) of type 790531 for thread 13080
    [16:58:35] Compiled 'C:\WINDOWS\CCM\CAComplRelay.mof'


    Wednesday, December 11, 2019 5:17 PM

All replies

  • Those snippets have no real value for troubleshooting.

    Does the end of ccmsetup.log say that the installation succeeded or failed?

    If failed, what's the error code?

    Also, what *exactly* are you troubleshooting and why; i.e., how do you know it's failing?


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

    Wednesday, December 11, 2019 5:34 PM
  • Can you upload the complete ccmsetup.log file in a hosting server and share with us the download link?
    Wednesday, December 11, 2019 6:36 PM
  • Hi,

    To know if the client is healthy and able to send /receive policies /able to talk to Management point or not ,there are few Log files which we should look into: CCMSETUP.LOG, ClientIDManagerStartup.log, ClientLocation.log, LocationServices.log. 

    For more details about this issue, please refer to:
    SCCM Client installation Troubleshooting steps Check list
    Troubleshooting SCCM ..Part I (Client Push Installation )

    Thanks for your time.

    Best regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, December 12, 2019 2:42 AM
  • Hi,

    Just checking in to see if there is any update. If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

    Thanks and regards,
    Simon 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 16, 2019 1:29 AM
  • Yeah, we're seeing same - v1906 client upgrade is stalling at 

    <![LOG[MSI: Action 14:23:58: CcmRegisterWmiMofFile. Compiles MOF files that were queued by CcmRegisterWmiMofFilesInit.]LOG]!><time="14:23:58.465+00" date="12-07-2019" component="ccmsetup" context="" type="0" thread="7252" file="msiutil.cpp:316">

    Same final entry in clientmsi.log as well

    MSI (s) (BC!DC) [14:25:34:323]: Closing MSIHANDLE (12797) of type 790531 for thread 6108
    MSI (s) (BC!DC) [14:25:34:323]: Creating MSIHANDLE (12798) of type 790531 for thread 6108
    MSI (s) (BC!DC) [14:25:34:323]: Closing MSIHANDLE (12798) of type 790531 for thread 6108
    MSI (s) (BC!DC) [14:25:34:517]: Creating MSIHANDLE (12799) of type 790531 for thread 6108
    MSI (s) (BC!DC) [14:25:34:517]: Closing MSIHANDLE (12799) of type 790531 for thread 6108
    MSI (s) (BC!DC) [14:25:34:517]: Creating MSIHANDLE (12800) of type 790531 for thread 6108
    [14:25:34] Compiled 'C:\Windows\CCM\CAComplRelay.mof'

    Ran a mofcomp on CAComplrelay.mof, no issues

    PS C:\Windows\ccm> mofcomp .\CAComplRelay.mof
    Microsoft (R) MOF Compiler Version 10.0.14393.0
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: .\CAComplRelay.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    WARNING: File .\CAComplRelay.mof does not contain #PRAGMA AUTORECOVER.
    If the WMI repository is rebuilt in the future, the contents of this MOF file will not be included in the new WMI reposi
    tory.
    To include this MOF file when the WMI Repository is automatically reconstructed, place the #PRAGMA AUTORECOVER statement
     on the first line of the MOF file.
    Done!


    Nothing further. Server and Workstation OSs. Case 17950343 open with MS.

    The msiexec process spawns another msiexec process, which spawns a rundll32:

    rundll32.exe PolicyAgentProvider.dll,Setup_CheckNamespaces 

    I found that if I kill that process, it will carry on, but the client will be broken. And put up quite the fight for repair. This particular machine has been trying to upgrade, stuck with that process, for 11 days!

    When I ran that command, from c:\windows\ccm as the rundll32 image suggests, a dialog box pops up with "There was a problem starting PolicyAgentProvider.dll

    The specified module cannot be found".

    Am guessing the installation program is doing the same thing - there's a hidden dialog box asking for an OK which it never gets.

    • Edited by andreww Wednesday, December 18, 2019 2:31 PM
    Wednesday, December 18, 2019 2:21 PM
  • Confirmed. Running one from the command line that pops up the dialog box results in a rundll32 stack trace that's stuck at the same place:

    https://imgur.com/a/iiyzqCU

    Maybe MS will reply to my many emails on the subject.

    Wednesday, December 18, 2019 2:40 PM
  • Maybe MS will reply to my many emails on the subject.

    I thought you said you had a case open for this? Only Microsoft can really help you with this.

    Note that given that this is isolated to only your (or at most two known environments) this is almost certainly something environmental.


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

    Wednesday, December 18, 2019 2:44 PM
  • Yes I have a case open. It's not proceeding at quite the pace I would like however.

    Not sure how it could be environmental that ccmsetup and thus msiexec is not providing a fully qualified path to rundll32. Suggestions?

    Wednesday, December 18, 2019 2:49 PM
  • CWDIllegalInDllSearch is in effect here. Shouldn't be that tho.....

    Wouldn't be the first time it broke SCCM tho - I had a case open with MS about how that stopped SCEP client installing. Yup, their own AV product breaks installation when you apply security settings they recommend...

    Wednesday, December 18, 2019 2:56 PM
  • And yes - MS now saying it's CWDIllegalInDllSearch to blame.

    Deploying this to see if it fixes it:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\rundll32.exe]
    "CWDIllegalInDllSearch"=dword:00000000

    edit: Yup. Installs and upgrades. Sonofa....

    • Proposed as answer by andreww Wednesday, December 18, 2019 3:24 PM
    • Edited by andreww Wednesday, December 18, 2019 3:24 PM
    Wednesday, December 18, 2019 3:13 PM
  • Yet none of these things are experienced by the vast majority of other customers (100,000+ using ConfigMgr) so that clearly points to some environmental factor.

    I'm in no way trying to discount your issue, just calling out that only Microsoft support along with direct, hand-on troubleshooting can truly help you work your way through this because it's unique and specific.


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

    Wednesday, December 18, 2019 3:19 PM
  • You can count CWDIllegalInDllSearch as an environmental issue. So at least we now know what the cause is, and better - it's now documented for all to see.
    Wednesday, December 18, 2019 3:28 PM