FIX: SQL Server 2008 R2 may not accept the client connection request when you perform a bulk insert and an OS error occurs

Article ID: 2703214
Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1) 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 2008 R2 Service Pack 1 (SP1) fix release.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You perform a bulk insert in Microsoft SQL Server 2008 R2.
  • An operating system error occurs that causes the ReadFile command or the CreateFile command to encounter an INVALID_HANDLE error.

    Note
    The ReadFile command and the CreateFile command are used to read and to create the data files or the format files that the Bulk Insert command uses.
  • A client application sends an attention to the instance of SQL Server.
In this scenario, the instance of SQL Server may not accept the client connection request. Additionally, error messages that resemble the following are logged in the SQL Server error log:

Error message 1
Date Time Server Unknown Exception raised by task.

Error message 2
Date Time Server * Access Violation occurred writing address 0000000000000008

Error message 3
Date Time Server ERROR: IO completion routine raised unhandled exception. Major: 29, Minor 5, Severity 25, State 1, IO CompRequest 0x0000000AAF7BB7E0, IO CompKey 0x0000000000000000, Address: 0x00000000026B6FD0
Note You have to restart the instance of SQL Server to recover from this issue.

Cause

This issue occurs because SQL Server does not catch and handle the situation correctly when the OS error is received.

Resolution

Cumulative update information

SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2720425 Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 7 for SQL Server 2008 R2 SP1. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2703282 Cumulative Update package 7 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

Status

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

Properties

Article ID: 2703214 - Last Review: August 1, 2012 - Revision: 2.0
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2703214

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com