Oh no, WMI error again.. last time I had WMI problem, on a different server, it took me a lot of effort troubleshooting the issue. This is totally unrelated, but is a good reference for what it can entail troubleshooting this kind of problem: [SOLVED] A MOF syntax error occured, installing SQL Server 2012 Advanced Express 64 bit edition
So, to the issue this time. A sql 2008 R2 server was migrated a couple of days ago, including its reporting services. The report server is working, and the reporting services configuration manager was working too at time of installation. A few days later, when I try to open the Reporting Services Configuration Manager, it does not give me an instance. It is blank, so I cannot connect to the report server.
First thing to try is push the connect button, it then gives me an error:
An unknown error has occurred in the WMI Provider. Error Code 80080005
I can't find anything about this error code. What does it mean ?
OK then, let's start by checking the WMI logs in the event viewer, a refresher how to do that:
To view WMI Events in Event Viewer 1.Open Event Viewer. On the View menu, click Show Analytic and Debug Logs. Locate the Trace channel log for WMI under Applications and Service Logs | Microsoft | Windows | WMI Activity. 2.Right-click the Trace log and select Log Properties. Click the Enable Logging check box to start the WMI event tracing. For more information about channels, see Event Logs and Channels in Windows Event Log. 3.WMI events appear in the event window for WMI-Activity. Double-click an event in the list to see the detailed information. You can view an event in XML View or in Friendly View format.
and I get:
Id = {DA8D4EF9-E66C-0001-B896-8DDA6CE6D101}; ClientMachine = machine; User = machine\user; ClientProcessId = 7640; Component = Unknown; Operation = Start IWbemServices::CreateInstanceEnum - root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\v10 : MSReportServer_Instance;
ResultCode = 0x80080005; PossibleCause = UnknownSo, it is trying to create an instance: IWbemServices::CreateInstanceEnum
And the name of the class is: root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\v10
I attempt to do the same with wbemtest. I can connect to the namespace, I can see the class, but trying to instantiate will give an error:
Id = {DA8D4EF9-E66C-0001-B896-8DDA6CE6D101}; ClientMachine = machine; User = machine\user; ClientProcessId = 9312; Component = Unknown; Operation = Start IWbemServices::CreateInstanceEnum - ROOT\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\v10 : MSReportServer_Instance;
ResultCode = 0x80041010; PossibleCause = UnknownSo, different error, doing the same thing, this time the error is "Invalid Class"
Applying remedies for this error:
1. Open the SQL Server Report Server folder.<Install Driver>:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer 2. Open the “bin” folder. 3. Copy and rename the file “reportingservices.mof” 4. Register the file using the following command Mofcomp <Install Driver>:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\bin\reportingservices.mof After doing the steps above, we should connect to the Reporting Services well. If the solution above does not above, could you please help to collect the following information? 1. Could you connect to SQL Server Configuration Manager? 2. The logs of SQL Server Reporting Services. 3. Does the Reporting Services windows service work fine? 4. The more detailed error message. 5. Any more information.
Did both:
C:\>mofcomp "c:\Program Files\Microsoft SQL Server\MSRS10_50.MS SQLSERVER\Reporting Services\ReportServer\bin\reportingservices.mof" Microsoft (R) MOF Compiler Version 6.3.9600.16384 Copyright (c) Microsoft Corp. 1997-2006. All rights reserved. Parsing MOF file: c:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Re porting Services\ReportServer\bin\reportingservices.mof MOF file has been successfully parsed Storing data in the repository... Done!
and
C:\>regsvr32 "C:\Program Files\Microsoft SQL Server\100\Shared\reportingserviceswmiprovider.dll"
DllRegisterServer in c:\program files\Microsoft sql server\100\shared\reportingserviceswmiprovider.dll suucceeded
Nothing changed. Just for the sake of it, let's verify WMI as a whole:
C:\Windows\system32>winmgmt /verifyrepository WMI repository is consistent
run a simple query, see things work:
wmic path "Win32_Process" get Name
works. OK then, let's run wmidiag, results in 5 errors:
44039 13:21:18 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 1 ERROR(S)! 44040 13:21:18 (0) ** - Root/aspnet, 0x8004100E - (WBEM_E_INVALID_NAMESPACE) Namespace specified cannot be found. 44041 13:21:18 (0) ** 44042 13:21:18 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 2 ERROR(S)! 44043 13:21:18 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Spooler_PrintQueue, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found. 44044 13:21:18 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)' 44045 13:21:18 (0) ** - Root/CIMV2, Win32_PerfRawData_Spooler_PrintQueue, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found. 44046 13:21:18 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)' 44047 13:21:18 (0) ** 44048 13:21:18 (0) ** WMI MOF representations: ............................................................................................ OK. 44049 13:21:18 (0) ** WMI QUALIFIER access operations: .................................................................................... OK. 44050 13:21:18 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 2 ERROR(S)! 44051 13:21:18 (0) ** - ROOT/CIMV2/POWER, InstancesOfAsync, 'CIM_Sensor', 0x80080005 - . 44052 13:21:18 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)' 44053 13:21:18 (0) ** - ROOT/CIMV2/POWER, InstancesOfAsync, 'CIM_NumericSensor', 0x80080005 - . 44054 13:21:18 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
Nothing related, but 2 of the errors are the same, and explanation of this error simply is = WBEM_UNKNOWN.
44106 13:21:18 (0) ** 2 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
OK, so, what should I try next?
OK different approach:
open up reporting services configuration manager, then check the event log. I see an error there. OK, push find button, and check event viewer again. same error, source Distributed DCOM:
The server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} did not register with DCOM within the required timeout.Unfortunately, this seems to be a generic error that says WMI did not respond, and is no help at all.
I have also checked the reporting services logs but not found any related entry. The log resides at:
C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles
Could anyone help please ?
Christmas spirit all year long Please remember to vote on useful replies. Mark answers. Help to answer questions of others while you are visting the forums. Thank you.