February 8, 2011 at 2:16 pm
We have a server running SQL 2008 SP1, Standard. We recently discovered that SSRS isn't cleaning up it's log files. Checking the in the ReportingServicesService.exe.config file and Service configuration confirms the service is configured to the default of 14 days, and the the log file locations are also default.
Does anyone have an idea why SSRS would keep over a years worth of log files, or what could stop the cleanup. We aren't seeing anything fail in the environment but the drive fills up.
Cheers
Leo
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
February 21, 2011 at 3:01 pm
I've followed up on this and it looks like this is a bug in SQL 2008 R1 and R2.
I'd be interested to know if anyone has checked their 2008 SSRS Servers to see if they have a lot of logs.
The log file is along a path like this: C:\Program Files\Microsoft SQL Server\MSRS10.SQL2008\Reporting Services\LogFiles
If you have the problem let Microsoft Connect know you can reproduce it and escalate the issue as it has been raised in Connect as :SSRS 2008 R2 KeepFilesForDays config file item does not appear to work.
This is a fairly serious issue in some respects. The file size is limited to 32MB, so on an active server you may get a lot of small files, causing disk backups to take longer and using backup resources, potentially filling the C: Drive and killing your server.
The only work around we have so far is to create a SQL Job to delete the backup files older than 14 days, but this may be an issue if you only have SSRS installed on it's own server. If anyone has any other work arounds it would be good to know.
Cheers
Leo
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
March 1, 2011 at 10:26 am
In case only SSRS are installed on the server you can use Windows scheduler with any command like batch job or VBscript job to delete older files.
Regards,Yelena Varsha
March 9, 2012 at 4:28 am
I've annoyingly bumped into the same issue recently on a production server whereby it seems to ignore that particular setting in the ReportingServicesService.exe.config, I went to test on another non-production server to see if it would consider removing files if I changed the setting to say 2 days - it didn't! Interestingly it did manage to pick up on other changes i.e. the FileName value when changed and the service is restarted will create a new file with the correct suffix/prefix.
I've been trying to find where the source of the deletion comes from but I can't seem to find any solid information on it as it may not come from the restart of the service like the generate of the log for example.
As Yelena suggested, I intend to implement a batch file of sorts on a schedule to remove files of a certain name/type for now as this would appear to be the only thing stopping my drive coming full of data I don't really want to see!
Did you get this raised with MS?
Regards,
Rik
February 12, 2013 at 10:57 am
Cool bug. Just found 7gb of 460K logs.:blink:
March 12, 2013 at 12:15 pm
Well, I'll be ... There's where my extra disk space was vanishing to.
Two years of SSRS logs can sure eat up a hard drive. Sheesh.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply