|
We're having a problem accessing the report services home page, even when logged onto the the server and doing it from localhost. When we hit
http://localhost/Reports
There's an error page that comes back and says "The remote name could not be resolved: 'administrator'" (with lower case administrator).
When we go to anything under http://localhost/ReportServer, it works OK.
The TFS server has been running for a couple of weeks now, but we haven't done much with the reporting yet, and just noticed this problem. (On a test TFS server, it works OK).
I ran the the "Reporting Services Configuration Manager", and it didn't have any errors. It had warnings next to "Email settings" and "Execution Agent", so I setup the e-mail, and used the TFSREPORTS domain user for the Execution agent. That didn't resolve the issue.
On the production server, I did have an SSL certificate setup originally and had installed Reporting Services to use it, which caused the TFS installer some grief. I fixed it by following these instructions though - http://msdn.microsoft.com/vstudio/teamsystem/tfsreadme.aspx - 2.17 Installation fails when the default Web site is configured to require a secure channel (SSL), with error code: 28804 or 28805.
I ran FileMon to see what was going on, and saw a log it was writing to, but not any other smoking guns. Opening that log file, I see entries that look like this:
w3wp!ui!1!9/28/2006-12:17:03:: e ERROR: The remote name could not be resolved: 'administrator' w3wp!ui!1!9/28/2006-12:17:03:: e ERROR: HTTP status code --> 500 -------Details-------- System.Net.WebException: The remote name could not be resolved: 'administrator' at System.Net.HttpWebRequest.GetRequestStream() at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.SqlServer.ReportingServices2005.ReportingService2005.ListSecureMethods() at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection() 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.Page.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) w3wp!ui!1!9/28/2006-12:17:05:: 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)
I don't know why its trying "administrator" for anything.
I checked the IIS site, and it seems configured fine (using the ReportServer App Pool which uses Network Service, for example).
I saw another post for a different problem mention checking TFSWarehouse.dbo._WarehouseConfig, and making sure DataReaderAccount is set correctly, and it is.
Any other ideas about what the problem might be or how to fix it?
Thanks, -Daniel |