All about SQL Server Reporting Services 2000 Logs:

 

There are tons of logs in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\LogFiles...what do all those files do?

ReportServerService_main:_TimeDateStamp:

This log records information about what happens during appdomain recycles, some info about service initialization and not too much else. If you don't have problems right as you start up SSRS, this log probably won't be all that useful to you.

ReportServerService:_TimeDateStamp:

When you have problems with subscriptions, delivery, and anything "unattended", this is the log where all the action is. If you don't feel like scrolling through the whole log, search on "e Error", which will land you on your problem entries.

ReportServerWebApp_TimeDateStamp:

This log records errors thrown by the Report Manager. If the SQL instance that hosts the ReportServer database is down, for example, you'll see errors here when you open up report manager (General Network Error) and it tries to talk to the webservice. This is where you'll also see other standard errors like "server is not initialized" (break out rskeymgmt.exe!)

ReportServer:_TimeDateStamp:

This is the log for the RS processing engine. More often then not, when you see an error in the ReportServerWebApp log, you'll see a matching one here. The error being reported by report manager is simply an exception that the engine has already thrown. This log records failed login attempts to various data sources your reports connect to as well.

Comments

• Anonymous
  March 13, 2007
  I have seen instances where the report output is not written to the latest ReportServer:_TimeDateStamp log file. Instead, errors were being outputted to one of the older ReportServer:_TimeDateStamp log files instead. I understand a new log file gets created on every restart. Are you saying that if SSRS is writing to one of the old log files that this is a bug?