Reporting Services - The underlying connection was closed: The remote name could not be re

Hi, Help, I am having trouble getting SQL Server 2000 Reporting
Services to work on my laptop computer. I have gotten it to work in
office/development environments several times, so it's not just
beginner cluelessness.
Installing onto Windows XP professional, 384 MB RAM, SQL Server 2000
Developer's Edition with SP 3a, ASP.NET 1.1, VS.NET 2003, not connected
to any network or even internet/wireless.
Installation ran fine, no error messages. Designer works fine, I can
select queries from my local NorthWind connecting as "sa". (I know
about not using sa, but this is for simplicity's sake)
Deploy seems to work fine. However, when I hit F5 (Play) or open IE
and navigate to localhost/Reports/Pages/Folder.aspx, I see this...
(X) Error
---
The underlying connection was closed: The remote name could not be
resolved.
Home
--
What can I do to fix this?
Thanks.
Jason
ps - localhost/reportserver?... works just fine. But the Report
Manager doesn't come up.First thing I would do is check my proxy settings in your browser. Ensure
you have selected to bypass the proxy for local request.
Next I would ensure that the machine name of your comptuer is the same as it
was when you intalled report server (the setup uses that value when forming
the URL).
Next, check that in the file rswebapplication.config under the report
manager install folder, you should find the entry reportserverurl. Ensure
the URL references your actual machinename.
If that fails, try to remove the reportserverurl element and replace it with
a reportservervirtualdirectory element and set the value to the path
"/reportserver". This should mean the report manager will look for the
report server on whatever path you access it on (e..g if you type
http://localhost/reports in the address bar, report manager will look at
http://localhost/reportserver to find the URL.
-Lukasz
--
This posting is provided "AS IS" with no warranties, and confers no rights.
<jason_wisdom@.yahoo.com> wrote in message
news:1108157981.898349.110400@.l41g2000cwc.googlegroups.com...
> Hi, Help, I am having trouble getting SQL Server 2000 Reporting
> Services to work on my laptop computer. I have gotten it to work in
> office/development environments several times, so it's not just
> beginner cluelessness.
> Installing onto Windows XP professional, 384 MB RAM, SQL Server 2000
> Developer's Edition with SP 3a, ASP.NET 1.1, VS.NET 2003, not connected
> to any network or even internet/wireless.
> Installation ran fine, no error messages. Designer works fine, I can
> select queries from my local NorthWind connecting as "sa". (I know
> about not using sa, but this is for simplicity's sake)
> Deploy seems to work fine. However, when I hit F5 (Play) or open IE
> and navigate to localhost/Reports/Pages/Folder.aspx, I see this...
>
> (X) Error
> ---
> The underlying connection was closed: The remote name could not be
> resolved.
> Home
> --
>
> What can I do to fix this?
> Thanks.
> Jason
> ps - localhost/reportserver?... works just fine. But the Report
> Manager doesn't come up.
>

Reporting Service

I have problem with repoting Service. When openhttp://localhost/reports it gives me below error what can be the solution for it

Error
The underlying connection was closed: An unexpected error occurred on a send.

Has reporting services ever worked on your box?

Was IIS working prior to installing SQL Server Reporting Services?

What account did you install reporting services to? Have you changed this account or has its password expired?

Look in both the Application and System event logs - you may find an expanatory message there.

|||

No before never i run reports on my localhost

Yea I am browsing many asp.net application and asp appcaltion on the same localhost and it is working very gud.

I Dont get error message in event log also

|||

You could also try posting tohttp://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=80&SiteID=17

You need to be as specific as possible as to host server, version of SQL you installed ect. Also patches applied as SP1 or Sp2 plus all security patches.

|||

Also check the HTTPSys log to see if you spot any problem.

C:\WINDOWS\system32\LogFiles\HTTPERR

This definitely sounds like an IIS issue rather than a RS issue.

|||

Their is no file like HTTPERR in C:\WINDOWS\system32\LogFiles\ Any another suggestion

|||Check the settings on the ReportingServices web site within IIS Manager. In particular check that the application name property is set.Which version of ASP.NET are you running on your web site? You may need to find and ASPNET_REGIIS -i to set all the ASP.NEt metadata.Also the temp files directory - check that the correct permissions have been applied to it. The ASP.NET set-up can fail to set set permissions to this.|||

Is your Reporting Service running on your locahost. If everthing is installed correctly, you should be able to to browse to it . You can check it Sql services are running from , right click on My computer-> manage->Sql Server Configuration Manager ->Sql Server 2005 services . check on right hand side widow if Sql Server Reporting Services are running.

hope this helps.

kushpaw