Reporting Services Configuration Tool unable to connect - by grant whellum

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 362738 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 8/20/2008 7:39:27 PM
Access Restriction Public


When opening the Reporting Services Configuration Manager attempting to connect to a local instance, no instances are available in the Report Server Instance drop down list, and when the find button is pressed the error

"No report servers were found.

Invalid Namespace"

is displayed. Have tried using the server name (with and without domain), localhost and . in the server name field and all return the same error.

The report server is operational as I am able to deploy and run reports and connect to both the report server and manager.

The old 2005 reporting services configuration tool (I have 2005 and 2008 installed side by side, 2005 is the default instance) can connect quite happily to the 2008 reporting services instance, but obviously cannot configure from there.

When you open the SQL Server Configuration Manager, select the reporting services service / properties and click the configure button it opens the 2005 tool instead of the 2008 one.

Can connect to the instance using Management studio

More feedback can be found here
Sign in to post a comment.
Posted by shannon w on 4/4/2014 at 1:01 PM
In case anyone is still researching a fix for this issue, I had the same error after an in place upgrade from 2008 to 2008 R2. Running this in a cmd window and restarting the Windows Management Instrumentation service fixed the problem for me.

mofcomp.exe "C:\Program Files\Microsoft SQL Server\MSRS10_50.ETL\Reporting Services\ReportServer\bin\reportingservices.mof"
Posted by thematrixhasyou on 1/21/2010 at 7:51 AM
Note: the reporting server name doesn't contain any special characters.
Posted by thematrixhasyou on 1/21/2010 at 7:50 AM
I just upgraded to SQL Server 2008 yesterday, and I was able to reproduce the error of "No report servers were found on the specified machine. Details: Invalid namespace".

I tried the fix below, and it didn't resolve the issue. Any other solutions available?
Posted by Microsoft on 9/2/2008 at 12:24 PM
Thank you for filing this issue.
This is a known problem that occurs in certain scenarios with RS 2008 named instance when it coexists with SQL RS 2005 side by side and we are working on fixing this issue.
The workaround to fix this is
1. Open the ReportingServices.mof file and remove "RS_" from the namespaces.
For ex: If your instance name for RS 2008 is "SQL2008", replace
#pragma namespace ("\\\\.\\root\\Microsoft\\SqlServer\\ReportServer\\RS_SQL2008")
#pragma namespace ("\\\\.\\root\\Microsoft\\SqlServer\\ReportServer\\SQL2008")
2. Run command "MOFCOMP" from the command prompt by supplying the reportingservices.mof file name as parameter

Note that the above workaround will not solve your problem if the instance name contains any special characters. For those scenarios you need to recreate a RS 2008 instance without using special characters.