SSIS Projects extension for VS2022 troubleshooting guide

Article
10/04/2023

Applies to: SQL Server Azure SQL Database Azure Synapse Analytics

Important

You can download the SSIS from the Visual Studio Marketplace.

Visit https://techcommunity.microsoft.com/t5/SQL-Server-Integration-Services/bg-p/SSIS for the latest information, tips, news, and announcements about SSIS directly from the product team. Integration Services (SSIS) extension release notes are listed on the extension marketplace.

Component Download

To design packages using Oracle and Teradata connectors and targeting an earlier version of SQL Server prior to SQL 2019, in addition to the Microsoft Oracle Connector and Microsoft Teradata Connector, you need to also install the corresponding version of Microsoft Connector for Oracle and Teradata by Attunity.
Since version 3.3, Power Query Source for SQL Server 2017-2022 have been excluded from the installation of this product. To continue using this component, manually download and install them by yourselves. Here are the download links: Power Query Source for SQL Server 2017-2022

Common Issues

SSIS Execute Package Task doesn't support debugging when ExecuteOutOfProcess is set to True.
Third party components aren't supported yet.
Sometimes this product or Visual Studio Tools for Applications 2022 may be somehow deleted during VS instance upgrade. If your existing SSIS projects cannot be loaded, try to repair this product via control panel. If VS doesn't pop up when clicking on "Edit Script", try to repair VSTA 2022 via control panel.
SSDT side by side issue. SQL Server Analysis Services and SQL Server Reporting Services extensions can now work side-by-side with this extension in VS2022 17.4 and previous version. The workaround is to download Visual Studio 2022 17.5 Preview 2 or later.
The SQL Server Native Client (often abbreviated SNAC) has been removed from SQL Server 2022 (16.x) and SQL Server Management Studio 19 (SSMS). The SQL Server Native Client (SQLNCLI or SQLNCLI11) and the legacy Microsoft OLE DB Provider for SQL Server (SQLOLEDB) are not recommended for new application development. Switch to the new Microsoft OLE DB Driver (MSOLEDBSQL) for SQL Server or the latest Microsoft ODBC Driver for SQL Server going forward. For SQLNCLI that ships as a component of SQL Server Database Engine (versions 2012 through 2019), see this Support Lifecycle exception.
If Oracle, Teradata, or other OOB component is not found after upgrading SSDT, please make sure that the connector for latest SQL Server version is installed.

Known issues

Version 1.0

SQL Server 2016 is not supported as target server version. (Target server versions supported are SQL Server 2017, 2019 and 2022.)
In the context menu (right mouse button) on objects in the project (e.g. the solution, a package) in Visual Studio, many of the entries appear many times. This happens only when Microsoft Analysis Services Projects 2022 is installed together.
Project name in Solution Explorer UI doesn't show target server version as suffix.
Dimension Processing and Partition Processing components are not supported.
DQO related components are not supported.

Version 0.4

Target server versions supported: SQL Server 2017, SQL Server 2019 and SQL Server 2022
Can't design Dimension Processing and Partition Processing.
Can't design DQS related component.
Project name in Solution Explorer UI doesn't show target server version as suffix.

Version 0.3

Target server versions supported: SQL Server 2017, SQL Server 2019 and SQL Server 2022
Can't design Dimension Processing and Partition Processing.
Can't design DQS related component.
Project name in Solution Explorer UI doesn't show target server version as suffix.
Localization and globalization aren't supported.
Can't edit Execute SQL Task when SQL Server 2022 is installed at the same machine
- Edit Execute SQL Task shows error: "'Microsoft.SqlServer.Dts.Tasks.ExecuteSQLTaskExecuteSQLTask, Microsoft.SqlServer.SQLTask, Version-16.0.0.0, Culture-neutral, PublicKeyToken=89845dcd8080cc91' is not registered for use on this computer."
- Workaround: Executing with non-admin user might solve the issue. If not, SQL Server 2022 & VS extension for SSIS have to be installed on separate machines for now. We are working on the fix.

Version 0.2

Target server versions supported: SQL Server 2019 and SQL Server 2022
Can't design Dimension Processing and Partition Processing.
Can't design DQS related component.
Project name in Solution Explorer UI doesn't show target server version as suffix.
Side by side, localization and globalization aren't supported.
Azure-enabled SSIS projects aren't supported
Repair action doesn't take effect. Reinstall it instead.
Logging container can't choose packages.

Version 0.1

Target server versions supported: SQL Server 2019 and SQL Server 2022
Can't design Dimension Processing and Partition Processing.
Can't design DQS related component.
Project name in Solution Explorer UI doesn't show target server version as suffix.
Side by side, localization and globalization aren't supported.
Packages using Oracle and Teradata connectors aren't supported.
Azure-enabled SSIS projects aren't supported.
Logging container can't choose packages.
Right-click Package and select SSIS Import and Export Wizard throws error, workaround: execute Common7\IDE\CommonExtensions\Microsoft\SSIS\160\Binn\DTSWizard.exe
Right-click Package and select Upgrade All Packages throws error, workaround: execute Common7\IDE\CommonExtensions\Microsoft\SSIS\160\Binn\SSISUpgrade.exe

Installation issues

If you install successfully, but the solution shows "incompatible", and "The application isn't installed":

Open Visual Studio -> Extension -> Manage Extensions -> Installed
Enable SSIS extension
Relaunch Visual Studio

If you get an error during installation, and find "Process returned error: 0x80131500" in the log. You can open %temp%\SsdtisSetup folder, search in Microsoft.DataTools.IntegrationServices_{timestamp}_ISVsix.log:

When the error is "Pre-check verification failed with warning(s) : AnotherInstallationRunning.",
- kill MSIExec.exe in task manager, and retry.
When the error is "Object reference not set to an instance of an object.",
- delete the broken instance folder "%ProgramData%\Microsoft\VisualStudio\Packages_Instances<InstallationID>"
When the error is "Error 0x80091007: Failed to verify hash of payload",
- delete C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7 and retry.
When the error isn't in the above list, you can zip %temp%\SsdtisSetup and send the logs to ssistoolsfeedbacks@microsoft.com for troubleshooting.

Offline installation

Follow the below steps to install this product in an offline environment:

Refer to the instructions in Create an offline installation package of Visual Studio for local installation, and make sure the following prerequisites are included:
- Prerequisite ID="Microsoft.VisualStudio.Component.Roslyn.LanguageServices" Version="[17.0,)" DisplayName="C# and Visual Basic"
- Prerequisite ID="Microsoft.VisualStudio.Component.CoreEditor" Version="[17.0,)" DisplayName="Visual Studio core editor"
- Prerequisite ID="Microsoft.Net.Component.4.7.TargetingPack" Version="[17.0,)" DisplayName=".NET Framework 4.7 targeting pack"
Launch the installer of this product and perform the installation, or you can run the installer in quiet mode. Launch the installer with "/?" argument to get more details of the arguments list of the installer.
VS Community doesn't support offline activation. To use this product with VS Community, you must log in to your Microsoft account occasionally in VS Community. If you want to use this product in an offline environment, we recommend you to install this product on VS Professional or Enterprise, which support offline activation via a product key.