Hi All,
I have a brand new install of sql server 2005 on brand new WINDOWS SERVER2003 with latest versions. Every thing works fine excepting I get a 404 when I connect to report server from management studio..
I am even able to publish reports and all the
url://localhost/reportserver
url://localhost/reports
url://localhost/reportserver/reportbuilder/reportbuilder.application
all work fine on local machine and with in the network behind the fire wall.
But when I try to connect to report server using management studio on the local server or remote server, I get the following error.
"
TITLE: Microsoft SQL Server Management Studio
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.SqlServer.Management.UI.RSClient)
ADDITIONAL INFORMATION:
The request failed with HTTP status 404: Not Found. (Microsoft.SqlServer.Management.UI.RSClient)
"
More techinal details
"===================================
Cannot connect to xxxxxxxxxxxx.
===================================
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.SqlServer.Management.UI.RSClient)
Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException e)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.SqlServer.Management.UI.RSClient.RSClientConnection.CreateConnection(String connectionString)
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.CreateConnectionObject()
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
The request failed with HTTP status 404: Not Found. (Microsoft.SqlServer.Management.UI.RSClient)
Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
"
Any help would be greatly appreciated.
Bob
What are you passing in as the server name to Management Studio?
You can connect several ways
http://localhost/reportserver
servername
servername\instance
|||I passed both the servername and the servername\instance to the management studio.
My IIS and uses port 80. I can access Reportserver, report manager and report bilder thru the Internet. I just can not connect to Report server from Management studio.
I will try connecting to RS is Management studo using http://localhost/reportserver.
Regards
Bobba
|||Hi Brad Syputa,
Thank you for the suggestion. I worked. I was not able to try your suggestion immediatly as I was out of town.
Now I have this big question:
Why am I only able to connect to "report server" from "management studio" using
1. http://localhost/reportserver
and not using
2. servername
3. servername\instance.
Your help would save me a lot of time
Regards
Bobba(Bob)
||||||bobba wrote:
Hi Brad Syputa,
Thank you for the suggestion. I worked. I was not able to try your suggestion immediatly as I was out of town.
Now I have this big question:
Why am I only able to connect to "report server" from "management studio" using
1. http://localhost/reportserver
and not using
2. servername
3. servername\instance.
Your help would save me a lot of time
Regards
Bobba(Bob)
Indeed, I am very interested in disvoering the answer. We had a developer in our organization with the same problem and could only connect by enterting http://localhost/reportserver. The DBA team is fine using servername\instance.
Is this a bug that will be resolved?
thanks in advance,
Jason Wall
|||You should be able to connect using machine\instance. This method uses WMI to get the url for SOAP calls. Will you try opening the report server config tool? Can this tool connect to the machine? Are you specifying the same instance name listed in the config tool connection dialog?|||I have the same problem.
I can connect to the reporting service by using machine\instance in report server config tool.
But I cannot connect to the reporting service through managment studio by providing machine\instance, instead, if I use http://localhost/reportserver, I can connect to the report server through management studio.
I even tried to uninstall the report service, and reinstall it again. This problem still exists.
But the same thing does not happen on my colleague's machine.
I think it is better to look into this issue...
|||I managed to solve this problem...
If you want to use machine\instance to connect Management studio.
You need to make sure in rsreportservice.config, element <UrlRoot>http://localhost/reportserver</UrlRoot> is correctly configured. (You can test this by visit this url)
I guess, the machine\instance will eventurally be translated to the <UrlRoot>. If the <UrlRoot> is not correct, then you will not be able to use machine\instance to connect report service.
|||the attempt to connect to the report server failed. check your connection information and that the report server is a compatible version(.Net 2003 version)|||I am try to solve this problem i give for this error"i have SQL 2205 with SP1 installed on my machine.
and i m not bale to connect to Report Server using SQL management studio as well as from web.
i have installed reporting server and database on same machine. i tried using
"http://localhost/reportserver"
"http://localhost/reports"
"http://localhost/reportmanager"
but i am not bale to connect i am getting "Service Unavailable" page.
and when i try to connect using SQL Management Studio with "servername/instance" as well as "http://localhost/reportserver" i am getting a error saying.
===================================
Cannot connect to http://localhost/reportserver.
The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)
===================================
but if i try and connect to other reporting server on other machine using web http://servername/reportserver i m able to connect it.
but dont know whats the problem on my machine.
do i need to start any services for this...
so anybody knows how to troubleshoot this issue.
Thanks in advance...
|||
Hi,
Any solution for the above mentioned problem?
have SQL 2005 without SP1 installed on my machine.
and i m not bale to connect to Report Server using SQL management studio as well as from web.
i have installed reporting server and database on same machine. i tried using
"http://localhost/reportserver"
"http://localhost/reports"
"http://localhost/reportmanager"
but i am not bale to connect i am getting "Service Unavailable" page.
and when i try to connect using SQL Management Studio with "servername/instance" it says, "No connection could not be made because the target machine actively refused it"
===================================
Cannot connect to http://localhost/reportserver.
The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)
Please post your suggestion, if you resolved it already.
Regards,
Bhuvana
|||i tried visiting this URL. it says 503, service un available error. Please give me the solution.|||Something to try:
I had the same issue, what I did to fix is goto C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services and ensure that the ASPNET user has read,read&Execute and List Folder security permissions applied to all the subdirectories also ensure that you click the 'Advance' button when applying the permissions to ensure the security settings are applied to all child objects. During my installation for some reason it did not assign the proper permissions to the ASPNET user (aspnet_wp account). It couldn't even read the config files.
good luck
sql
No comments:
Post a Comment