September 4, 2012 at 3:33 pm
I am receiving an error: Unable to connect to the Report Server WMI provider. Invalid Namespace when trying to connect to my report server instance on SQL 2008 SP2.
The instance is a default instance (MSSQLSERVER). I have found this error reported on servers where SQL 2005 Reporting Services where installed and an SQL 2008 Reporting Server was installed as a named instance. This server has NEVER had SQL 2005 Reporting Services installed and does not have a named instance.
September 11, 2012 at 6:26 am
does everything look fine within reporting services config manager?
September 11, 2012 at 6:54 am
No. When I open Reporting Services Configuration Manager, and attempt to connect to the Report Server, I get the error and the application closes.
September 11, 2012 at 7:53 am
are you using any special characters?
any info @ MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles?
September 11, 2012 at 7:57 am
No it is a default instance. The server recently received all Windows Updates and the latest Service Pack. I believe that's when it broke.
September 11, 2012 at 8:50 am
My last resort would be to look into the MOF file:
Maybe you will see something that doesnt look right to you.
September 11, 2012 at 9:01 am
I looked at the file. All of the documentation I have found on this error said that there would be two report instances in the mof file and that it is caused when you have SQL 2005 and SQl 2008 installed on the same server. I only have one reference in the file and have never had any version of SQL installed on the Server except SQL 2008.
I also compared the mof file on my production report server to my test report server and they appear to be the same.
Any other ideas will be much appreciated. I do appreaciate your time in trying to help resolve my problem.
September 11, 2012 at 2:11 pm
run > WBEMTEST , connect to "root\microsoft\sqlserver\reportserver" and then from the query... button, run "select * from __namespace" (I think its double underscore). this will tell you what instances of RS are reg. to your machine... see if there is anything out of the blue here?
I remember seeing an article from MS forums about doing the above, I will check tommorow morning.
You might want to consider running repair on the reporting services install too? not sure how many RDL files you got built on this server and if you got subscriptions etc.. but may be a option.
September 11, 2012 at 2:13 pm
I'll try that. My only problem is that this a PROD system so I need to schedule an outage. Also, I just realized that I have tested SP3 on my DEV, but have not migrated it to Prod yet. When I install the SP, I'll see if that fixes, if not, then I'll try this while I have approved downtime.
Thanks again!
September 11, 2012 at 2:18 pm
sounds like a good plan. Service Pack is the way to go first - get to a consistent state.
good luck.
p.s. this is for SQL 2005 but similar concept for 2008
http://msdn.microsoft.com/en-us/library/dd353297(v=sql.90).aspx
September 26, 2012 at 1:12 pm
When I tried to install the Service Pack, I received the same error. Our System Admins did the following to rebuild the WMI database. This corrected all of my issues and I was able to install the latest service pack.
They used the instructions in this article to reset the repository files, then re-register all of the MOF files to rebuild the default WMI namespace
http://technet.microsoft.com/en-us/library/ff406382.aspx
Then restored the reporting services MOF file for the reporting services configuration manager to work properly. Details are here:
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply