I am debugging errors on my server, the machine appears to be power-cycling periodically. In trying to rule out everything I see a message in the SSRS log at:C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\LogFileswhich repeatedly says 'call to clean batch()'. Is this meaningful?Thanks in advance

You can ignore those logfile messages. What these messagesrefer to is the background thread that cleans up expired user sessions from the ReportServerTempDB. These calls happen at a configurable interval (via RSReportServer.config) and if there is no cleanup work to do, you will typically see an immediate follow-on logfile message like the following: Code Snippet i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings. -- Robert

Thanks Robert. Another perhaps related logging question: in the Application Event Logs of the machine there are logons to SQL Server by my local server (localhost\Administrator) up to 20 in a single minute at times and sometimes two in a second. Either way this goes on 24x7, and when my IIS/ASP.Net/ReportViewer application is not in use. Perhaps this is not SSRS? I have three SQL Agent jobs running every 5 minutes, maybe it's related to those.

Check the credentials SSRS is using to connect to the report server databse. If SSRS is not using the administrator account to connect to the rsdb, then it is probably due to some other process. Otherwise, it is probably some other process on the box. Hope that helps, -Lukasz

So how do we have the reportservertempdb clean up the open sessions without having to log in twice. What happens to me is that we use forms authentication, and most mornings when I come in, it requires that I log in twice to get on report manager. It does show on the event log under security that I log in and immediately my machine is logged off. So I log in again, and everything works fine. I then looked in the SSRS log and it showed the system running the Call to CleanBatch() on the database. Is there something in SSRS, that would allow us so that does not happen again?DBA