Wednesday, March 7, 2012

ReportingSrvc Logs filling drive

For no apparent reason RS logging started filling the
servers drive with 33 MB files. Researching it gave a
reboot solution, but no fix. The same 4 lines repeat
themselves.
ReportingServicesService!runningjobs!273c!8/15/2004-
14:22:20:: i INFO: Execution Log Entry Expiration timer
enabled: Cycle: 41859 seconds
ReportingServicesService!dbcleanup!2738!8/15/2004-
14:22:20:: i INFO: Expiring old execution log entries
ReportingServicesService!dbcleanup!2738!8/15/2004-
14:22:20:: i INFO: Expiration of old execution log entries
is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!2738!8/15/2004-
14:22:21:: i INFO: Cleaned 0 broken snapshots, 0 chunks
ReportingServicesService!runningjobs!2738!8/15/2004-
14:22:21:: i INFO: Execution Log Entry Expiration timer
enabled: Cycle: 41858 seconds
ReportingServicesService!dbcleanup!273c!8/15/2004-
14:22:21:: i INFO: Expiring old execution log entries
ReportingServicesService!dbcleanup!273c!8/15/2004-
14:22:21:: i INFO: Expiration of old execution log entries
is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!273c!8/15/2004-
14:22:21:: i INFO: Cleaned 0 broken snapshots, 0 chunks
Is there a fix for this?
GRWe are aware of this issue and are working on a potential fix. Your best
option at this point is to contact PSS.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"GR" <anonymous@.discussions.microsoft.com> wrote in message
news:696501c48399$85c483e0$a301280a@.phx.gbl...
> For no apparent reason RS logging started filling the
> servers drive with 33 MB files. Researching it gave a
> reboot solution, but no fix. The same 4 lines repeat
> themselves.
> ReportingServicesService!runningjobs!273c!8/15/2004-
> 14:22:20:: i INFO: Execution Log Entry Expiration timer
> enabled: Cycle: 41859 seconds
> ReportingServicesService!dbcleanup!2738!8/15/2004-
> 14:22:20:: i INFO: Expiring old execution log entries
> ReportingServicesService!dbcleanup!2738!8/15/2004-
> 14:22:20:: i INFO: Expiration of old execution log entries
> is complete. Removed 0 entries.
> ReportingServicesService!dbcleanup!2738!8/15/2004-
> 14:22:21:: i INFO: Cleaned 0 broken snapshots, 0 chunks
> ReportingServicesService!runningjobs!2738!8/15/2004-
> 14:22:21:: i INFO: Execution Log Entry Expiration timer
> enabled: Cycle: 41858 seconds
> ReportingServicesService!dbcleanup!273c!8/15/2004-
> 14:22:21:: i INFO: Expiring old execution log entries
> ReportingServicesService!dbcleanup!273c!8/15/2004-
> 14:22:21:: i INFO: Expiration of old execution log entries
> is complete. Removed 0 entries.
> ReportingServicesService!dbcleanup!273c!8/15/2004-
> 14:22:21:: i INFO: Cleaned 0 broken snapshots, 0 chunks
> Is there a fix for this?
> GR

No comments:

Post a Comment