ReportServer Service Is Filling Up Log Files

I saw this header from back in April, but it has since been expired from
Microsoft's news server. Anywho, for some reason, my trace log file for the
ReportingServices Service is filling up at about 1 Mb per minute. I have dropped
the trace level down to 2 for now, but this does not fix the core issue. It
seems that the "Execution Log Entry Expiration" task, or whatever it is, is
running and will not stop, thus generating tons of trace log entries. Can
somebody please help with this?
Here is the warning message:
ReportingServicesService!runningjobs!22c8!6/22/2005-09:15:09:: w WARN: Previous
request for Execution Log Entry Expirationstill executing, skipping...
Here is the info message:
ReportingServicesService!dbcleanup!1a4c!6/22/2005-10:06:03:: i INFO: Expiring
old execution log entries
ReportingServicesService!dbcleanup!1a4c!6/22/2005-10:06:03:: i INFO: Expiration
of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!1a4c!6/22/2005-10:06:03:: i INFO: Cleaned 0
broken snapshots, 0 chunks
ReportingServicesService!runningjobs!1a4c!6/22/2005-10:06:03:: i INFO: Execution
Log Entry Expiration timer enabled: Cycle: 57236 seconds
Also, is there any way to change the location of the trace log files?This is fixed in SP2. There's also a hotfix available if you need to stay on
SP1 for some reason. What I used to do is just have a scheduled task that
ran a vbscript to delete the older log files if the size of the log folder >
300 MB
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Darrell" <Darrell.Wright.nospam@.okc.gov> wrote in message
news:u7aJg5zdFHA.688@.TK2MSFTNGP14.phx.gbl...
>I saw this header from back in April, but it has since been expired from
>Microsoft's news server. Anywho, for some reason, my trace log file for the
>ReportingServices Service is filling up at about 1 Mb per minute. I have
>dropped the trace level down to 2 for now, but this does not fix the core
>issue. It seems that the "Execution Log Entry Expiration" task, or whatever
>it is, is running and will not stop, thus generating tons of trace log
>entries. Can somebody please help with this?
> Here is the warning message:
> ReportingServicesService!runningjobs!22c8!6/22/2005-09:15:09:: w WARN:
> Previous request for Execution Log Entry Expirationstill executing,
> skipping...
> Here is the info message:
> ReportingServicesService!dbcleanup!1a4c!6/22/2005-10:06:03:: i INFO:
> Expiring old execution log entries
> ReportingServicesService!dbcleanup!1a4c!6/22/2005-10:06:03:: i INFO:
> Expiration of old execution log entries is complete. Removed 0 entries.
> ReportingServicesService!dbcleanup!1a4c!6/22/2005-10:06:03:: i INFO:
> Cleaned 0 broken snapshots, 0 chunks
> ReportingServicesService!runningjobs!1a4c!6/22/2005-10:06:03:: i INFO:
> Execution Log Entry Expiration timer enabled: Cycle: 57236 seconds
> Also, is there any way to change the location of the trace log files?