"Logicalman" <tony9scott45us@com7cast.net34> wrote in message
news:5DE74C28-B866-4F79-9E74-0539C6514E78@microsoft.com...
> We have an instance of SQLRS on a virtual server under W2003.
> Recently we had cause to reset the sever due to a dramatic slowdown in
> response times. Upon checking we found the CPU usage was constantly around
> 95
> to 100%.
> Stopping the RS and SQL services made no difference and it was only
> resolved
> by restarting the server itself.
> This coincided with a user accessing an RS report with an Excel output,
> which failed to respond 'fast enough' so he closed the window prior to the
> dialogue box appearing (open-save-cancel).
> We then set up a second server, and emulated exactly the users actions and
> found the same problems with the CPU running out of control, requiring a
> reset.
> What might be the cause of this problem? I understand the user closing the
> window initially caused the problem, but I am at a loss as to why stopping
> the RS and SQL Services failed to resolve the problem. What other process
> could RS have initiated that went out of control?
> ANY pointers would be of use as this functionality is essential to some of
> our processes, but we will need to restrict it's until this gets resolved.
> Note: We have not, as yet, installed SP2 on either of the RS Servers.
>
> Thanks in advance,
>
>
>

"TechnoSpyke" wrote:

> We've ran into the same issues with high CPU usage. Support was never able
> to point out the exact cause of the CPU spikes.
>
> We have since installed all SPs, and the latest HotFix. So far, we haven't
> seen the issue popup again. Maybe the SP2 helped with that, but we dont
> know. It'll be good to know what causes it.
>
>
> "Logicalman" <tony9scott45us@com7cast.net34> wrote in message
> news:5DE74C28-B866-4F79-9E74-0539C6514E78@microsoft.com...
> > We have an instance of SQLRS on a virtual server under W2003.
> > Recently we had cause to reset the sever due to a dramatic slowdown in
> > response times. Upon checking we found the CPU usage was constantly around
> > 95
> > to 100%.
> > Stopping the RS and SQL services made no difference and it was only
> > resolved
> > by restarting the server itself.
> > This coincided with a user accessing an RS report with an Excel output,
> > which failed to respond 'fast enough' so he closed the window prior to the
> > dialogue box appearing (open-save-cancel).
> > We then set up a second server, and emulated exactly the users actions and
> > found the same problems with the CPU running out of control, requiring a
> > reset.
> > What might be the cause of this problem? I understand the user closing the
> > window initially caused the problem, but I am at a loss as to why stopping
> > the RS and SQL Services failed to resolve the problem. What other process
> > could RS have initiated that went out of control?
> > ANY pointers would be of use as this functionality is essential to some of
> > our processes, but we will need to restrict it's until this gets resolved.
> > Note: We have not, as yet, installed SP2 on either of the RS Servers.
> >
> > Thanks in advance,
> >
> >
> >
>
>