FIX: You receive an access violation error message when you try to perform a read of a large binary large object column in SQL Server 2000 (917972)
The information in this article applies to:
- Microsoft SQL Server 2000 Personal Edition
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Enterprise Edition
- Microsoft SQL Server 2000 Standard Edition
Bug #: 50000123 (SQL Hotfix) Bug #: 50000157 (SQL Hotfix) Bug #: 473454 (SQL Server 8.0) Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release. SUMMARYThis article describes the following about this hotfix
release:
- The issues that are fixed by the hotfix package
- The prerequisites for installing the hotfix
package
- Whether you must restart the computer after you install the
hotfix package
- Whether you must make any registry changes
- The files that are contained in the hotfix
package
SYMPTOMSWhen you try to perform a read of a large
binary large object (BLOB) column in Microsoft SQL Server 2000,
you may experience one of the following problems:
- You receive an access violation error message.
- The client application connection that performs
the read unexpectedly ends.
Note The text data type, the ntext data type, and the image data type are examples of large binary large objects. This problem may occur if the following conditions are true:
- You have one connection that performs the read of the large
binary large object column.
- The read of the large binary large object column uses the
READ_UNCOMMITTED isolation level or uses the
NOLOCK query hint.
Note A read that uses the
READ_UNCOMMITTED isolation level is called a dirty read.
- You have a second connection that changes the contents of
the large binary large object column.
- The changes to the contents of the large binary large object column
reduce the size of the large binary large object column.
For a list of all publicly released SQL Server 2000
post-Service Pack 4 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base: 894905 Cumulative list of the hotfixes that are available for SQL Server 2000 Service Pack 4
RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. Prerequisites- Microsoft SQL Server 2000 Service Pack 4 (SP4)
For information about how to obtain SQL Server 2000 SP4, 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
Restart information You do not have to restart the computer after you apply this
hotfix. Registry information You do not have to change the registry. Hotfix file informationThis 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 file attributes) 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 item in Control Panel.SQL Server 2000, 32-bit hotfix |
Dtsui.dll | 2000.80.2194.0 | 1,593,344 | 21-Apr-2006 | 15:05 | x86 | Impprov.dll | 2000.80.2194.0 | 102,400 | 21-Apr-2006 | 15:05 | x86 | Msgprox.dll | 2000.80.2194.0 | 94,208 | 21-Apr-2006 | 15:05 | x86 | Msrpjt40.dll | 4.10.9424.0 | 188,473 | 24-Jan-2006 | 08:13 | x86 | Mssdi98.dll | 8.11.50523.0 | 239,104 | 06-Jun-2005 | 22:46 | x86 | Ntwdblib.dll | 2000.80.2194.0 | 290,816 | 21-Apr-2006 | 15:05 | x86 | Odsole70.dll | 2000.80.2194.0 | 69,632 | 21-Apr-2006 | 15:05 | x86 | Osql.exe | 2000.80.2194.0 | 57,344 | 20-Apr-2006 | 20:17 | x86 | Pfclnt80.dll | 2000.80.2194.0 | 430,080 | 21-Apr-2006 | 15:05 | x86 | Replmerg.exe | 2000.80.2194.0 | 163,840 | 20-Apr-2006 | 20:32 | x86 | Replprov.dll | 2000.80.2194.0 | 237,568 | 21-Apr-2006 | 15:05 | x86 | Replrec.dll | 2000.80.2194.0 | 315,392 | 21-Apr-2006 | 15:05 | x86 | Replsub.dll | 2000.80.2194.0 | 270,336 | 21-Apr-2006 | 15:05 | x86 | Semexec.dll | 2000.80.2194.0 | 856,064 | 21-Apr-2006 | 15:05 | x86 | Sqlagent.exe | 2000.80.2194.0 | 323,584 | 20-Apr-2006 | 19:51 | x86 | Sqldiag.exe | 2000.80.2194.0 | 118,784 | 20-Apr-2006 | 21:32 | x86 | Sqldmo.dll | 2000.80.2194.0 | 4,362,240 | 21-Apr-2006 | 15:05 | x86 | Sqlevn70.rll | 2000.80.2194.0 | 45,056 | 21-Apr-2006 | 15:05 | Not
Applicable | Sqlfth75.dll | 2000.80.2194.0 | 102,400 | 20-Apr-2006 | 20:14 | x86 | Sqlservr.exe | 2000.80.2194.0 | 9,162,752 | 20-Apr-2006 | 23:26 | x86 | Sqlsort.dll | 2000.80.2194.0 | 589,824 | 21-Apr-2006 | 15:05 | x86 | Stardds.dll | 2000.80.2194.0 | 176,128 | 21-Apr-2006 | 15:05 | x86 | Svrnetcn.dll | 2000.80.2194.0 | 110,592 | 21-Apr-2006 | 15:05 | x86 | Ums.dll | 2000.80.2194.0 | 35,328 | 21-Apr-2006 | 15:05 | x86 | Xpstar.dll | 2000.80.2194.0 | 311,296 | 21-Apr-2006 | 15:05 | x86 |
WORKAROUNDTo work around this problem, use one of the following
methods: - Use the READ_COMMITTED isolation level to
perform the read of the large binary large object column.
- Do not use the NOLOCK query hint to
perform the read of the large binary large object column.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 9/22/2006 |
---|
Keywords: | kbBug kbfix kbtshoot kbQFE kbhotfixserver kbpubtypekc KB917972 kbAudITPRO kbAudDeveloper |
---|
|