Microsoft KB Archive/914384

From BetaArchive Wiki

Article ID: 914384

Article Last Modified on 11/2/2007



APPLIES TO

  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Workgroup Edition




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.

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 the computer after you install the hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package


SYMPTOMS

Consider the following scenario. You perform a bulk copy in a transaction in SQL Server 2000. In the same transaction, you insert data in the same table. When you try to roll back the transaction, you may receive the following error message:

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation. Connection Broken

Additionally, the status of the database is set to Suspect. Error messages that resemble the following are logged in the SQL Server ErrorLog file:

2006-02-02 11:08:19.71 spid14 Stack Signature for the dump is 0xFCDEDADE
2006-02-02 11:08:19.74 spid14 SQL Server Assertion: File: <logscan.cpp>, line=3399 Failed Assertion = 'm_lastLSN == NullLSN || startLSN < m_lastLSN'.
2006-02-02 11:08:19.74 spid14 Location: logscan.cpp:3399 Expression: m_lastLSN == NullLSN || startLSN < m_lastLSN SPID: 14 Process ID: 7252
2006-02-02 11:08:19.74 spid14 Error: 9004, Severity: 23, State: 7
2006-02-02 11:08:19.74 spid14 An error occurred while processing the log for database 'testdb'..
2006-02-02 11:08:19.76 spid14 Error: 3414, Severity: 21, State: 1
2006-02-02 11:08:19.76 spid14 Database 'testdb' (database ID 17) could not recover. Contact Technical Support..

For a list of all publicly released SQL Server 2000 Service Pack 4 hotfixes, see the following article in the Microsoft Knowledge Base:

894905 Cumulative list of the hotfixes that are available for SQL Server 2000 SP4


CAUSE

This problem occurs because SQL Server 2000 cannot roll back a transaction when both logged changes and non-logged changes have been made on the splitting pages.

RESOLUTION

The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:

  • The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.


Note This issue does not occur on systems that use the Intel Itanium processor architecture.

  • The system is running a 64-bit version of the Microsoft Windows Server operating system.
  • The system is running a 32-bit version of SQL Server 2000.

We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

Hotfix information

A 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

You must have Microsoft SQL Server 2000 Service Pack 4 (SP4) installed before you can install this hotfix.

For more information about how to obtain SQL Server 2000 Service Pack 4, 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 requirement

You do not have to restart the computer.

Registry information

You do not have to change the registry.

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 of 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.

File name File version File size Date Time Platform
Dtsui.dll 2000.80.2187.0 1,593,344 09-Mar-2006 04:47 x86
Impprov.dll 2000.80.2187.0 102,400 09-Mar-2006 04:47 x86
Msgprox.dll 2000.80.2187.0 94,208 09-Mar-2006 04:47 x86
Msrpjt40.dll 4.10.9424.0 188,473 23-Jan-2006 16:13 x86
Mssdi98.dll 8.11.50523.0 239,104 06-Jun-2005 06:46 x86
Ntwdblib.dll 2000.80.2187.0 290,816 09-Mar-2006 04:47 x86
Odsole70.dll 2000.80.2187.0 69,632 09-Mar-2006 04:47 x86
Osql.exe 2000.80.2187.0 57,344 09-Mar-2006 02:37 x86
Pfclnt80.dll 2000.80.2187.0 430,080 09-Mar-2006 04:47 x86
Replmerg.exe 2000.80.2187.0 163,840 09-Mar-2006 02:46 x86
Replprov.dll 2000.80.2187.0 237,568 09-Mar-2006 04:47 x86
Replrec.dll 2000.80.2187.0 315,392 09-Mar-2006 04:47 x86
Replsub.dll 2000.80.2187.0 270,336 09-Mar-2006 04:47 x86
Semexec.dll 2000.80.2187.0 856,064 09-Mar-2006 04:47 x86
Sqlagent.exe 2000.80.2187.0 323,584 09-Mar-2006 02:26 x86
Sqldiag.exe 2000.80.2187.0 118,784 09-Mar-2006 03:22 x86
Sqldmo.dll 2000.80.2187.0 4,362,240 09-Mar-2006 04:47 x86
Sqlevn70.rll 2000.80.2187.0 45,056 09-Mar-2006 04:47 Not Applicable
Sqlfth75.dll 2000.80.2187.0 102,400 09-Mar-2006 02:35 x86
Sqlservr.exe 2000.80.2187.0 9,162,752 09-Mar-2006 04:45 x86
Sqlsort.dll 2000.80.2187.0 589,824 09-Mar-2006 04:47 x86
Stardds.dll 2000.80.2187.0 176,128 09-Mar-2006 04:47 x86
Svrnetcn.dll 2000.80.2187.0 110,592 09-Mar-2006 04:47 x86
Ums.dll 2000.80.2187.0 35,328 09-Mar-2006 04:47 x86


STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information, 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


Keywords: kbfix kbexpertiseadvanced kbhotfixserver kbqfe kbpubtypekc KB914384