Error: The underlying connection was closed....

I have been getting the following error since re-installing Reporting
Services (I had to set up my Virtual PC again from scratch): "The underlying
connection was closed: The remote name could not be resolved" when I try to
gain access via http://localhost/reports (and when trying to run a report
using a BI product called TARGIT). I have read one other post relating to
this error - the author re-installed Reporting Services and the problem went
away - I have tried the same thing and still get the error. I also get the
error on Reporting Services with and without SP2 installed.
Can anybody help?Run the rsconfig.exe utility specifying the new server name along with the
security information.
You need to update the server URL in the file rswebapplication.config
In your Report Manager directory, look for a RSWebApplication.config file.
Open it and look for something like:
<ReportServerUrl>http://Youroldservername/ReportServer</ReportServerUrl>
Good luck!
Rajesh
MCSD.NET
http://meenrajan.blogspot.com
"Neil Wright" wrote:
> I have been getting the following error since re-installing Reporting
> Services (I had to set up my Virtual PC again from scratch): "The underlying
> connection was closed: The remote name could not be resolved" when I try to
> gain access via http://localhost/reports (and when trying to run a report
> using a BI product called TARGIT). I have read one other post relating to
> this error - the author re-installed Reporting Services and the problem went
> away - I have tried the same thing and still get the error. I also get the
> error on Reporting Services with and without SP2 installed.
> Can anybody help?|||Hi ,
I figured out the solution to this problem. Follwoing 3 things should be
made sure of:
1. Never reinstall reporting services without first uninstalling it
completely... i.e first remove the registry entiries manually then only
reporting services uninstallation is complete.
2. In the RSWebApplication.Config file in Reports Manager , the
ReportServerURL key should have a value as https:/IP(of the report manager
virtual directory)/ReportServer . If in other Report Server and Report
manager .Config files, you find localhost... replace it with the IP of the
virtual directory where reports manager and report server are installed.
3. When you deploy the report, in the configuration properties for the
project .. in the deployment path, again specify the IP instaed of
localhost...
If all these 3 things are taken care of.. then this error will not occur...
When i fixed all these, it worked for me.
pmud
"Rajesh" wrote:
> Run the rsconfig.exe utility specifying the new server name along with the
> security information.
> You need to update the server URL in the file rswebapplication.config
> In your Report Manager directory, look for a RSWebApplication.config file.
> Open it and look for something like:
> <ReportServerUrl>http://Youroldservername/ReportServer</ReportServerUrl>
> Good luck!
> Rajesh
> MCSD.NET
> http://meenrajan.blogspot.com
>
>
> "Neil Wright" wrote:
> > I have been getting the following error since re-installing Reporting
> > Services (I had to set up my Virtual PC again from scratch): "The underlying
> > connection was closed: The remote name could not be resolved" when I try to
> > gain access via http://localhost/reports (and when trying to run a report
> > using a BI product called TARGIT). I have read one other post relating to
> > this error - the author re-installed Reporting Services and the problem went
> > away - I have tried the same thing and still get the error. I also get the
> > error on Reporting Services with and without SP2 installed.
> >
> > Can anybody help?