sql server reporting services: We have a Report Server installation that we cannot access the Report
Manager.

The OS is Windows Server 2003. the computer is a member of an Active Server
Domain.

We a page that displays

X Error
_______________________________________________________________

The underlying connection was closed: Unable to connect to the remote
server.


Here is the Error Log:

w3wp!ui!1554!5/8/2006-11:03:04:: e ERROR: The underlying connection was
closed: Unable to connect to the remote server.
w3wp!ui!1554!5/8/2006-11:03:04:: e ERROR: HTTP status code --> 500
-------Details--------
System.Net.WebException: The underlying connection was closed: Unable to
connect to the remote server. at
System.Net.HttpWebRequest.CheckFinalStatus() at
System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
System.Net.HttpWebRequest.GetRequestStream() at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods() at
Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods() at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname) at Microsoft.ReportingServices.UI.Global.SecureAllAPI() at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level) at
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args) at System.EventHandler.Invoke(Object sender,
EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at
System.Web.UI.Control.InitRecursive(Control namingContainer) at
System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!1554!5/8/2006-11:03:11:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)
at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)

Hi Bellis,

Thank you for posting.

From your description, after installing the SQLSErver reporting service,
you're unable to visit the Report Manager application, it return a "the
underying connection was closed.... " exception , correct?

As for the reporting service, is it SSRS 2005 with SQL 2005 DB engine?
Based on my experience, there is some setting about the reportmanger or
reportserver application's virtual directory setting in IIS which could
cause this problem. You can have a look at the following MSDN article to
see whether the problem in your scenario fits them:

#Configuring Report Server Virtual Directories
http://msdn2.microsoft.com/en-US/library/ms159261.aspx

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Thanks for the help Steven,
We are running SQL 2000 on this server (not sure if that matters). we are
trying the fix you reccommended and will keep you posted.

....Bryan

Thanks for your response Bryan,

Please feel free to post here or share with us if you have got any progress.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Help this did not solve our problem!
We are not using any custom security extensions for report server.

....Bryan


[quoted text, click to view]

Perhaps the problem may be related to the fact that report server was
installed by the DBA and we are trying to access the report manager using a
different account?
....Bryan


[quoted text, click to view]

Thanks for your response Bryan,

Actually that msdn document mentioend that those changes also necessary
when you're not performed the installation of reporting service as the
default mode( reportManager and reportServer application under the same
local default site ...). So is your reporting service installed as the
default mode?(both reportserver and report manager application are
installed on the same machine and under tha default IIS site)? Anyway,
onething you can have a look is the reporting service's log file which is
under the "C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\LogFiles folder". You can check it to see whehter there is any
clues about the problem.

As for the Account issue, I think it won't quite matter who install it. By
default, the report server and report manager will running under the proper
IIS's application pool service account (if using IIS6). And when user try
accessing reportManger, report Server, since by default both the two
applications are configured to use windows authentication(deny anonymous),
the vistor's account will be used as the security context. Also, you can
try directly visiting the report server application(rather than report
Manager) to see whether you'll get the same error(if so, also check log
files).

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Thanks for your response Steven,

We discovered today that durring the initial install of Reporting services
we encountered this error: http://support.microsoft.com/?kbid=867872

The DBA who did the install followed the workaround which involved manually
configuring the virtual directories.

Is there a way to resolve the IWAM_Computername password syncronization?

We would really prefer to do the default installation of RS.

....Bryan

Thanks for your response Bryan,

Then, after you installed the reporting service following that kb article,
has it been working correctly ever or just never works? As for the
IWAM_ACCOUNT, it is the IIS's web application manager account, its password
is controlled by machine (not users). However, after you've installed the
reporting service, I don't think that account will matter much(since it is
used at install time...).
Also, I think the problem is still like some security setting not
configured correctly in the IIS virtual directory of the report server
application. I suggest you look over the virtual directory settings
mentioend in that kb article and the article I mentioned earlier ( IIS vdir
setting is same between SSRS 2000 and 2005).

BTW, have you found any security or authentication related error info in
the log files?

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Thanks Steven,

We found that the Server had been IIS Hardened which meant that DCOM (COM+)
had been disabled by default.
We manually started this service and the ASP.Net Service and then were able
to perform the default install of RS.

The Reporting serices is now installed and functional.

Thanks for your help!
....Bryan

Thanks for your followup Bryan,

Really glad that you've got it working.

Have a good day!

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)