July 27, 2005 at 10:14 am
We've started to get Error 1222: Lock request time out period exceeded when we try to read the Current Activity in EM.
Our suspicion is that we've got an application that is causing this (whatever THIS is). I've installed the sp_blocker_pss80 utility and am running profiler. Anyone have any ideas what I should be looking for? sp_blocker_pss80 is great, but the doc on MS website the output isn't the best.
TIA
July 27, 2005 at 11:08 am
Blocker puts out a lot of info. Have you tried just using sp_lock to determine the locking info when this problem occurs? This system stored procedure goes syslockinfo and gets you the raw results. EM hits against three system tables in tempdb and that may be why you're timing out. Therefore, sp_lock is going to tell you what has the locks on the tempdb objects and that will give you a clearer picture than the blocker script if the locking problem is persistent. More here:
K. Brian Kelley
@kbriankelley
July 28, 2005 at 7:47 am
When this happens with our server, it is usually do to some long running, resource intensive process. We use sp_who & sp_who2 to see what is running when EM becomes non-responsive.
July 29, 2005 at 4:40 am
I've occaisonally seen this and in each case it was due to tables in TEMPDB being locked by an application. I can't remember which ones but I used sp_lock to find the answer just as Brian K suggests.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply