none
SQL 2005 Uninstall/Install Problem WMI Configuration related

    Question

  • Hi,

    I'm the following encountering WMI error message when invoking SQL2005 setup.

    The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine CAPRICORN Error:2147942405 (0x80070005).

    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=70342

    I'ver found other postings related to WMI errors and tried the WMI fix batch, but to no avail. I noted the error code I have is 2147942405 which is different from other postings. And from examining setup log generated, this seems to be security related, but cannot find much help combing thru msdn/google, etc

    Any help is greatly appreciated.

    -James Lin

    SCC LOG

    ================================================================

    SCCOpenPerformer Added machine: CAPRICORN
    RegisterAddCheckArticleCallbackFunction registered callback function

    Calling add article callback function for article: WMIServiceWin32OSWorking
    Callback function returned TRUE
    Adding Article...
    Article Id: WMIServiceWin32OSWorking
    Article type: 4, ARTICLE_WMI_TYPE_VALUES
    Number of value: 2
    Value: 1
    Type: ARTICLE_WMI_TYPE_PROPERTY
    Namespace: cimv2
    Class name: Win32_OperatingSystem
    Property name: OSLanguage
    Property type: 2
    Value: 2
    Type: ARTICLE_WMI_TYPE_PROPERTY
    Namespace: cimv2
    Class name: Win32_OperatingSystem
    Property name: SystemDirectory
    Property type: 2

    Calling add article callback function for article: WMIServiceWin32CompSystemWorking
    Callback function returned TRUE
    Adding Article...
    Article Id: WMIServiceWin32CompSystemWorking
    Article type: 4, ARTICLE_WMI_TYPE_VALUES
    Number of value: 1
    Value: 1
    Type: ARTICLE_WMI_TYPE_PROPERTY
    Namespace: cimv2
    Class name: Win32_ComputerSystem
    Property name: NumberOfProcessors
    Property type: 2

    Calling add article callback function for article: WMIServiceWin32ProcessorWorking
    Callback function returned TRUE
    Adding Article...
    Article Id: WMIServiceWin32ProcessorWorking
    Article type: 4, ARTICLE_WMI_TYPE_VALUES
    Number of value: 1
    Value: 1
    Type: ARTICLE_WMI_TYPE_PROPERTY
    Namespace: cimv2
    Class name: Win32_Processor
    Property name: CpuStatus
    Property type: 2

    Calling add article callback function for article: WMIServiceReadRegWorking
    Callback function returned TRUE
    Adding Article...
    Article Id: WMIServiceReadRegWorking
    Article type: 4, ARTICLE_WMI_TYPE_VALUES
    Number of value: 1
    Value: 1
    Type: ARTICLE_WMI_TYPE_REGISTRY
    DefKey: 0x80000002
    Subkey name: SOFTWARE\Microsoft\Windows\CurrentVersion
    Value name: ProgramFilesDir
    Registry type: 4

    Calling add article callback function for article: WMIServiceWin32DirectoryWorking
    Callback function returned TRUE
    Adding Article...
    Article Id: WMIServiceWin32DirectoryWorking
    Article type: 3, ARTICLE_WMI_TYPE_CLASS
    Namespace: cimv2
    WQL Query: Select * from Win32_Directory where name='C:\\'

    Calling add article callback function for article: WMIServiceCIMDataWorking
    Callback function returned TRUE
    Adding Article...
    Article Id: WMIServiceCIMDataWorking
    Article type: 3, ARTICLE_WMI_TYPE_CLASS
    Namespace: cimv2
    WQL Query: Select * from CIM_DataFile where name='C:\\'

    Calling add article callback function for article: XMLDomDocument
    Callback function returned TRUE
    Adding Article...
    Article Id: XMLDomDocument
    Article type: 1, ARTICLE_TYPE_GENERIC_FUNCTION
    RegisterCallbackFunction registered callback function
    Callback filter = 0x6

    Performing check on local machine CAPRICORN
    Connecting to CAPRICORN machine
    ConnectServer returned 0 (0x0)
    ConnectServer returned 0 (0x0)
    Openning namespace \\root\cimv2
    GetNamespace \\root\cimv2 returned 0 (0x0)
    Creating class instance Win32_ComputerSystem
    CreateInstanceEnum Win32_ComputerSystem returned 0 (0x0)
    Enumerating the first class of Win32_ComputerSystem
    EnumClass of Win32_ComputerSystem returned 2147942405 (0x80070005)
    Creating class instance Win32_OperatingSystem
    CreateInstanceEnum Win32_OperatingSystem returned 0 (0x0)
    Enumerating the first class of Win32_OperatingSystem
    EnumClass of Win32_OperatingSystem returned 2147942405 (0x80070005)
    Creating class instance Win32_OperatingSystem
    CreateInstanceEnum Win32_OperatingSystem returned 0 (0x0)
    Enumerating the first class of Win32_OperatingSystem
    EnumClass of Win32_OperatingSystem returned 2147942405 (0x80070005)
    Creating class instance Win32_Processor
    CreateInstanceEnum Win32_Processor returned 0 (0x0)
    Enumerating the first class of Win32_Processor
    EnumClass of Win32_Processor returned 2147942405 (0x80070005)
    Openning namespace \\root\default
    GetNamespace \\root\default returned 0 (0x0)
    Getting method EnumValues in StdRegProv class
    GetMethod returned 0 (0x0)
    Executing method EnumValues in StdRegProv class
    ExecMethod returned 2147942405 (0x80070005)

    Processing article WMIServiceWin32OSWorking
    Scc Error:  50026 (0xc36a)
    Error code: 2147942405 (0x80070005)
    Calling callback function for reason: 0x2
    Callback function returned TRUE

    Processing article WMIServiceWin32CompSystemWorking
    Scc Error:  50026 (0xc36a)
    Error code: 2147942405 (0x80070005)
    Calling callback function for reason: 0x2
    Callback function returned TRUE

    Processing article WMIServiceWin32ProcessorWorking
    Scc Error:  50026 (0xc36a)
    Error code: 2147942405 (0x80070005)
    Calling callback function for reason: 0x2
    Callback function returned TRUE

    Processing article WMIServiceReadRegWorking
    Scc Error:  50024 (0xc368)
    Error code: 2147942405 (0x80070005)
    Calling callback function for reason: 0x2
    Callback function returned TRUE

    Processing article WMIServiceWin32DirectoryWorking
    Openning namespace \\root\cimv2
    GetNamespace \\root\cimv2 returned 0 (0x0)
    Scc Error:  50022 (0xc366)
    Error code: 70347 (0x112cb)
    Calling callback function for reason: 0x2
    Callback function returned TRUE

    Processing article WMIServiceCIMDataWorking
    Openning namespace \\root\cimv2
    GetNamespace \\root\cimv2 returned 0 (0x0)
    Scc Error:  50022 (0xc366)
    Error code: 70347 (0x112cb)
    Calling callback function for reason: 0x2
    Callback function returned TRUE

    Processing article XMLDomDocument
    Scc Error:  0 (0x0)
    Error code: 0 (0x0)
    Calling callback function for reason: 0x4
    Callback function returned TRUE
    SccPerformer closed.

     

    Wednesday, May 17, 2006 10:20 PM

Answers

  •  

    Finally figured out a solution....

    -open Administrative Tools => Local Security Policies
    -find Local Policies=>Security Options=>"DCOM: Machine Launch Restriction in Security Descriptor Definition Language(SDDL)"
    -in my case it was showing "Not Defined" , and I opened up the properties dialog and gave System user "Local Launch" and "Local Activation"  ALLOW.
    -voila! the WMI error message is gone and the setup GUI appears.

    I guess somehow I messed up this DCOM permission when I was prepping server security before exposing the server to the internet. Again, this fix is for following sql install/uninstall erroor :

    The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine CAPRICORN Error:2147942405 (0x80070005).

    Thursday, June 22, 2006 5:53 PM

All replies

  • Cant help but have similar problem running on Vista Beta 2 , all this WMI security stuff seems insanely complicated.

    Ben

     

    Thursday, June 08, 2006 11:25 AM
  • After the 10 click install of CRM Server, I've now succeeded in screwing up a divinely error-free SBS2003 installation.  Is there a secret to removing SQL2005?  Running Add/Remove just drops straight through with no result and the CD based removal just closes without doing anything.  I've tried rubbing it out, scrubbing it out....

    John

    Saturday, June 10, 2006 5:16 PM
  •  

    Finally figured out a solution....

    -open Administrative Tools => Local Security Policies
    -find Local Policies=>Security Options=>"DCOM: Machine Launch Restriction in Security Descriptor Definition Language(SDDL)"
    -in my case it was showing "Not Defined" , and I opened up the properties dialog and gave System user "Local Launch" and "Local Activation"  ALLOW.
    -voila! the WMI error message is gone and the setup GUI appears.

    I guess somehow I messed up this DCOM permission when I was prepping server security before exposing the server to the internet. Again, this fix is for following sql install/uninstall erroor :

    The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine CAPRICORN Error:2147942405 (0x80070005).

    Thursday, June 22, 2006 5:53 PM
  • OK, I'm getting the error also. I tried all of the tricks that I could locate.

    Installing SQL should not be this difficult.

    If anyone has any ideas...

    Friday, June 23, 2006 6:30 PM
  • Tried this but no luck..any other ideas? I even compared local security settings to another server i had sql 2005 installed fine on and they are the same. Only difference is the one im installing on is a cluster and the other is a standalone server..that shouldnt make a big differenec here should it?
    Wednesday, July 12, 2006 7:46 PM
  • If you open Computer Management, expand Services and Applications and right click on WMI Control and select properties do you get an error?
    Wednesday, July 12, 2006 8:02 PM
  • I found the solve of this problem 2 days. I tried microsoft's scripts, reinstalling wmi and so on. But nothing worked.  And today i install sql 2005 by installing its  MSI components. First was SqlRun_SQL.msi (database service), then other components from disk1 and disk 2. All works.
    Monday, February 05, 2007 11:08 AM
  • Did have this problem also in a VM.
    After i did ingrease the RAM to 1024 Mb the problem was gone :)
    Wednesday, June 10, 2009 11:41 AM