April 2, 2012 at 3:28 pm
I have a random SSRS issue that is causing the reporting services service to use 100% CPU. The issue will not resolve until SSRS is restarted.
I have seen this at other times when excessing blocking occurred on the source. But there are no blocking issues or waits on the source database server. I don't see any unusual entries in the reporting services log. The ExecutionLog2 view shows reports still being processed and nothing but rsSuccess on the statuses. This has happened once a week for the past few weeks but not at the same time or on the same day.
Any guidance on where to look next would be greatly appreciated!
Thanks,
Kim
May 17, 2012 at 1:19 pm
This has happened to us several times, the reporting services takes up the 100% CPU. I've gone through the reporting log and have found nothing that makes sense.
My solution so far is to restart reporting services. This is not a solution I prefer.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply