Article ID: 914384 - View products that this article applies to.
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.
This article describes the following about this hotfix release:
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:
Additionally, the status of the database is set to Suspect. Error messages that resemble the following are logged in the SQL Server ErrorLog file:
[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
For a list of all publicly released SQL Server 2000 Service Pack 4 hotfixes, see the following article in the Microsoft Knowledge Base:
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..
(http://support.microsoft.com/kb/894905/ )Cumulative list of the hotfixes that are available for SQL Server 2000 SP4
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.
The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
PrerequisitesYou 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:
(http://support.microsoft.com/kb/290211/ )How to obtain the latest SQL Server 2000 service pack
Restart requirementYou do not have to restart the computer.
Registry informationYou 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 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.
Collapse this tableExpand this table
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 914384 - Last Review: October 9, 2011 - Revision: 2.0