Frequent generated log files takes up the whole system drive (C:\)

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,
MichaelCheck out this hotfix:
http://support.microsoft.com/kb/885286/
This problem should be fixed in SP2.
--
Adrian M.
MCP
"Michael" <missisummer@.community.nospam> wrote in message
news:C1FE7688-A420-49E1-A17C-0FC736DECC7D@.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|||Hi Michael,
Yes, as Adrian M said this is a known issue for us now. A supported hotfix
is now available from Microsoft, but it is only intended to correct the
problem that is described in this article. Only apply it to systems that
are experiencing this specific problem. This hotfix may receive additional
testing. Therefore, if you are not severely affected by this problem, we
recommend that you wait for the next Microsoft SQL Server 2000 Reporting
Services service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support
Services to obtain the hotfix. For a complete list of Microsoft Product
Support Services phone numbers and information about support costs, visit
the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
Note that if will be a *free* incident if you only asking for the hotfix
from PSS :)
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||As a quick fix, you can delete old logs using a scheduled job. Check
http://solidqualitylearning.com/blogs/dejan/archive/2004/12/19/225.aspx.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Michael" <missisummer@.community.nospam> wrote in message
news:C1FE7688-A420-49E1-A17C-0FC736DECC7D@.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