Out of the blue today, with no changes on the server that I'm aware of, I'm
getting this message when I try to access the report manager....

The underlying connection was closed: The remote name could not be resolved.

I can access https://localhost/reportserver and get the FTP style listing of
the folders and reports. And run the reports.

I'm also getting this message when I try to access the reports though the
web service.

Please help.

RE: 'The remote name could not be resolved' error suddenly by Aaron

Aaron
Tue Aug 16 11:42:23 CDT 2005

Some additional information...I've tried most of the posted fixes for this
including...

Making sure I have this in my RSReportServer.config file...
<Add Key="SecureConnectionLevel" Value="0"/>

Making sure my RSWebApplication.config file contains the correct
ReportServerUrl entry.

As I stated previously everything work until this morning. None of these
files were changed and there were no system changes that I'm aware of.

Could the Automatic Updates installed something that affected this?

"Aaron" wrote:

> Out of the blue today, with no changes on the server that I'm aware of, I'm
> getting this message when I try to access the report manager....
>
> The underlying connection was closed: The remote name could not be resolved.
>
> I can access https://localhost/reportserver and get the FTP style listing of
> the folders and reports. And run the reports.
>
> I'm also getting this message when I try to access the reports though the
> web service.
>
> Please help.

RE: 'The remote name could not be resolved' error suddenly by Aaron

Aaron
Tue Aug 16 13:55:30 CDT 2005

PROBLEM SOLVED

The DNS server was down so the URL listed in the ReportServerUrl tag was not
being resolved.

"Aaron" wrote:

> Some additional information...I've tried most of the posted fixes for this
> including...
>
> Making sure I have this in my RSReportServer.config file...
> <Add Key="SecureConnectionLevel" Value="0"/>
>
> Making sure my RSWebApplication.config file contains the correct
> ReportServerUrl entry.
>
> As I stated previously everything work until this morning. None of these
> files were changed and there were no system changes that I'm aware of.
>
> Could the Automatic Updates installed something that affected this?
>
> "Aaron" wrote:
>
> > Out of the blue today, with no changes on the server that I'm aware of, I'm
> > getting this message when I try to access the report manager....
> >
> > The underlying connection was closed: The remote name could not be resolved.
> >
> > I can access https://localhost/reportserver and get the FTP style listing of
> > the folders and reports. And run the reports.
> >
> > I'm also getting this message when I try to access the reports though the
> > web service.
> >
> > Please help.