FIX: An access violation exception may occur when multiple users try to perform data modification operations at the same time that fire triggers that reference a deleted or an inserted table in SQL Server 2000 on a computer that is running SMP

This article has been archived. It is offered "as is" and will no longer be updated.
Bug #: 471952 (SQL Server 8.0)

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package.
  • The prerequisites for installing the hotfix package.
  • Whether you must restart your computer after you install the hotfix package.
  • Whether the hotfix package is replaced by any other hotfix package.
  • Whether you must make any registry changes.
  • The files that are contained in the hotfix package.

back to the top
When you are working in a multi-user environment and you connect to an instance of Microsoft SQL Server 2000 that is running on a symmetric multi-processor (SMP) computer, an access violation exception may occur when you try to modify the data in a SQL Server table.

This behavior may occur when all the following conditions are true:
  • Multiple users try to perform data modification operations such as an UPDATE operation on the same SQL Server table at the same time.
  • One or more triggers are defined on the SQL Server table that corresponds to the data modification operations.
  • One or more triggers access the inserted table, the deleted table, or both.
The occurrence of this behavior depends on the time difference between the data modification operation and the log scan operation. The time difference is small. Therefore, this behavior does not occur frequently.

For a list of previous hotfixes, see the "Microsoft SQL Server 2000 post-Service Pack 3 or Microsoft SQL Server 2000 post-Service Pack 3a hotfixes" section in the following Microsoft Knowledge Base article:
290211 How to obtain the most recent SQL Server 2000 service pack
back to the top

Service pack information

To 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 How to obtain the latest SQL Server 2000 service pack

Hotfix information


This hotfix requires Microsoft SQL Server 2000 Service Pack 3 (SP3) or Microsoft SQL Server 2000 Service Pack 3a (SP3a). For information about how to obtain SQL Server 2000 SP3 or SQL Server 2000 SP3a, see the following article in the Microsoft Knowledge Base:

290211 How to obtain the most recent SQL Server 2000 Service Pack
back to the top

Restart information

You do not have to restart your computer after you apply this hotfix.

back to the top

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix 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   -------------------------------------------------------------------------   15-Jul-2004  16:12  2000.80.961.0     664,128  Autoplt.dll   15-Jul-2004  16:27  2000.80.961.0      78,400  Console.exe   15-Jul-2004  16:44  2000.80.961.0     315,968  Custtask.dll   15-Jul-2004  16:12  2000.80.961.0      33,340  Dbmslpcn.dll   08-Apr-2004  09:12                    786,432  Distmdl.ldf   08-Apr-2004  09:12                  2,359,296  Distmdl.mdf   10-Oct-2003  06:18                        180  Drop_repl_hotfix.sql   15-Jul-2004  16:40  2000.80.961.0   1,905,216  Dtspkg.dll   15-Jul-2004  16:37  2000.80.961.0     528,960  Dtspump.dll   15-Jul-2004  16:53  2000.80.961.0   1,557,052  Dtsui.dll   15-Jul-2004  16:52  2000.80.961.0     639,552  Dtswiz.dll   10-Oct-2003  06:18                    747,927  Instdist.sql   10-Oct-2003  06:18                      1,581  Inst_repl_hotfix.sql   15-Jul-2004  16:59  2000.80.961.0     352,828  Isqlw.exe   15-Jul-2004  16:53  2000.80.961.0      82,492  Itwiz.exe   15-Jul-2004  16:11  2000.80.961.0      90,692  Msgprox.dll   19-May-2004  11:13  8.11.40209.0      209,408  Mssdi98.dll   15-Jul-2004  16:14  2000.80.961.0      62,024  Odsole70.dll   15-Jul-2004  16:32  2000.80.961.0      25,144  Opends60.dll   15-Jul-2004  16:13  2000.80.961.0      57,904  Osql.exe   15-Jul-2004  16:41  2000.80.961.0     279,104  Pfutil80.dll   10-Oct-2003  06:07                    550,780  Procsyst.sql   08-Apr-2004  09:12                     12,305  Qfe469315.sql   08-Apr-2004  09:12                     19,195  Qfe469571.sql   15-Jul-2004  17:43                  1,105,167  Replmerg.sql   15-Jul-2004  16:21  2000.80.961.0     221,768  Replprov.dll   15-Jul-2004  16:23  2000.80.961.0     307,784  Replrec.dll   15-Jul-2004  16:14  2000.80.961.0     159,813  Replres.rll   10-Oct-2003  06:18                  1,087,150  Replsys.sql   10-Oct-2003  06:18                    986,603  Repltran.sql   15-Jul-2004  16:27  2000.80.961.0     287,304  Rinitcom.dll   15-Jul-2004  16:12  2000.80.961.0      78,416  Sdiclnt.dll   15-Jul-2004  16:01  2000.80.961.0      66,112  Semmap.dll   15-Jul-2004  16:06  2000.80.961.0      57,916  Semnt.dll   15-Jul-2004  16:50  2000.80.961.0     492,096  Semobj.dll   15-Jul-2004  16:45  2000.80.961.0     172,032  Semobj.rll   15-Jul-2004  16:20  2000.80.961.0      53,832  Snapshot.exe   13-Jul-2004  08:29                    117,834  Sp3_serv_uni.sql   15-Jul-2004  16:06  2000.80.961.0      28,672  Sqlagent.dll   15-Jul-2004  16:10  2000.80.961.0     311,872  Sqlagent.exe   15-Jul-2004  16:16  2000.80.961.0     168,001  Sqlakw32.dll   15-Jul-2004  16:16  2000.80.961.0      33,344  Sqlctr80.dll   15-Jul-2004  16:52  2000.80.961.0   4,215,360  Sqldmo.dll   15-Jul-2004  16:19                     25,172  Sqldumper.exe   15-Jul-2004  16:02  2000.80.961.0      28,672  Sqlevn70.rll   15-Jul-2004  16:22  2000.80.961.0     156,224  Sqlmaint.exe   15-Jul-2004  16:25  2000.80.961.0     180,792  Sqlmap70.dll   15-Jul-2004  16:50  2000.80.961.0     188,992  Sqlmmc.dll   15-Jul-2004  16:46  2000.80.961.0     479,232  Sqlmmc.rll   15-Jul-2004  16:44  2000.80.961.0     401,984  Sqlqry.dll   15-Jul-2004  16:23  2000.80.961.0      57,920  Sqlrepss.dll   15-Jul-2004  16:16  2000.80.961.0   7,512,640  Sqlservr.exe        15-Jul-2004  16:04  2000.80.961.0     590,396  Sqlsort.dll         15-Jul-2004  16:24  2000.80.961.0      45,644  Sqlvdi.dll   15-Jul-2004  16:23  2000.80.961.0     106,588  Sqsrvres.dll   15-Jul-2004  16:12  2000.80.961.0      33,340  Ssmslpcn.dll   15-Jul-2004  16:13  2000.80.961.0      82,492  Ssnetlib.dll   15-Jul-2004  16:30  2000.80.961.0      25,148  Ssnmpn70.dll   15-Jul-2004  16:25  2000.80.961.0     123,456  Stardds.dll   15-Jul-2004  16:26  2000.80.961.0     158,240  Svrnetcn.dll   15-Jul-2004  16:26  2000.80.961.0      76,416  Svrnetcn.exe   15-Jul-2004  16:30  2000.80.961.0      53,808  Ums.dll   15-Jul-2004  16:27  2000.80.961.0      98,872  Xpweb70.dll

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
back to the top
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

back to the top
More information
For additional information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For additional information about the terminology that Microsoft uses when correcting software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684Description of the standard terminology that is used to describe Microsoft software updates

Stack information

When this behavior occurs, you may notice a short stack dump that is similar to the following in the SQL Server error log file:

