SQL Server crashes with an access violation when you use the TRY…CATCH construct for bulk copy

Consider the following scenario:
  • You perform a bulk copy operation in SQL Server 2012 or 2014.
  • The operation triggers a call to a common language runtime (CLR) function.
  • The CLR function executes a Transact-SQL statement that contains a TRY…CATCH construct.

In this scenario, SQL Server 2012 crashes with an access violation . Additionally, a dump file is generated in the SQL Server error log.

Update information

This issue is fixed in the following cumulative updates for SQL Server:

Cumulative Update 5 for SQL Server 2012 Service Pack 3

Cumulative update 2 for SQL Server 2014 SP2

Recommendation: Install the latest cumulative update for SQL Server

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.

Article ID: 3184099 - Last Review: 10/18/2016 03:27:00 - Revision: 3.0

Microsoft SQL Server 2012 Developer, Microsoft SQL Server 2012 Enterprise, Microsoft SQL Server 2012 Enterprise Core, Microsoft SQL Server 2012 Standard

  • kbqfe kbfix kbexpertiseinter kbsurveynew KB3184099