KB3168740 - An access violation occurs when you execute two parent packages that run the same child package in parallel in SQL Server 2014 or 2016

Applies To
SQL Server 2014 Business Intelligence - duplicate (do not use) SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Enterprise Core - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use) SQL Server 2014 Web - duplicate (do not use) SQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use)

Symptoms

Consider the following scenario:

  • You use SQL Server Integration Services (SSIS) with SQL Server 2014 or 2016.
  • You create two SSIS packages that both run the same child package.
  • The child package contains a connection string that is specified by an expression.
  • You execute those two parent packages in parallel.

In this scenario, a race condition that causes an access violation may occur.

Resolution

This problem was fixed in the following cumulative updates for SQL Server:

Cumulative Update 8 for SQL Server 2014 Service Pack 1
        
        Cumulative update 2 for SQL Server 2014 SP2
        
        Cumulative Update 2 for SQL Server 2016
      

About cumulative updates 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:

Latest cumulative update for SQL Server 2014
        
        Latest cumulative update for SQL Server 2016
        
      

Status

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

References

Learn about the terminology Microsoft uses to describe software updates.