Large Log File Problem

Is there any progress with the previously reported issue of large log files,
where you get a new 33MB of log file every 2-3 minutes?
(C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerService__mm_dd_yyyy_hh_nn_ss.log)
One of my servers started doing this over the weekend and kept going until
it ran out of space I assume. It has stopped now, but obviously not very
nice of it.
<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.743.00</Product>
<Locale>en-US</Locale>
<TimeZone>GMT Daylight Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerService__08_15_2004_00_03_22.log</Path>
<SystemName>FOGDB1</SystemName>
<OSName>Microsoft Windows NT 5.0.2195.0</OSName>
<OSVersion>5.0.2195.0</OSVersion>
</Header>
ReportingServicesService!library!6c4!8/15/2004-00:03:22:: i INFO: Cleaned 0
batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
chunks, 0 running jobs
ReportingServicesService!library!6c4!8/15/2004-00:13:22:: i INFO: Cleaned 0
batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
chunks, 0 running jobs
ReportingServicesService!library!6c4!8/15/2004-00:23:22:: i INFO: Cleaned 0
batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
chunks, 0 running jobs
ReportingServicesService!library!6c4!8/15/2004-00:33:22:: i INFO: Cleaned 0
batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
chunks, 0 running jobs
ReportingServicesService!library!6c4!8/15/2004-00:43:22:: i INFO: Cleaned 0
batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
chunks, 0 running jobs
ReportingServicesService!library!6c4!8/15/2004-00:53:22:: i INFO: Cleaned 0
batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
chunks, 0 running jobs
ReportingServicesService!library!6c4!8/15/2004-01:03:22:: i INFO: Cleaned 0
batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
chunks, 0 running jobs
ReportingServicesService!library!6c4!8/15/2004-01:13:22:: i INFO: Cleaned 0
batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
chunks, 0 running jobs
ReportingServicesService!library!6c4!8/15/2004-01:23:22:: i INFO: Cleaned 0
batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
chunks, 0 running jobs
ReportingServicesService!library!6c4!8/15/2004-01:33:22:: i INFO: Cleaned 0
batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
chunks, 0 running jobs
ReportingServicesService!library!6c4!8/15/2004-01:43:22:: i INFO: Cleaned 0
batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
chunks, 0 running jobs
ReportingServicesService!library!6c4!8/15/2004-01:53:22:: i INFO: Cleaned 0
batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
chunks, 0 running jobs
ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO: Expiring
old execution log entries
ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
Expiration of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO: Cleaned
0 broken snapshots, 0 chunks
ReportingServicesService!runningjobs!6c4!8/15/2004-02:00:00:: i INFO:
Execution Log Entry Expiration timer enabled: Cycle: 86399 seconds
-- repeat last 4 lines a lot!
Cheers
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com
PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.orgWe have been looking at a potential fix for this problem. Your best option
at this point is to contact PSS.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in message
news:uMbEbq5gEHA.3016@.tk2msftngp13.phx.gbl...
> Is there any progress with the previously reported issue of large log
files,
> where you get a new 33MB of log file every 2-3 minutes?
> (C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerService__mm_dd_yyyy_hh_nn_ss.log)
> One of my servers started doing this over the weekend and kept going until
> it ran out of space I assume. It has stopped now, but obviously not very
> nice of it.
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
> 8.00.743.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>GMT Daylight Time</TimeZone>
> <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerService__08_15_2004_00_03_22.log</Path>
> <SystemName>FOGDB1</SystemName>
> <OSName>Microsoft Windows NT 5.0.2195.0</OSName>
> <OSVersion>5.0.2195.0</OSVersion>
> </Header>
> ReportingServicesService!library!6c4!8/15/2004-00:03:22:: i INFO: Cleaned
0
> batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> chunks, 0 running jobs
> ReportingServicesService!library!6c4!8/15/2004-00:13:22:: i INFO: Cleaned
0
> batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> chunks, 0 running jobs
> ReportingServicesService!library!6c4!8/15/2004-00:23:22:: i INFO: Cleaned
0
> batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> chunks, 0 running jobs
> ReportingServicesService!library!6c4!8/15/2004-00:33:22:: i INFO: Cleaned
0
> batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> chunks, 0 running jobs
> ReportingServicesService!library!6c4!8/15/2004-00:43:22:: i INFO: Cleaned
0
> batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> chunks, 0 running jobs
> ReportingServicesService!library!6c4!8/15/2004-00:53:22:: i INFO: Cleaned
0
> batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> chunks, 0 running jobs
> ReportingServicesService!library!6c4!8/15/2004-01:03:22:: i INFO: Cleaned
0
> batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> chunks, 0 running jobs
> ReportingServicesService!library!6c4!8/15/2004-01:13:22:: i INFO: Cleaned
0
> batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> chunks, 0 running jobs
> ReportingServicesService!library!6c4!8/15/2004-01:23:22:: i INFO: Cleaned
0
> batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> chunks, 0 running jobs
> ReportingServicesService!library!6c4!8/15/2004-01:33:22:: i INFO: Cleaned
0
> batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> chunks, 0 running jobs
> ReportingServicesService!library!6c4!8/15/2004-01:43:22:: i INFO: Cleaned
0
> batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> chunks, 0 running jobs
> ReportingServicesService!library!6c4!8/15/2004-01:53:22:: i INFO: Cleaned
0
> batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> chunks, 0 running jobs
> ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
Expiring
> old execution log entries
> ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> Expiration of old execution log entries is complete. Removed 0 entries.
> ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
Cleaned
> 0 broken snapshots, 0 chunks
> ReportingServicesService!runningjobs!6c4!8/15/2004-02:00:00:: i INFO:
> Execution Log Entry Expiration timer enabled: Cycle: 86399 seconds
> -- repeat last 4 lines a lot!
> Cheers
>
> Darren Green (SQL Server MVP)
> DTS - http://www.sqldts.com
> PASS - the definitive, global community for SQL Server professionals
> http://www.sqlpass.org
>|||Hi Daniel,
Is PSS the only option? We are experiencing the exact same problem and had
to suspend our nights rest to free up disk space on one of our (ofcourse
important) production servers.
Erik
"Daniel Reib [MSFT]" <> wrote in message
news:ec44VM6gEHA.3264@.tk2msftngp13.phx.gbl...
> We have been looking at a potential fix for this problem. Your best
option
> at this point is to contact PSS.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in
message
> news:uMbEbq5gEHA.3016@.tk2msftngp13.phx.gbl...
> > Is there any progress with the previously reported issue of large log
> files,
> > where you get a new 33MB of log file every 2-3 minutes?
> > (C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\LogFiles\ReportServerService__mm_dd_yyyy_hh_nn_ss.log)
> >
> > One of my servers started doing this over the weekend and kept going
until
> > it ran out of space I assume. It has stopped now, but obviously not very
> > nice of it.
> >
> > <Header>
> > <Product>Microsoft SQL Server Reporting Services Version
> > 8.00.743.00</Product>
> > <Locale>en-US</Locale>
> > <TimeZone>GMT Daylight Time</TimeZone>
> > <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\LogFiles\ReportServerService__08_15_2004_00_03_22.log</Path>
> > <SystemName>FOGDB1</SystemName>
> > <OSName>Microsoft Windows NT 5.0.2195.0</OSName>
> > <OSVersion>5.0.2195.0</OSVersion>
> > </Header>
> > ReportingServicesService!library!6c4!8/15/2004-00:03:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-00:13:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-00:23:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-00:33:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-00:43:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-00:53:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-01:03:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-01:13:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-01:23:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-01:33:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-01:43:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-01:53:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> Expiring
> > old execution log entries
> > ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> > Expiration of old execution log entries is complete. Removed 0 entries.
> > ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> Cleaned
> > 0 broken snapshots, 0 chunks
> > ReportingServicesService!runningjobs!6c4!8/15/2004-02:00:00:: i INFO:
> > Execution Log Entry Expiration timer enabled: Cycle: 86399 seconds
> > -- repeat last 4 lines a lot!
> >
> > Cheers
> >
> >
> > Darren Green (SQL Server MVP)
> > DTS - http://www.sqldts.com
> >
> > PASS - the definitive, global community for SQL Server professionals
> > http://www.sqlpass.org
> >
> >
>|||Hi Daniel,
Is PSS the only option? We are experiencing the exact same problem and had
to suspend our nights rest to free up disk space on one of our (ofcourse
important) production servers.
Erik
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:ec44VM6gEHA.3264@.tk2msftngp13.phx.gbl...
> We have been looking at a potential fix for this problem. Your best
option
> at this point is to contact PSS.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in
message
> news:uMbEbq5gEHA.3016@.tk2msftngp13.phx.gbl...
> > Is there any progress with the previously reported issue of large log
> files,
> > where you get a new 33MB of log file every 2-3 minutes?
> > (C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\LogFiles\ReportServerService__mm_dd_yyyy_hh_nn_ss.log)
> >
> > One of my servers started doing this over the weekend and kept going
until
> > it ran out of space I assume. It has stopped now, but obviously not very
> > nice of it.
> >
> > <Header>
> > <Product>Microsoft SQL Server Reporting Services Version
> > 8.00.743.00</Product>
> > <Locale>en-US</Locale>
> > <TimeZone>GMT Daylight Time</TimeZone>
> > <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\LogFiles\ReportServerService__08_15_2004_00_03_22.log</Path>
> > <SystemName>FOGDB1</SystemName>
> > <OSName>Microsoft Windows NT 5.0.2195.0</OSName>
> > <OSVersion>5.0.2195.0</OSVersion>
> > </Header>
> > ReportingServicesService!library!6c4!8/15/2004-00:03:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-00:13:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-00:23:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-00:33:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-00:43:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-00:53:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-01:03:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-01:13:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-01:23:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-01:33:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-01:43:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!library!6c4!8/15/2004-01:53:22:: i INFO:
Cleaned
> 0
> > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > chunks, 0 running jobs
> > ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> Expiring
> > old execution log entries
> > ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> > Expiration of old execution log entries is complete. Removed 0 entries.
> > ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> Cleaned
> > 0 broken snapshots, 0 chunks
> > ReportingServicesService!runningjobs!6c4!8/15/2004-02:00:00:: i INFO:
> > Execution Log Entry Expiration timer enabled: Cycle: 86399 seconds
> > -- repeat last 4 lines a lot!
> >
> > Cheers
> >
> >
> > Darren Green (SQL Server MVP)
> > DTS - http://www.sqldts.com
> >
> > PASS - the definitive, global community for SQL Server professionals
> > http://www.sqlpass.org
> >
> >
>|||At this point it is the only option. There should be no cost associated
with this, you just need to reference KB article 885286.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Erik Tamminga" <REVERSE_THIS_agnimmate@.REVERSE_THIS_nerrats.ln> wrote in
message news:edOccUunEHA.396@.TK2MSFTNGP10.phx.gbl...
> Hi Daniel,
> Is PSS the only option? We are experiencing the exact same problem and had
> to suspend our nights rest to free up disk space on one of our (ofcourse
> important) production servers.
> Erik
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:ec44VM6gEHA.3264@.tk2msftngp13.phx.gbl...
> > We have been looking at a potential fix for this problem. Your best
> option
> > at this point is to contact PSS.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in
> message
> > news:uMbEbq5gEHA.3016@.tk2msftngp13.phx.gbl...
> > > Is there any progress with the previously reported issue of large log
> > files,
> > > where you get a new 33MB of log file every 2-3 minutes?
> > > (C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > > Services\LogFiles\ReportServerService__mm_dd_yyyy_hh_nn_ss.log)
> > >
> > > One of my servers started doing this over the weekend and kept going
> until
> > > it ran out of space I assume. It has stopped now, but obviously not
very
> > > nice of it.
> > >
> > > <Header>
> > > <Product>Microsoft SQL Server Reporting Services Version
> > > 8.00.743.00</Product>
> > > <Locale>en-US</Locale>
> > > <TimeZone>GMT Daylight Time</TimeZone>
> > > <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > > Services\LogFiles\ReportServerService__08_15_2004_00_03_22.log</Path>
> > > <SystemName>FOGDB1</SystemName>
> > > <OSName>Microsoft Windows NT 5.0.2195.0</OSName>
> > > <OSVersion>5.0.2195.0</OSVersion>
> > > </Header>
> > > ReportingServicesService!library!6c4!8/15/2004-00:03:22:: i INFO:
> Cleaned
> > 0
> > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > chunks, 0 running jobs
> > > ReportingServicesService!library!6c4!8/15/2004-00:13:22:: i INFO:
> Cleaned
> > 0
> > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > chunks, 0 running jobs
> > > ReportingServicesService!library!6c4!8/15/2004-00:23:22:: i INFO:
> Cleaned
> > 0
> > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > chunks, 0 running jobs
> > > ReportingServicesService!library!6c4!8/15/2004-00:33:22:: i INFO:
> Cleaned
> > 0
> > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > chunks, 0 running jobs
> > > ReportingServicesService!library!6c4!8/15/2004-00:43:22:: i INFO:
> Cleaned
> > 0
> > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > chunks, 0 running jobs
> > > ReportingServicesService!library!6c4!8/15/2004-00:53:22:: i INFO:
> Cleaned
> > 0
> > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > chunks, 0 running jobs
> > > ReportingServicesService!library!6c4!8/15/2004-01:03:22:: i INFO:
> Cleaned
> > 0
> > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > chunks, 0 running jobs
> > > ReportingServicesService!library!6c4!8/15/2004-01:13:22:: i INFO:
> Cleaned
> > 0
> > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > chunks, 0 running jobs
> > > ReportingServicesService!library!6c4!8/15/2004-01:23:22:: i INFO:
> Cleaned
> > 0
> > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > chunks, 0 running jobs
> > > ReportingServicesService!library!6c4!8/15/2004-01:33:22:: i INFO:
> Cleaned
> > 0
> > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > chunks, 0 running jobs
> > > ReportingServicesService!library!6c4!8/15/2004-01:43:22:: i INFO:
> Cleaned
> > 0
> > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > chunks, 0 running jobs
> > > ReportingServicesService!library!6c4!8/15/2004-01:53:22:: i INFO:
> Cleaned
> > 0
> > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > chunks, 0 running jobs
> > > ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> > Expiring
> > > old execution log entries
> > > ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> > > Expiration of old execution log entries is complete. Removed 0
entries.
> > > ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> > Cleaned
> > > 0 broken snapshots, 0 chunks
> > > ReportingServicesService!runningjobs!6c4!8/15/2004-02:00:00:: i INFO:
> > > Execution Log Entry Expiration timer enabled: Cycle: 86399 seconds
> > > -- repeat last 4 lines a lot!
> > >
> > > Cheers
> > >
> > >
> > > Darren Green (SQL Server MVP)
> > > DTS - http://www.sqldts.com
> > >
> > > PASS - the definitive, global community for SQL Server professionals
> > > http://www.sqlpass.org
> > >
> > >
> >
> >
>|||I am experiencing the same problem in a production server.
I read kb article 885286. This article spoke about a hotfix that has not
been fully tested and their recommendation is not to apply this fix unless
the problem is ocurring frequently. They also stated that the next service
pack of report services will include the fix and it is best to wait. When
will the next service pack of report services be available ?
"Daniel Reib [MSFT]" wrote:
> At this point it is the only option. There should be no cost associated
> with this, you just need to reference KB article 885286.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Erik Tamminga" <REVERSE_THIS_agnimmate@.REVERSE_THIS_nerrats.ln> wrote in
> message news:edOccUunEHA.396@.TK2MSFTNGP10.phx.gbl...
> > Hi Daniel,
> >
> > Is PSS the only option? We are experiencing the exact same problem and had
> > to suspend our nights rest to free up disk space on one of our (ofcourse
> > important) production servers.
> >
> > Erik
> >
> > "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> > news:ec44VM6gEHA.3264@.tk2msftngp13.phx.gbl...
> > > We have been looking at a potential fix for this problem. Your best
> > option
> > > at this point is to contact PSS.
> > >
> > > --
> > > -Daniel
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > >
> > > "Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in
> > message
> > > news:uMbEbq5gEHA.3016@.tk2msftngp13.phx.gbl...
> > > > Is there any progress with the previously reported issue of large log
> > > files,
> > > > where you get a new 33MB of log file every 2-3 minutes?
> > > > (C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > > > Services\LogFiles\ReportServerService__mm_dd_yyyy_hh_nn_ss.log)
> > > >
> > > > One of my servers started doing this over the weekend and kept going
> > until
> > > > it ran out of space I assume. It has stopped now, but obviously not
> very
> > > > nice of it.
> > > >
> > > > <Header>
> > > > <Product>Microsoft SQL Server Reporting Services Version
> > > > 8.00.743.00</Product>
> > > > <Locale>en-US</Locale>
> > > > <TimeZone>GMT Daylight Time</TimeZone>
> > > > <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > > > Services\LogFiles\ReportServerService__08_15_2004_00_03_22.log</Path>
> > > > <SystemName>FOGDB1</SystemName>
> > > > <OSName>Microsoft Windows NT 5.0.2195.0</OSName>
> > > > <OSVersion>5.0.2195.0</OSVersion>
> > > > </Header>
> > > > ReportingServicesService!library!6c4!8/15/2004-00:03:22:: i INFO:
> > Cleaned
> > > 0
> > > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > > chunks, 0 running jobs
> > > > ReportingServicesService!library!6c4!8/15/2004-00:13:22:: i INFO:
> > Cleaned
> > > 0
> > > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > > chunks, 0 running jobs
> > > > ReportingServicesService!library!6c4!8/15/2004-00:23:22:: i INFO:
> > Cleaned
> > > 0
> > > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > > chunks, 0 running jobs
> > > > ReportingServicesService!library!6c4!8/15/2004-00:33:22:: i INFO:
> > Cleaned
> > > 0
> > > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > > chunks, 0 running jobs
> > > > ReportingServicesService!library!6c4!8/15/2004-00:43:22:: i INFO:
> > Cleaned
> > > 0
> > > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > > chunks, 0 running jobs
> > > > ReportingServicesService!library!6c4!8/15/2004-00:53:22:: i INFO:
> > Cleaned
> > > 0
> > > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > > chunks, 0 running jobs
> > > > ReportingServicesService!library!6c4!8/15/2004-01:03:22:: i INFO:
> > Cleaned
> > > 0
> > > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > > chunks, 0 running jobs
> > > > ReportingServicesService!library!6c4!8/15/2004-01:13:22:: i INFO:
> > Cleaned
> > > 0
> > > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > > chunks, 0 running jobs
> > > > ReportingServicesService!library!6c4!8/15/2004-01:23:22:: i INFO:
> > Cleaned
> > > 0
> > > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > > chunks, 0 running jobs
> > > > ReportingServicesService!library!6c4!8/15/2004-01:33:22:: i INFO:
> > Cleaned
> > > 0
> > > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > > chunks, 0 running jobs
> > > > ReportingServicesService!library!6c4!8/15/2004-01:43:22:: i INFO:
> > Cleaned
> > > 0
> > > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > > chunks, 0 running jobs
> > > > ReportingServicesService!library!6c4!8/15/2004-01:53:22:: i INFO:
> > Cleaned
> > > 0
> > > > batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0
> > > > chunks, 0 running jobs
> > > > ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> > > Expiring
> > > > old execution log entries
> > > > ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> > > > Expiration of old execution log entries is complete. Removed 0
> entries.
> > > > ReportingServicesService!dbcleanup!6c4!8/15/2004-02:00:00:: i INFO:
> > > Cleaned
> > > > 0 broken snapshots, 0 chunks
> > > > ReportingServicesService!runningjobs!6c4!8/15/2004-02:00:00:: i INFO:
> > > > Execution Log Entry Expiration timer enabled: Cycle: 86399 seconds
> > > > -- repeat last 4 lines a lot!
> > > >
> > > > Cheers
> > > >
> > > >
> > > > Darren Green (SQL Server MVP)
> > > > DTS - http://www.sqldts.com
> > > >
> > > > PASS - the definitive, global community for SQL Server professionals
> > > > http://www.sqlpass.org
> > > >
> > > >
> > >
> > >
> >
> >
>
>|||Hi Maria,
We are Reporting Services SP2 Beta was under testing internally. I believe
it will be relased by the end of 2004 with final availability in the first
half of 2005.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!