Article ID: 875445
Article Last Modified on 11/2/2007
APPLIES TO
- 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 Enterprise Edition
- Microsoft SQL Server 2000 Workgroup Edition
- Microsoft SQL Server 2000 Desktop Engine (Windows)
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Enterprise Edition 64-bit
Bug #: 470792 (SQL Server 8.0)
Article contents
SUMMARY
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.
SYMPTOMS
When you try to access Microsoft SQL Server on a computer that is running under low-memory conditions, an access violation may occur.
This problem may also occur when you try to perform an operation such as running a stored procedure on an instance of SQL Server if the computer that is running SQL Server is running under low-memory conditions.
After the access violation exception occurs, SQL Server may stop responding.
This problem occurs if all the following are true:
- The process thread, on which the access violation occurs, is not User Mode Scheduler (UMS) enabled.
- The process thread, on which the access violation occurs, does not contain an Execution Context.
- The BPool space is used up. Therefore, SQL Server cannot steal the memory.
Note The network process threads such as net_readdata and wait_for_client_connects are not UMS enabled and they may not contain an Execution Context. Therefore, the network threads may experience an access violation, and SQL Server may stop responding.
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
RESOLUTION
NoteThis fix will not correct the low-memory condition problem completely. After you apply this fix, the computer that is running SQL Server may work correctly, even when the memory space is low.
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
Prerequisites
This hotfix requires Microsoft SQL Server 2000 Service Pack 3 (SP3). For information about how to obtain SQL Server 2000 SP3, see the following article in the Microsoft Knowledge Base:
290211 How to obtain the most recent SQL Server 2000 Service Pack
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
WORKAROUND
To work around this problem, you may be able to diagnose the low-memory condition and resolve the problem. For example, you can use the Transact-SQL DBCC MEMORYSTATUS statement to troubleshoot the issues that relate to a low-memory condition.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
271624 INF: Using DBCC MEMORYSTATUS to Monitor SQL Server Memory Usage
STATUS
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:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Stack information
When this behavior occurs, you may see a stack dump file that contains a message that is similar to the following:
* Short Stack Dump * 00444449 Module(sqlservr+00044449) (ExecutionContext::SmartYield+00000007) * 0056E83D Module(sqlservr+0016E83D) (BufIter::NextBuf+00000051) * 0056E8CC Module(sqlservr+0016E8CC) (BPool::CalculateBufferStats+00000029) * 0084DF54 Module(sqlservr+0044DF54) (CMemManager::DumpMemoryStatus+00000046) * 0084DB49 Module(sqlservr+0044DB49) (DumpMemoryStatus+0000000B) * 0082C95A Module(sqlservr+0042C95A) (BPool::Map+000001CC) * 0082CAFB Module(sqlservr+0042CAFB) (BPool::Steal+00000282) * 00416E34 Module(sqlservr+00016E34) (CMemManager::PbAllocBPool+00000018) * 00416DCB Module(sqlservr+00016DCB) (CMemManager::PbRequestPages+000000A5) * 00416ED5 Module(sqlservr+00016ED5) (CFreePageMgr::PbGetNewPages+00000046) * 00416E8E Module(sqlservr+00016E8E) (CMemProc::PbGetNewPages+00000011) * 0041F8A8 Module(sqlservr+0001F8A8) (CVarPageMgr::PviNewVarPage+0000002E) * 0040C853 Module(sqlservr+0000C853) (CVarPageMgr::PbAllocate+00000056) * 0040250F Module(sqlservr+0000250F) (CMemObj::Alloc+00000021) * 004024E5 Module(sqlservr+000024E5) (CMemProc::Alloc+0000000F) * 0056BA77 Module(sqlservr+0016BA77) (srv_proc::Init+00000163) * 004FBEBE Module(sqlservr+000FBEBE) (wait_for_client_connects+000000D4) * 7800C9EB Module(MSVCRT+0000C9EB) (beginthread+000000CE) * 77E8B2D8 Module(KERNEL32+0000B2D8) (lstrcmpiW+000000B7)
Additional query words: AV OOM crash hang
Keywords: kbbug kbfix kbqfe kbmemory kbsqlserv2000presp4fix kbhotfixserver KB875445