locked
unable to compile the file CollectionSettings.mof RRS feed

  • Question

  • Hi All,

    I am trying to reinstall CCM client on one of the Windows 2008 server that was having some WUA issues. For some reason the client could not be reinstalled and its ben failing with following error

    "Setup was unable to compile the file CollectionSettings.mof"

    Tracking error in client.msi.log led me to following

     Failed to compile 'C:\Windows\CCM\CollectionSettings.mof' (Phase: 3, Object: 7, Lines: 90 - 100, Error: 8004100F)

    When I checked the line 90-100 in collectionsettings.mof, it was pointing to

    //******************************************************************************
    //
    //  CCM_ServiceWindow Working Hours defaults - Mon-Fri 5am - 10pm
    //
    //******************************************************************************
    instance of CCM_ServiceWindow
    {
        PolicyID = "7cb56688-692f-4fae-b398-0e3ff4413adb";
        PolicyInstanceID = "7cb56688-692f-4fae-b398-0e3ff4413adb";
        PolicyRuleID = "NONE";
        PolicySource = "LOCAL";
        PolicyVersion = "1.00";
        Schedules = "02C159C0381A200002C159C0381B200002C159C0381C200002C159C0381D200002C159C0381E2000";
        ServiceWindowID = "7cb56688-692f-4fae-b398-0e3ff4413adb";
        ServiceWindowType = 6;
    };

    I wonder if there is something stucked in WMI regarding service window due to prior installation and it cannot be overwritten now Is there any suggestion on how to fix this?

    Thanks

    Monday, January 11, 2016 6:34 PM

All replies

  • I wonder if there is something stucked in WMI regarding service window due to prior installation and it cannot be overwritten now Is there any suggestion on how to fix this?

    Dear Sir,

    You can try to delete pre-created CCM WMI with below command:

    Get-WMIObject -Namespace "root" -query "Select * from _Namespace where name = 'CCM'" | REMOVE-Wmiobject

    Or to manually remove CCM Client, follow http://blogs.technet.com/b/michaelgriswold/archive/2013/01/02/manual-removal-of-the-sccm-client.aspx

    Best regards

    Frank


    • Edited by Frank Dong Tuesday, January 12, 2016 3:21 AM
    Tuesday, January 12, 2016 3:21 AM
  • There are no CCM nor SMS namespace in WMI. By looking at the error, the setup is failing when its trying to setup maintenance/service window in WMI. Seems like its outside of CCM namespace
    Tuesday, January 12, 2016 3:06 PM
  • "Seems like its outside of CCM namespace"

    That's incorrect. CCM_ServiceWindow is most certainly within the CCM namespace created by the agent at installation time. are you looking for root\ccm?


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

    Tuesday, January 12, 2016 6:40 PM
  • Sorry for using words loosely. I did not mean CCM_ServiceWindow but what I meant was the agent is trying to configure default schedule somewhere in WMI based on collectionsettings.mof file (line 90-100) but it seems to me that the schedule defined in above section already exists and that might be causing agent to fail. I have confirmed that there is no root\cimv2\CCM , root\SMS nor root\CCM namespace exists in WMI. The log says it was creating these namespaces but when its setting up the schedule, it fails the installation and rolls back everything. I am suspecting issue might be outside of CCM since there is no namespace exists related to CCM in WMI.
    Tuesday, January 12, 2016 8:33 PM