FIX: Analysis Services Execute DDL task fails to impersonate the user context to the remote Analysis services instance in SQL Server 2017 and 2019

Applies to: SQL Server 2019 on WindowsSQL Server 2017 Developer on WindowsSQL Server 2017 Enterprise Core on Windows

Symptoms


Assume that you upgrade your Microsoft SQL Server 2017 or 2019 instance to any version later than Cumulative Update 4 (CU4). When you run a SQL Server Integration Services (SSIS) package that connects to a remote Analysis Services instance under the SQL Server Agent Job, you notice that the Analysis Services Execute DDL task fails to impersonate the user context to the remote Analysis services instance. 

Note The default underlying connection will be made by using AMO. AMO does not support impersonation by specifying a user or password for the connection string. Instead, if this scenario is required (for example, by using SQL Server Agent to connect to the Analysis Services instance), the Connection Manager has to specify "DataSourceInfo=MSOLAP" in the connection string.

Status


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

Resolution


This issue is fixed in the following cumulative updates for SQL Server:
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:

Workaround


To work around the issue, you can use the following methods:
  1. You can use a SQL Server proxy account to run the SQL Server Agent job.
  2. You can use the SQL Server Agent service account that has permissions on the target Analysis Services server.

References


Learn about the terminology that Microsoft uses to describe software updates.