Oracle source and destination missing in visual studio 2022 after installing Microsoft Connector for Oracle v1.2/1.3

vamsi krishna 0 Reputation points

We are running SSIS packages originally developed for SQL Server 2016 on servers that have been upgraded to SQL Server 2022 (both OS and database engine). The packages use the Attunity Oracle connectors. After the upgrade we attempted to open the packages in Visual Studio 2022, but the Oracle Source and Oracle Destination components do not appear in the Data Flow toolbox.

We have tried the following steps without success:

Installed both the 32‑bit and 64‑bit versions of the Microsoft Connector for Oracle (v1.2 and v1.3) as administrator.

Restarted the SQL Server Integration Services service after each installation.

Confirmed that Visual Studio 2022 has the latest SQL Server Integration Services Projects extension installed.

Despite these steps, the Oracle Source and Destination items are still absent from the Common tab in the SSIS Data Flow toolbox.

  1. What additional configuration or prerequisites are required for the Microsoft Connector for Oracle v1.2/v1.3 to register the Oracle Source and Destination components in Visual Studio 2022 when targeting SQL Server 2022?
  2. To upgrade our existing SSIS packages from SQL Server 2016 to SQL Server 2022 without rebuilding them from scratch, what is the supported migration path for packages that currently use Attunity Oracle connectors?
0 comments No comments
Sign in to comment

Answer recommended by moderator

Akhil Gajavelly 1,830 Reputation points • Microsoft External Staff • Moderator

Hi @Vamsi Krishna ,

Thanks for sharing the error screenshot this actually reveals a different root cause than the Oracle connector itself.

The error Microsoft.DataWarehouse.Interfaces, Version=15.23.0.0 is a VS 2019/SSDT-era assembly. This strongly suggests that leftover SSDT components from an older Visual Studio installation are conflicting with your current environment, causing the SSIS designer itself to fail loading which is why reinstalling the Oracle connectors repeatedly didn't help.

Before anything else, confirm one thing: Your original post mentions VS 2022, but the error screenshot appears to be from VS 2019. Which version are you actually opening the packages in? This matters because the fix differs depending on the answer.

Then follow these steps in order:

  1. Uninstall the SSIS Projects extension from whichever VS version you are using
  2. Repair Visual Studio via the Visual Studio Installer → Repair option
  3. Reinstall the SSIS Projects extension that matches your VS version (v3.16 for VS 2019, appropriate version for VS 2022)
  4. If you have both VS 2019 and VS 2022 installed, check for and remove any leftover SSDT components from the older version as these are known to cause assembly version conflicts

Once the SSIS designer loads cleanly without errors, then revisit the Oracle connector installation. The components will not appear in the toolbox regardless of how many times the connector is reinstalled if the underlying SSIS designer is broken.

The Oracle connector is not your problem right now the SSIS environment is.

Thanks,
Akhil.

0 comments No comments
Sign in to comment

1 additional answer

  1. Akhil Gajavelly 1,830 Reputation points • Microsoft External Staff • Moderator

    Hi @Vamsi Krishna ,

    Thanks for raising this and also thanks to the earlier inputs shared.

    Before replacing any components, try these fixes in order:

    1. Check your SQL Server Edition first The Microsoft Connector for Oracle only works on Enterprise or Developer Edition. Standard Edition is silently unsupported no error is shown.
    2. Install the x86 (32-bit) MSI Visual Studio is a 32-bit host. You must install the 32-bit version of MicrosoftSSISOracleConnector-SQL22-x86.msi alongside the 64-bit one. This is the most common cause of components not appearing in the toolbox.
    3. Downgrade SSIS Projects Extension to v3.16 Extension v4.x has known incompatibility with the Oracle connector. Uninstall your current version and install v3.16 from Microsoft's CDN, then reboot.
    4. Force toolbox population Right-click the toolbox → Choose Items → SSIS Data Flow Items → manually check Oracle Source and Destination.

    For loading your old SQL 2016 packages: Install Attunity Connector v4.0 alongside the Microsoft Connector to open the old packages without errors, then re-map the connection managers to the new Microsoft Oracle Connection Manager.

    Thanks,
    Akhil.

    1. vamsi krishna 0 Reputation points

      👁 20260421_194641

      Hi @Akhil Gajavelly

      This is not working, I tried everything.Sql server is enterprise, I installed both 32 bit and 64bit connector, ssis project extension is 3.16.

      Im getting below error in vs 2019.

    2. Akhil Gajavelly 1,830 Reputation points • Microsoft External Staff • Moderator

      Hi @Vamsi Krishna ,

      Just following up were you able to verify which Visual Studio version is being used and try the suggested SSIS repair/reinstall steps? Since the issue appears related to the SSIS designer environment itself rather than the Oracle connector, confirming whether the designer loads cleanly after the repair would help narrow things down further.

      Feel free to share any update or new error details if the issue still persists.

      Thanks,
      Akhil.

    3. Akhil Gajavelly 1,830 Reputation points • Microsoft External Staff • Moderator

      Hi @vamsi krishna ,

      Just checking in to see if you had a chance to review the suggested SSIS repair/reinstall steps and verify the Visual Studio version being used.

      If the issue is still occurring, please share whether the SSIS designer opens normally after the repair or if any updated error messages are being displayed. That information would help the community narrow down whether this is an SSIS extension issue or something specific to the development environment configuration.

      Thanks,
      Akhil.

    Sign in to comment
Sign in to answer

Your answer