View Single Post
  #2 (permalink)  
Old October 25th, 2004, 10:05 PM
happygv happygv is offline
Friend of Wrox
 
Join Date: Jun 2003
Location: Bangalore, KA, India.
Posts: 2,480
Thanks: 0
Thanked 1 Time in 1 Post
Default

Check this link - INF: Refresh of Current Activity in SEM May Cause "Error 1222: Lock Request time out period exceeded" Error Message

As it reads on that page... A second refresh usually results in success. However, if the locks are held for an extended period the error message may occur again. If you execute the sp_lock stored procedure, you can evaluate which process is holding locks on Object IDs 1, 2 and 3 of the dbid 2 (tempdb).

Also check out this Understanding and Resolving SQL Server 7.0 or 2000 Blocking Problems

Hope that helps.
Cheers!

_________________________
- Vijay G
Strive for Perfection
Reply With Quote