Article ID: 914298 - Last Review: November 2, 2007 - Revision: 2.4 FIX: You may receive an error message, and the SQL Server process may crash when you copy or transfer SQL Server 2000 data
BUG #: 313 (SQL Hotfix) BUG #: 473650 (SQL Server 8.0) BUG #: 474273 (SQL Server 8.0) BUG #: 474582 (SQL Server 8.0) BUG #: 474886 (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. On This PageSUMMARYThis article describes the following about this hotfix release:
SYMPTOMSWhen you copy or transfer Microsoft SQL Server 2000 data by using the BULK INSERT (Transact-SQL) command and a COM component such as Full Text Search or SQLMail, you may experience one of the following problems. Additionally, one of these problems may occur when a third-party COM component executes in SQL Server memory space.
When this problem occurs, the SQL Server process may crash. WORKAROUNDTo avoid this problem, use either the bulk copy program or Data Transformation Services (DTS) to import the data. To find more information about these options, refer to SQL Server 2000 Books Online, available from the following Microsoft Web site:http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
(http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx)
RESOLUTIONThe 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: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Prerequisites
894905
(http://support.microsoft.com/kb/894905/
)
Cumulative list of the hotfixes that are available for SQL Server 2000 Service Pack 4
Restart informationYou do not have to restart the computer after you apply this hotfix.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 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. 32-bit hotfixCollapse this table
64-bit hotfixCollapse this table
64-bit hotfix for Itanium processorsCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONYou may notice assertions that have the following type of stack in the error log: 0322abb4 410733d8 sqlservr!utassert_fail+0x345 0322ac04 41072b0a ums!UmsScheduler::CheckForIoCompletion+0x58 0322ac1c 004023c4 ums!UmsScheduler::Suspend+0x4a 0322ac48 00402406 sqlservr!upyield+0x7e 0322ac5c 00403616 sqlservr!ExecutionContext::SmartYield+0x29 0322ac7c 00405bcd sqlservr!SDES::GetPage+0x26 0322ace8 00405e94 sqlservr!SearchIndex+0x1d6 0322adb4 00405f07 sqlservr!prepscan+0x2bc 0322ae30 0040612d sqlservr!LinkedPageSupplier::FirstPage+0x46 0322ae84 00406180 sqlservr!LinkedPageSupplier::GetNextPage+0xd1 0322aedc 00448e05 sqlservr!SDES::GetBiDi+0x1a0 0322af2c 00448f8b sqlservr!CSysScan::FGetNext+0x8b 0322af44 00471d15 sqlservr!CSysScan::StartScan+0x183 0322afe8 005fda12 sqlservr!CIndexScan::FFindById+0xff 0322ba08 00659269 sqlservr!StartXactForSysIndexesUpdate+0x11a 0322e9b4 00776604 sqlservr!updatestats+0xcf7 0322ea74 00415d04 sqlservr!CStmtUpdStats::XretExecute+0x20f 0322eae0 00416214 sqlservr!CMsqlExecContext::ExecuteStmts+0x446 0322eb38 00415f28 sqlservr!CMsqlExecContext::Execute+0x255 0322eb8c 0050bcef sqlservr!CSQLSource::Execute+0x39a 0322f17c 0050bb13 sqlservr!CStmtExec::XretLocalExec+0x1bc 0322f754 00415d04 sqlservr!CStmtExec::XretExecute+0x46b 0322f7c0 00416214 sqlservr!CMsqlExecContext::ExecuteStmts+0x446 0322f818 00415f28 sqlservr!CMsqlExecContext::Execute+0x255 0322f86c 0049c32e sqlservr!CSQLSource::Execute+0x39a 0322fa80 0049c46a sqlservr!language_exec+0x451 0322ff00 41075309 sqlservr!process_commands+0x13f 0322ff70 41074978 ums!ProcessWorkRequests+0x2d9 0322ff84 7c34940f ums!ThreadStartRoutine+0x98 0322ffb8 77e66063 msvcr71!_threadstart+0x6c 0322ffec 00000000 kernel32!BaseThreadStart+0x34 SQL Server Assertion: File: <umsio.cpp>, line=563 Failed Assertion = 'm_busyCnt == 1'. You may also notice an access violation that has the following type of stack: 089edfb8 0098d962 sqlservr!LockOwner::DescribeForSyslocks+0x7e 089edfd4 0098e4b7 sqlservr!LockHashSlot::GetNextRowInFakeTbl+0x176 089edff0 0098e570 sqlservr!LockManager::GetNextRowInFakeTbl+0x94 089ee008 00570b9e sqlservr!SyslockScan::GetNextRow+0x4d 089ee020 0042c22f sqlservr!FakeSystemRowset::FetchNextRow+0x4f 089ee04c 004fdbd0 sqlservr!CQScanRowset::GetRowWithPrefetch+0x3e 089ee06c 0050873c sqlservr!CQScanTableScan::GetRow+0x6b 089ee090 00508798 sqlservr!CQScanSort::BuildSortTable+0x12c ....(removed for brevity) 089eea7c 00418173 sqlservr!CStmtExecStr::XretExecute+0x4ec 089eeae8 00418579 sqlservr!CMsqlExecContext::ExecuteStmts+0x446 089eeb40 00418397 sqlservr!CMsqlExecContext::Execute+0x255 089eeb94 0051f75b sqlservr!CSQLSource::Execute+0x39a 089ef184 0051f57f sqlservr!CStmtExec::XretLocalExec+0x1bc 089ef754 00418173 sqlservr!CStmtExec::XretExecute+0x46b 089ef7c0 00418579 sqlservr!CMsqlExecContext::ExecuteStmts+0x446 089ef818 00418397 sqlservr!CMsqlExecContext::Execute+0x255 089ef86c 004e7db1 sqlservr!CSQLSource::Execute+0x39a 089efa80 004e7eed sqlservr!language_exec+0x451 089eff00 41071a4c sqlservr!process_commands+0x13f 089eff70 41072743 ums!ProcessWorkRequests+0x2d9 089eff84 7c34940f ums!ThreadStartRoutine+0x98 089effb8 77e66063 msvcr71!_threadstart+0x6c 089effec 00000000 kernel32!BaseThreadStart+0x34 " For more information, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