* Short Stack Dump* 00000000004ACA40 Module(sqlservr+00000000000ACA40) (LC::Copy+00000000000000B0)* 00000000004ABDC0 Module(sqlservr+00000000000ABDC0) (LogMgr::LogBlockReadAheadAsync+0000000000000160)* 0000000000716D80 Module(sqlservr+0000000000316D80) (LogIterForward::ReadLog+0000000000000180)* 00000000007185D0 Module(sqlservr+00000000003185D0) (LogIterForward::TryLogReadAhead+0000000000000260)* 0000000000717170 Module(sqlservr+0000000000317170) (LogIterForward::GetNextBlock+0000000000000190)* 0000000000717C70 Module(sqlservr+0000000000317C70) (LogIterForward::GetNext+00000000000001C0)* 000000000105D110 Module(sqlservr+0000000000C5D110) (RowsetLogScan::GetNextRows+0000000000000250)* 00000000004F1E70 Module(sqlservr+00000000000F1E70) (CQScanRowset::GetRowWithPrefetch+0000000000000330)* 00000000004F2010 Module(sqlservr+00000000000F2010) (CQScanRowset::GetRow+00000000000000E0)* 0000000000458C50 Module(sqlservr+0000000000058C50) (CQueryScan::GetRow+00000000000002F0)* 00000000004545C0 Module(sqlservr+00000000000545C0) (CStmtQuery::ErsqExecuteQuery+00000000000006F0)* 0000000000472550 Module(sqlservr+0000000000072550) (CStmtAssignWithQuery::XretExecute+0000000000000310)* 0000000000472220 Module(sqlservr+0000000000072220) (CMsqlExecContext::ExecuteStmts+0000000000000CB0)* 000000000044F480 Module(sqlservr+000000000004F480) (CMsqlExecContext::Execute+0000000000000810)* 000000000044F280 Module(sqlservr+000000000004F280) (CSQLSource::Execute+00000000000003C0)* 00000000014BA680 Module(sqlservr+00000000010BA680) (ExecTrigger+0000000000000210)* 00000000014BDAF0 Module(sqlservr+00000000010BDAF0) (ExecAfterTrigs+0000000000000380)* 00000000009EF910 Module(sqlservr+00000000005EF910) (CStmtDML::XretExecuteNormal+0000000000002150)* 00000000004816A0 Module(sqlservr+00000000000816A0) (CMsqlExecContext::ExecuteStmts+0000000000000BB0)* 000000000044F480 Module(sqlservr+000000000004F480) (CMsqlExecContext::Execute+0000000000000810)* 000000000044F280 Module(sqlservr+000000000004F280) (CSQLSource::Execute+00000000000003C0)* 00000000015734B0 Module(sqlservr+00000000011734B0) (ExecuteSql+00000000000004D0)* 0000000001540C90 Module(sqlservr+0000000001140C90) (CSpecProc::ExecuteSpecial+0000000000000730)* 0000000001541F50 Module(sqlservr+0000000001141F50) (CSpecProc::Execute+00000000000001F0)* 00000000009DD390 Module(sqlservr+00000000005DD390) (execrpc+0000000000001250)* 0000000000452A30 Module(sqlservr+0000000000052A30) (process_commands+0000000000000760)* 0000000000404240 Module(sqlservr+0000000000004240) (ProcessWorkRequests+0000000000000A00)* 0000000000726430 Module(sqlservr+0000000000326430) (ThreadStartRoutine+0000000000000150)* 000006FB7FAFE230 Module(msvcrt+000000000005E230) (tanhf+0000000000054550)* 0000000077D24400 Module(kernel32+0000000000094400) (GetDateFormatW+0000000000070070)

back to the top

Article ID: 873446 - Last Review: 01/17/2015 08:47:28 - Revision: 3.0

  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Workgroup Edition
  • kbnosurvey kbarchive kbsqlclient kbserver kbclientserver kbclient kbbug kbfix kbsqlserv2000presp4fix kbhotfixserver kbqfe KB873446