Reporting Services 2008 - HTTP 404 after database migration

  • Background - moved ReportServer and ReportServerTempDB databases from one Reporting Services 2008 installation to another. Restored encryption keys via the RS configuration manager, removed the old server name from the scale-out deployment tab.

    Everything started up fine, both Report Manager and web service is accessible. Able to browse report folders but when a report item (report, data source, model, etc.) is clicked on, an HTTP 404 error is received.

    Have read and attempted steps in this post with no luck:

    http://www.sqlservercentral.com/blogs/dknight/archive/2009/7/24/http-404-not-found-with-reporting-services-and-windows-7.aspx

    Wondering if anyone has experienced similar issues?

    Thanks,

    Bryan

  • Even further confused...tried editing report's properties via Report Manager, then noticed the below entry in the Report Server service log. We're not using SSL, so I'm not sure why a connection attempt to 127.0.0.1:443 is being made:

    ibrary!ReportServer_0-2!2220!01/14/2010-18:06:34:: Call to ListChildrenAction(/, False).

    library!ReportServer_0-2!2220!01/14/2010-18:06:34:: Call to ListChildrenAction(/<Folder name removed by beargle>, False).

    ui!ReportManager_0-1!5220!01/14/2010-18:06:35:: e ERROR: Unable to connect to the remote server

    ui!ReportManager_0-1!5220!01/14/2010-18:06:35:: e ERROR: HTTP status code --> 500

    -------Details--------

    System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:443

    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)

    --- End of inner exception stack trace ---

    at System.Net.HttpWebRequest.GetRequestStream()

    at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

    at Microsoft.SqlServer.ReportingServices2005.ReportingService2005.GetItemDataSources(String Item)

    at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemDataSources(String itemPath)

    at Microsoft.ReportingServices.UI.ReportDataSourcePropertiesTab.LoadReportDataSources()

    at Microsoft.ReportingServices.UI.ReportWrapperPage.Page_PreRender(Object sender, EventArgs args)

    at System.EventHandler.Invoke(Object sender, EventArgs e)

    at System.Web.UI.Control.OnPreRender(EventArgs e)

    at System.Web.UI.Control.PreRenderRecursiveInternal()

    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    library!ReportServer_0-2!2220!01/14/2010-18:06:35:: Call to GetSystemPropertiesAction().

    ui!ReportManager_0-1!5220!01/14/2010-18:06:35:: 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 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 Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)

  • Finally solved, following the instructions here:

    http://blog.iautomate.ca/2009/08/no-connection-could-be-made-because-the-target-machine-actively-refused-it/

    Never had to touch one of the rsreportserver.config file until now...

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply