FIX: You may receive an access violation when you perform a bulk copy operation in SQL Server 2005

This article has been archived. It is offered "as is" and will no longer be updated.
Bug #: 50000900 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2005 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 2005 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 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 perform a bulk copy operation in Microsoft SQL Server 2005, you may receive an access violation. For example, this problem may occur you run the SELECT INTO statement. This problem occurs if the following conditions are true:
  • You are running the x86 version of SQL Server 2005.
  • You have the Address Windowing Extensions (AWE) option enabled on the server.
Resolution

Hotfix information

A 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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: 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

To apply this hotfix, you must have SQL Server 2005 Service Pack 2 installed on the computer. For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005

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 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 nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3155.0296,30413-Mar-200714:12x86
Mssqlsystemresource.ldfNot applicable524,28813-Mar-200711:11Not applicable
Mssqlsystemresource.mdfNot applicable40,173,56813-Mar-200711:11Not applicable
Rdistcom.dll2005.90.3155.0644,46413-Mar-200714:12x86
Msmdlocal.dll9.0.3155.015,930,22413-Mar-200714:12x86
Sqlaccess.dll2005.90.3155.0350,57613-Mar-200714:12x86
Sqlservr.exe2005.90.3155.029,192,56013-Mar-200714:12x86
Workaround
To work around this problem, disable the AWE option by using the sp_configure system stored procedure. For more information, visit the following Microsoft Developer Network (MSDN) Web site:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
When this problem occurs, you may receive an access violation that resembles the following:

020E00BC sqlservr!BPool::WaitForMinimallyLogged+0x106                                                                             021F092B sqlservr!PageFlushManager::FlushAll+0xcc021EF209 sqlservr!ParNestedXdes::Commit+0x12012E7F09 sqlservr!CQueryScan::CommitSubXacts+0x3b012E672F sqlservr!CXStmtQuery::ShutdownNormal+0xcb01035529 sqlservr!CXStmtQuery::ErsqExecuteQuery+0x91f01056A5E sqlservr!CXStmtDML::XretDMLExecute+0x28401C51AA6 sqlservr!CXStmtSelectInto::XretSelectIntoExecute+0x3bf01C51C52 sqlservr!CXStmtSelectInto::XretExecute+0xd7 01023B03 sqlservr!CMsqlExecContext::ExecuteStmts<1,1>+0x36101025B6D sqlservr!CMsqlExecContext::FExecute+0x55b01024D6E sqlservr!CSQLSource::Execute+0x74e01C30FDA sqlservr!CStmtExecStr::XretExecStrExecute+0x3ef                                                                         01C2F78B sqlservr!CXStmtExecStr::XretExecute+0x23                                                                          01023B03 sqlservr!CMsqlExecContext::ExecuteStmts<1,1>+0x361   01025B6D sqlservr!CMsqlExecContext::FExecute+0x55b01024D6E sqlservr!CSQLSource::Execute+0x74e0133E906 sqlservr!CStmtExecProc::XretLocalExec+0x1f60133E77D sqlservr!CStmtExecProc::XretExecExecute+0x5520133E612 sqlservr!CXStmtExec::XretExecute+0x2301023B03 sqlservr!CMsqlExecContext::ExecuteStmts<1,1>+0x361 01025B6D sqlservr!CMsqlExecContext::FExecute+0x55b01024D6E sqlservr!CSQLSource::Execute+0x74e0133E906 sqlservr!CStmtExecProc::XretLocalExec+0x1f60133E77D sqlservr!CStmtExecProc::XretExecExecute+0x5520133E612 sqlservr!CXStmtExec::XretExecute+0x2301023B03 sqlservr!CMsqlExecContext::ExecuteStmts<1,1>+0x361 01025B6D sqlservr!CMsqlExecContext::FExecute+0x55b01024D6E sqlservr!CSQLSource::Execute+0x74e0103B704 sqlservr!process_request+0x2e3010381D5 sqlservr!process_commands+0x2e001006888 sqlservr!SOS_Task::Param::Execute+0xe2010069AE sqlservr!SOS_Scheduler::RunTask+0xb9010066BE sqlservr!SOS_Scheduler::ProcessTasks+0x141014656FD sqlservr!SchedulerManager::WorkerEntryPoint+0x1ab014655F4 sqlservr!SystemThread::RunWorker+0x7f014652BC sqlservr!SystemThreadDispatcher::ProcessWorker+0x24601465459 sqlservr!SchedulerManager::ThreadEntryPoint+0x143781329AA Module(MSVCR80+000029AA)78132A36 Module(MSVCR80+00002A36)
For more 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 more information about software update terminology, 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
This hotfix is also included in the cumulative update package (build 3161) for SQL Server 2005 Service Pack 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935356 Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available
Properties

Article ID: 933549 - Last Review: 01/16/2015 02:32:00 - Revision: 3.0

  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard Edition
  • kbnosurvey kbarchive kbautohotfix kbsql2005engine kbfix kbexpertiseadvanced kbHotfixServer kbqfe KB933549
Feedback