Reporting Services CPU utilization

I have a box that is running SPS03 and SQL Reporting Svcs.
it was all running fine on friday when I left. When I got
in this morning the box was close to a meltdown from
running at 100% CPU Utilization for who knows how long. I
took a look at the task manager and found it was Reporting
Services running at 50% utilization hitting SQL which was
running at 50% utilization. Nobody was hittting Reporting
services at the time. It was doing this on it's own. If I
shut down the reporting services service the utilization
drops to about 0%. if I turn it back on, it goes back up
to 100%. Has anyone ever seen this type of behavior from
Reporting Services?Please contact me offline so we can troubleshoot this further :
tudortr@.microsoft.com
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Starr" <MStarr13@.hotmail.com> wrote in message
news:225e001c45d18$66eb6e40$a501280a@.phx.gbl...
> I have a box that is running SPS03 and SQL Reporting Svcs.
> it was all running fine on friday when I left. When I got
> in this morning the box was close to a meltdown from
> running at 100% CPU Utilization for who knows how long. I
> took a look at the task manager and found it was Reporting
> Services running at 50% utilization hitting SQL which was
> running at 50% utilization. Nobody was hittting Reporting
> services at the time. It was doing this on it's own. If I
> shut down the reporting services service the utilization
> drops to about 0%. if I turn it back on, it goes back up
> to 100%. Has anyone ever seen this type of behavior from
> Reporting Services?|||Yup, just had that problem myself today, and I found that not only was it hogging cpu time, it also created some 6 Gb of log files under the LogFiles folder before I became aware of the problem... 8-( You might want to check that out.
The log files all said something about expiring old execution log entries, but no matter how much I tried to turn of this execution log or the expiring of its entries, it kept making more log files with identical content, save for the timestamp on each line, which told me this happened many times per second!
I tried many things, until it struck me: I very seldomly turn off my workstation. Test: Reboot, and voila, no problems anymore.
I don't feel confident that this will be the last time it does this, because it feels too much like a bug in RS, like using GetTickCount inappropriately or something...
Hope this helps! 8-)
--
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.