Frequent generated log file takes up the entire system drive

This happend twice on two different servers. A 33MB reporting service log was
generated every 3 minutes until it took up the entire C:\ drive. The log file
has a header then repeat some message as in the following exerpt for 30+
thousand times. Then it starts another log file endlessly until the whole C:\
drive is used.
It has caused the interruptions of programs hosted on the server. After
delete the logs the reporting service is back to normal. But we need to
prevent this from happening again.
<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.743.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerService__03_29_2005_ 18_55_53.log</Path>
<SystemName>WSReport</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiring old execution log entries
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiration of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO: Cleaned
0 broken snapshots, 0 chunks
.......
Thanks,
Michael
This is a known bug fixed in the imminent SP2 for Reporting Services.
http://support.microsoft.com/kb/885286/
You can get a hotfix, details are in the KB article. What've I've tended to
do is just set up a scheduled task to check the size of the logs folder and
if it gets over a certain size start deleting old logs.
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
"Michael" <missisummer@.community.nospam> wrote in message
news:6A7FD5FA-AA33-4B15-8472-D204B6D8B75A@.microsoft.com...
> This happend twice on two different servers. A 33MB reporting service log
> was
> generated every 3 minutes until it took up the entire C:\ drive. The log
> file
> has a header then repeat some message as in the following exerpt for 30+
> thousand times. Then it starts another log file endlessly until the whole
> C:\
> drive is used.
> It has caused the interruptions of programs hosted on the server. After
> delete the logs the reporting service is back to normal. But we need to
> prevent this from happening again.
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
> 8.00.743.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>Eastern Standard Time</TimeZone>
> <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerService__03_29_2005_ 18_55_53.log</Path>
> <SystemName>WSReport</SystemName>
> <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> <OSVersion>5.2.3790.0</OSVersion>
> </Header>
> ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
> Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiring old execution log entries
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiration of old execution log entries is complete. Removed 0 entries.
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Cleaned
> 0 broken snapshots, 0 chunks
> ......
> Thanks,
> Michael
|||Jasper,
My DBA is looking for this. Would you be able to send me the code for this
scheduled task. I'd apprciate it.
Bill..
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:%238P0SFuNFHA.604@.TK2MSFTNGP10.phx.gbl...
> This is a known bug fixed in the imminent SP2 for Reporting Services.
> http://support.microsoft.com/kb/885286/
> You can get a hotfix, details are in the KB article. What've I've tended
> to do is just set up a scheduled task to check the size of the logs folder
> and if it gets over a certain size start deleting old logs.
> --
> 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
> "Michael" <missisummer@.community.nospam> wrote in message
> news:6A7FD5FA-AA33-4B15-8472-D204B6D8B75A@.microsoft.com...
>
|||> Jasper,
> My DBA is looking for this. Would you be able to send me the code for
this
> scheduled task. I'd apprciate it.
> Bill..
You can use something I create couple of months ago for diferent purposes,
but can apply to this problem as well:
http://solidqualitylearning.com/blog...2/19/225.aspx.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com