FIX: “A connection cannot be made” error when SSIS package uses a parameterized connection manager in SQL Server 2016 and 2017

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


Assume that you use Microsoft SQL Server Integration Services (SSIS) packages in Microsoft SQL Server 2016 and 2017. You have a SSIS package that contains the Execute SQL task that uses parameterized SQL statements in Connection Manager to copy connection string details from a project parameter to a user variable.

When another task whose connection string is dynamically populated from the user variable, the task fails. Additionally, you receive error messages that resembles the following:


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

Cumulative Update 13 for SQL Server 2017

Cumulative Update 4 for SQL Server 2016 Service Pack 2


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


Learn about the terminology Microsoft uses to describe software updates.