Unable to connect to the remote server
Greetings:
We have a copy of SQL2k Report Services running on a Windows 2003 Server. But the database used by the Reports is actually on another box in our network. (This is a option you can use during install.) This setup worked fine for about a year but now neither the reports and ReportManager no longer run. The Reporting services Log error is:
System.Net.WebException: The underlying connection was closed: Unable to connect to the remote server.
In a browser we get the error:
"Directory Listing Denied"
"This Virtual Directory does not allow contents to be listed."
Turning on the option to list directory contents in IIS does not resolve the issue.
Anyone seen this creep up before? I am unaware of any changes to the machine's security in the last few weeks but something has obviously changed.
- I can ping the remote servers where the DB's are stored.
- I am using Windows Integrated Authentication.
- I have a dev box with a similar configuration, except everything is hosted locally, and it runs fine.
Any ideas?
Thanks.
[1205 byte] By [
KidVB] at [2007-12-25]
I love replying to my own post. 
O.K. I got this resolved but wanted to post this solution as it was difficult to find via the web. The issue revolves around mappings in IIS. To fix this you need to create a new mapping in the Application Configuration on the folder for Report Server and Report Manager. Here we go:
- Launch the IIS Manager and browse to your ReportServer folder. (or whatever you have named it)
- Right-click on the folder and choose "Properties."
- Under the "Virtual Directory" tab click on the "Configuration" button located next to the "Execute Permissions" drop down list.
- Under the "Wildcard Application Maps" in the lower portion of the dialog box click the "Insert" button.
- Then click on the "Browse" button and browse to the "aspnet_isapi.dll" file located (usually) at "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322" (Depending on what version you may have installed the "v1.1.4322" portion of that path might be different.
- Click OK.
- Click OK again to get back to the main Dialog and the apply your changes.
- Voila! Mystery problem solved.
Don't know who or what removed this mapping info on the system but if I find out how I'll post that too.
Good luck!
Thanks, that solved my problem as well!
I have not followed up the forums on reporting services, but it seems like every now and then something goes wrong with RS and I have to fix it.
It usually happens 'over night' and has no logical explanation - not to me anyways. This time it was your solution that fixed it, but earlier I have had to reinstall RS to get it working again.
