WMI error has occurred when using report configuration manager


  • Hi,

    I Installed SQL Server 2005 Standard Edition with Reporting Services.

    When i open report configuration manager and try to connect,  i found the following error:

    Reporting Services Configuration Manager: kashif-pc\SQLKashif

    "Unhandled exception has occured in your application. If you click continue, the pplication will ignore this error and attempt to continue. .....................

    A WMI error has occurred and no additonal error information is available.

    for details:

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    ReportServicesConfigUI.WMIProvider.WMIProviderException: A WMI error has occurred and no additional error information is available. ---> System.Runtime.InteropServices.COMException (0x8000000A)
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
       at ReportServicesConfigUI.WMIProvider.RSInstance.RefreshServerStatus()
       --- End of inner exception stack trace ---
       at ReportServicesConfigUI.WMIProvider.RSInstance.RefreshServerStatus()
       at ReportServicesConfigUI.WMIProvider.RSInstance.get_DelayLoadConfiguration()
       at ReportServicesConfigUI.WMIProvider.RSInstance.get_Item(ConfigurationItemNames itemName)
       at ReportServicesConfigUI.ConfigurationManager.ResetStepStatus()
       at ReportServicesConfigUI.ConfigurationManager.ChangeMachine()
       at ReportServicesConfigUI.ConfigurationManager.LaunchDialog()
       at ReportServicesConfigUI.ConfigurationManager.OnActivated(EventArgs e)
       at System.Windows.Forms.Form.set_Active(Boolean value)
       at System.Windows.Forms.Form.WmActivate(Message& m)
       at System.Windows.Forms.Form.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    ************** Loaded Assemblies **************
        Assembly Version:
        Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
        Assembly Version:
        Win32 Version: 9.00.1399.00
        CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/RSConfigTool.exe
        Assembly Version:
        Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/
        Assembly Version:
        Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/
        Assembly Version:
        Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/
        Assembly Version:
        Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/
        Assembly Version:
        Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the section.
    The application must also be compiled with debugging

    For example:

        < jitDebugging="true" />

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.


    Friday, March 13, 2009 6:14 PM

All replies

  • Are you getting this error right after the installation? What installation and configuration steps did you follow?

    Life ~ Game
    Tuesday, March 17, 2009 1:26 AM
  • I am getting the same error right after installing Reporting Services on a Windows Server 2008.  When I run the Reporting Services Configuration Tool I get the same error described above by Kashif Chotu.  the configuration steps I used where from a Citrix document "Configuring Reporting Services for Citrix EdgeSight".  Here is a link to that document -  I used the instructions for SQL 2005 starting on page 27.  On page 32, step 10, I set the service to use Local System Account.  The SQL Server Reporting Services service is started and running using the Local System Account.  I installed Reporting services on it's own server, not an SQL database server.  I will be pointing the reporting server to an existing SQL database server.

    Thank you for your help.
    Monday, April 27, 2009 7:01 PM
  • I figured it out.  All I had to do was install SQL 2005 Service Pack 2.  That resolved my issue.  Thanx.

    • Proposed as answer by Gandhi Pritesh Tuesday, April 27, 2010 2:02 PM
    Monday, April 27, 2009 7:07 PM
  • Thanks
    Tuesday, April 27, 2010 2:02 PM
  • I have SQL Server 2005 SP3. But still i am getting the same problem any workaround???
    Thursday, July 8, 2010 8:50 AM
  • Same issue. SP3 installed. Installed reporting services on default instance and local system account.
    Tuesday, August 10, 2010 3:44 PM
  • Same issue here. Connecting remotely to Windows Server 2008 R2.  Running SQL Server 2005 SP3, when launching Reporting Services COnfiguration tool I get the same WMI error and eventually it completely crashes the tool. 

    Can we configure ReportingServices from command line or sql mgmt studio?  Can Reporting Services 2008 be installed on a SQL Server 2005 database instance?

    fwiw, I also get a WMI error upon remote login for VkernelAppView (an unrelated app).

    I don't have access to setup disc and havent been able to reinstall. ANyone have the problem persist after a reinstall of Reporting Services 2005?



    Tuesday, October 26, 2010 8:20 AM
  • My situation resolved itself when I uninstalled 2005 Reporting Services ( a very scary experience with the uninstall routine making you feel like you're uninstalling SQL server which i didn't want to do, make sure you read through others experiences in this uninstall regard).

    I then installed Reporting Services 2005 again on the same original SQL server instance.  At this point i ran the SP3 pack against Reporting Services and it updated RS to SP3 which was my original problem i think.  While my sql server 2005 had always been at SP3 I don't think the instance of Reporting Services was ever patched to sp3 so it's possible that if I had patched RS to SP3 at the beginning I may have never even encountered the original WMI errors.


    Thursday, October 28, 2010 11:42 AM
  • After receiving the same error described in this forum, I applied SP3 to SQL and SSRS, resolving the wmi error.

    Clifton G. Collins III
    Tuesday, November 16, 2010 1:45 PM
  • Installing SP4 against Reporting Service did the trick for me.  I had installed SQL Server 2005 first (without Reporting Services), i then installed Service Pack 4.  At a later time, I installed the Reporting services component and was getting the error posted in the thread.  It seems since RS and SQL are not on the same SP level, you get the message.  I re-ran the SP4 setup, and it listed the Reporting Services component, i selected those, and once that was installed, everything worked fine.

    Thanks to the person who posted the SP suggestion!!

    Tuesday, August 23, 2011 6:15 PM