Article ID: 821741 - Last Review: November 2, 2007 - Revision: 10.3 FIX: Lock monitor exception in DeadlockMonitor::ResolveDeadlock
BUG #: 469704 (SHILOH_BUGS) On This PageSYMPTOMSThe following stack trace may be recorded in the SQL Server
error log, and the SQL Server process may stop responding (hang) or need to be restarted: * Short Stack Dump * 00845549 Module(sqlservr+00445549) (DeadlockMonitor::ResolveDeadlock+00000025 Line 583+00000006) * 00845438 Module(sqlservr+00445438) (DeadlockMonitor::SearchAndResolve+00000134 Line 424+00000000) * 004C2D12 Module(sqlservr+000C2D12) (lockMonitor+000002F7 Line 6600+00000000) * 004C2BBC Module(sqlservr+000C2BBC) (lockMonitorThread+000000A4 Line 6414+00000005) * 41072838 Module(UMS+00002838) (ProcessWorkRequests+00000272 Line 451+00000000) * 410725B3 Module(UMS+000025B3) (ThreadStartRoutine+00000098 Line 263+00000007) * 77C37E53 Module(MSVCRT+00027E53) (endthread+000000AA) * 77E7D33B Module(kernel32+0001D33B) (RegisterWaitForInputIdle+00000043) RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:290211
(http://support.microsoft.com/kb/290211/
)
How to obtain the latest SQL Server 2000 service pack
Hotfix informationThe English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Date Time Version Size File name ------------------------------------------------------------------ 31-May-2003 18:45 2000.80.818.0 78,400 Console.exe 25-Jun-2003 01:01 2000.80.818.0 33,340 Dbmslpcn.dll 25-Apr-2003 02:12 786,432 Distmdl.ldf 25-Apr-2003 02:12 2,359,296 Distmdl.mdf 30-Jan-2003 01:55 180 Drop_repl_hotfix.sql 23-Jun-2003 22:40 2000.80.837.0 1,557,052 Dtsui.dll 23-Jun-2003 22:40 2000.80.837.0 639,552 Dtswiz.dll 24-Apr-2003 02:51 747,927 Instdist.sql 03-May-2003 01:56 1,581 Inst_repl_hotfix.sql 08-Feb-2003 06:40 2000.80.765.0 90,692 Msgprox.dll 01-Apr-2003 02:07 1,873 Odsole.sql 05-Apr-2003 01:46 2000.80.800.0 62,024 Odsole70.dll 07-May-2003 20:41 2000.80.819.0 25,144 Opends60.dll 02-Apr-2003 21:48 2000.80.796.0 57,904 Osql.exe 02-Apr-2003 23:15 2000.80.797.0 279,104 Pfutil80.dll 22-May-2003 22:57 19,195 Qfe469571.sql 12-Jun-2003 16:37 1,083,989 Replmerg.sql 04-Apr-2003 21:53 2000.80.798.0 221,768 Replprov.dll 08-Feb-2003 06:40 2000.80.765.0 307,784 Replrec.dll 05-May-2003 00:05 1,085,874 Replsys.sql 01-Jun-2003 01:01 2000.80.818.0 492,096 Semobj.dll 31-May-2003 18:27 2000.80.818.0 172,032 Semobj.rll 29-May-2003 00:29 115,944 Sp3_serv_uni.sql 01-Jun-2003 01:01 2000.80.818.0 4,215,360 Sqldmo.dll 07-Apr-2003 17:44 25,172 Sqldumper.exe 19-Mar-2003 18:20 2000.80.789.0 28,672 Sqlevn70.rll 02-Jul-2003 00:18 2000.80.834.0 180,736 Sqlmap70.dll 08-Feb-2003 06:40 2000.80.765.0 57,920 Sqlrepss.dll 23-Jun-2003 22:40 2000.80.837.0 7,553,105 Sqlservr.exe 08-Feb-2003 06:40 2000.80.765.0 45,644 Sqlvdi.dll 25-Jun-2003 01:01 2000.80.818.0 33,340 Ssmslpcn.dll 01-Jun-2003 01:01 2000.80.818.0 82,492 Ssnetlib.dll 01-Jun-2003 01:01 2000.80.818.0 25,148 Ssnmpn70.dll 01-Jun-2003 01:01 2000.80.818.0 158,240 Svrnetcn.dll 31-May-2003 18:59 2000.80.818.0 76,416 Svrnetcn.exe 30-Apr-2003 23:52 2000.80.816.0 45,132 Ums.dll 02-Jul-2003 00:19 2000.80.834.0 98,816 Xpweb70.dll STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4. MORE INFORMATIONIf you can, remove the source of the deadlock problem
and avoid using Transact-SQL-based deadlock priority adjustments. For more information, see the "set deadlock_priority" topic in SQL
Server Books Online. After this problem occurs, the SQL Server process may remain in a state that is not expected and may cause behaviors that are not wanted. Microsoft recommends that you restart the SQL Server process after this problem occurs. APPLIES TO
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
