Reporting service setup went wrong
-
Hello--I have a new SQL2005 installation. SQL works. Notification works. Analysis works. Reporting Service fails. The default virtual directory says service unavailable or page cannot be displayed, depending on the identity I use in the default app pool.
SQL Management Studio displays this error when I attempt t connect to Reporting Services--what does it mean?:
TITLE: Connect to Server
------------------------------
Cannot connect to <server name>
------------------------------
ADDITIONAL INFORMATION:
The underlying connection was closed: An unexpected error occurred on a receive. (Microsoft.SqlServer.Management.UI.RSClient)
------------------------------
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. (System)
------------------------------
An existing connection was forcibly closed by the remote host (System)
------------------------------
BUTTONS:
OK
------------------------------
-
Are you using SSL? I never saw your exact error; but there are a group of them that people seem to get repeatedly. There is a very good book on Reporting Services (Hitchhikers' Guide to SQL Server 2000...) and they have a web site that you can browse; but you have to buy the book in order to get responses, or to read other responses... so it is somewhat limited. I just searched there with your error message and there were no hits - so scratch that; but the book is very good for setting up the earlier reporting services, and most of it translates.
One thing that I found funny about the file RSWebApplication.config was that it cannot contain both the ReportServerURL and VirtualServer... (after installing SSL) lines that are created by default... it is one or the other, and this is documented on MSDN2.
If you have manually edited this file look carefully in that area.
-
Thanks.
I do not have SSL.
The exact error is what you see in my original post ar Times New Roman text. The browser shows Service Unavailable or Cannot Display Page depening on whether or not I use Network Service as the identity property in the app pool.
I have not manually edited any files.
-
SSL or not, I would try this if I were you. I cannot test it because we are running SSL everywhere we are using Reporting Services. This information was taken from an article on SSL - and it works... Do try it.
Go into the file named rswebapplication.config and change the URL for the reportserver; but do NOT qualify it with the port number.
For our server the change looked as follows:
<ReportServerUrl>https://p7reporting/reportserver</ReportServerUrl>
Remove the line above the ReportServerUrl entry for the ReportServerVirtualDirectory. These two lines are "mutually exclusive" according to a document on MSDN.
I cannot imagine this not being true without SSL, and no, I cannot explain why it is configured this way, or whether it is always, or not.
Good luck. I hope it helps.
-
In our case we use a virtual directory. I think SSL just needs to specifiy https.
Our config file had a virtual server line that looked like: <ReportServerUrl></ReportServerUrl>
I edited as you described, using my own server name and there is no change. I tried an IIS reset and Report Server config but no change.
I don't think the cause is the same and this might explain why the error we both saw is not the same.
thanks though
-
Here is an article on configuring report server virtual directories
http://msdn2.microsoft.com/en-us/library/ms159261.aspx
Hope it helps.
-
Hola tengo una cuenta con el rol de sysadmin. y tengo instalado en mi maquina el cliente de Sql 2005 cuando intento conectarme al servidor donde esta configurado reporting services. envia el siguiente error
Cannot connect to your server name(Microsoft.SqlServer.Management.UI.RSClient).
Si me conecto a traves del Managment studio del servidor con la misma cuenta si me deja ver esta parte .. el problema sale cuando lo intento con el cliente de otra pc
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply