March 11, 2009 at 6:14 am
I have a problem with three servers running SQL SERVER 9.0.3073 (SP2) reporting services.
The reporting services server will not start as it comes up with a timeout error.
The only cure I have come accross so far is a registry hack, I not too keen on doing this as these are live high volume servers. Has anyone else experienced this and come up with a more elegant solution ?
March 11, 2009 at 12:46 pm
you may want to review the logs. The logs will be located on the drive where SSRS are installed, in case of my computer, on drive C:
C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles
The file name will be something like this including date and time:
ReportServerService__03_11_2009_14_36_35.log
I just started my SSRS and have about 2 pages of the startup. It may have some errors in it.
Also in the following file check what authentication is used for your SSRS to conenct to SQL Server database.
C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config. If is true, check if SSRS startup account has rights to login to SQL Server Reporting Services database and if the database is up for the first place.
Also check Windows Event Log, there could be some records on startup.
Regards,Yelena Varsha
March 12, 2009 at 9:01 am
The only thing I could see was this:
Account has the relevant permissions. Not sure if this is of any use could find anything on google
System.Web.Services.Protocols.SoapException: The Report Server Windows service 'ReportServer' is not running. The service must be running to use Report Server. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerServiceUnavailableException: The Report Server Windows service 'ReportServer' is not running. The service must be running to use Report Server.
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.WebServer.ReportingService2005Impl.GetPermissions(String Item, String[]& Permissions)
at Microsoft.ReportingServices.WebServer.ReportingService2005.GetPermissions(String Item, String[]& Permissions)
w3wp!ui!6!03/11/2008-09:09:31:: e ERROR: HTTP status code --> 200
-------Details--------
System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: The Report Server Windows service 'ReportServer' is not running. The service must be running to use Report Server. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerServiceUnavailableException: The Report Server Windows service 'ReportServer' is not running. The service must be running to use Report Server.
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.WebServer.ReportingService2005Impl.GetPermissions(String Item, String[]& Permissions)
at Microsoft.ReportingServices.WebServer.ReportingService2005.GetPermissions(String Item, String[]& Permissions)
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.SqlServer.ReportingServices2005.ReportingService2005.GetPermissions(String Item)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetPermissions(String Item)
at Microsoft.ReportingServices.UI.Permissions.GetPermissions()
at Microsoft.ReportingServices.UI.Permissions.CurrentUser(String itemPath)
at Microsoft.ReportingServices.UI.ReportingPage.get_RSUser()
at Microsoft.ReportingServices.UI.FolderPage.Page_Init(Object sender, EventArgs e)
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!6!03/11/2008-09:09:31:: 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)
March 12, 2009 at 10:16 am
This exception looks like the one from the front end.
Did you check the ReportServer log as I described? There should be messages on the startup. Also next to it there is another log:
ReportServerService_XX_XX_XX..log, check this too.
just make sure XX_XX_XX_... correspond the date and time you are trying to restart the server.
Regards,Yelena Varsha
March 12, 2009 at 10:34 am
No new log is created after the failed startup. There is nothing in the event log. A log was created last night it's entry is:
w3wp!runningjobs!1!23/02/2009-12:37:26:: e ERROR: Error in timer Running Requests DB : Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerServiceUnavailableException: The Report Server Windows service 'ReportServer' is not running. The service must be running to use Report Server.
at Microsoft.ReportingServices.Diagnostics.DataProtection.ProtectData(Byte[] unprotectedData, String tag)
at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at Microsoft.ReportingServices.Library.RunningJobsDb.GetMyRunningJobs()
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.Library.RunningJobsDb.GetMyRunningJobs()
at Microsoft.ReportingServices.Library.RunningJobDbTimer.DoTimerAction()
at Microsoft.ReportingServices.Diagnostics.TimerActionBase.TimerAction(Object unused)
w3wp!webserver!7!23/02/2009-12:37:49:: i INFO: Reporting Web Server stopped
March 12, 2009 at 12:42 pm
Stupid question: did you check the ReportServer service is started in Services applet? The display name for the service is
SQL Server Reporting Services (MSSQLSERVER)
This is what your error message is saying: this service has to be started first. Unless of course this is what you are trying to do: to start this service. Check for the startup type, try to start it from the Services applet, see what messages you will get (unless as I say this is exactly what you already tried).
Regards,Yelena Varsha
March 17, 2009 at 4:01 am
Thanks for your continued help. I get the following error message:
Error:1053 The service did not respond to the start or control request in a timely fashion
May 21, 2009 at 6:02 pm
I am having the same problem. any one has a solution?? Please help
Thank you
Sally
May 22, 2009 at 3:21 am
In the end we had to transfer it to another server that was on a lower service pack level. It was the only was we could get around it. Microsoft did release a hotfix to deal with this issue but it was highly unstable and crashed our test servers.
May 22, 2009 at 8:49 am
Thanks for the update. Sometimes issues are resolved through the re-install.
Regards,Yelena Varsha
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply