August 30, 2010 at 10:01 am
Hi All,
I came in this morning and started going through my morning checks on one of my production SQL 2008 boxes and got the following error when I went to expand the Processes area in Activity Monitor:
"The Activity Monitor is unable to execute queries against server (production server name). Activity monitor will be placed into a paused state.
Use the context Menu in the overview pane to resume the activity."
I have seen this in the past, but when I have seen this message it has usually been the result of a very large block, extremely high resource utilization or excessive locking. Unfortunately, I don't have any of that happening today. My processor and memory utilization is on the lower end of normal. My buffer cache hit ratio is hovering between 98 and 100%. My queue lengthes (disk and processor) are on the lower end of normal and there isn't any blocking or excessive locking happening.
Activity Monitor is otherwise functioning normally. That is to say that as long as I leave the processes area along the histograms, Resource Waits, Data File I/O and Recent Expensive Queries all work normally.
I did find the two post below and worked through them to no avail:
http://social.msdn.microsoft.com/Forums/en-US/sqltools/thread/f939197a-40d1-4a0b-adbf-c81a9467d808
http://serverfault.com/questions/141849/activity-monitor-is-unable-to-execute-queries-against-server
The only thing that has changed on this server is that the System Center DPM Protection Agent on this server was updated over the weekend.
Obviously this is not a back breaker as there are plenty of other methods for monitoring my active processes on this server. However, I was wondering if anyone else has come across this issue or if anyone knew what is going on under the covers in terms of SP's or queries when the process area is expanded.
Any help would be greatly appreciated.
August 30, 2010 at 1:42 pm
UDATE:
After digging around and reviewing user connections I found a SPID that had over 30 suspended connections to the server. Since this is highly unusual in my environment, I killed the SPID and what do you know... Everything is working....
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply