How can I import a SSIS package to our SSDT?

けたとんしゃん 25 Reputation points
2026-07-05T09:50:19.8366667+00:00

Although a SSIS package is running on our SQLServer2017, we lost that source file. Which is a dtsx file.

Then we plan to migrate everything from SQLServer2017 to 2022, we need to see the design and change some information of this package.

How can I handle this image error I am facing?

HRESULT からの例外:0xC00160AC (Microsoft.SqlServer.DTSRuntimeWrap)

１２

SQL Server Integration Services
0 comments

Answer accepted by question author

Deepesh Dhake 820 Reputation points
2026-07-05T15:53:29.1533333+00:00

I am assuming this is the error: 0xC00160AC (Microsoft.SqlServer.DTSRuntimeWrap) which is a connection/enumeration failure against the legacy Integration Services service (MsDtsServer), which fronts the old Package Store (MSDB + file system). Your "Add Copy of Existing Package" dialog targets that store. But your package is deployed to the SSISDB catalog (Project Deployment Model - visible in your screenshot under Integration Services Catalogs => SSISDB => Projects => Packages). The catalog isn't served through MsDtsServer, so that dialog can't reach it.

You can recover it one of two ways.

Option A - Export the .ispac from SSMS (simplest):

SSMS => connect to the Database Engine on SQL 2017 (not Integration Services).

Integration Services Catalogs => SSISDB => your folder => Projects => right-click the project => Export.

Save the .ispac. It's an OPC zip - rename to .zip and extract to confirm the .dtsx, .params, and .conmgr files are all there.

  • Option B - Import Project Wizard (rebuilds the project directly in SSDT):

Visual Studio => File => New => Project => Integration Services Import Project Wizard.

Source: Integration Services Catalog => server = SQL 2017 instance => browse to the project.

Finish. You get the full project - every package, connection managers, project parameters - open in the designer.

Then the 2017 => 2022 migration:

Open the recovered project in SSDT, make your edits.

Set project TargetServerVersion = SQL Server 2022.

Rebuild → produces a fresh .ispac.

Deploy to the SSIS 2022 catalog side-by-side, validate on 2022.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-07-05T09:50:50.79+00:00

    The running package can be brought back into SSDT by first exporting it from where it is stored (msdb, SSIS Package Store, or file system), then adding it to an SSIS project. The HRESULT error is raised by the SSIS runtime when the designer cannot access the package location, so the key is to use the correct storage and path.

    A supported workflow is:

    1. Locate and export the package from SQL Server/SSIS service
      In SQL Server Management Studio (SSMS):
      • Connect to Integration Services in the Connect to Server dialog.
      • In Object Explorer, expand Stored Packages (or the relevant folder under the SSIS service).
      • Find the package that is currently running on SQL Server 2017.
      • Right‑click the package and choose Export (or use the Import/Export options on the folder) to save it either to the File System (.dtsx) or to SQL Server/msdb.
    2. Add the exported package into SSDT
      In SQL Server Data Tools (SSDT):
      • Open or create an SSIS project that targets SQL Server 2017 or 2022 as needed.
      • In Solution Explorer, right‑click SSIS Packages and select Add Existing Package.
      • In the Add Copy of Existing Package dialog:
        • Set Package location to File system if the package was exported as a .dtsx file, or to SQL Server/SSIS Package Store if it was saved there.
        • Use the Browse (...) button to select the package path.
      • Confirm to add a copy of the package into the project.
    3. If the original .dtsx is missing but the package is in SSISDB
      Export it from SSISDB via SSMS into the file system or package store, then follow step 2 to add it into SSDT.
    4. Copy/duplicate inside SSDT if needed
      Once the package opens in SSDT, it can be copied with File → Save <package name> As, and a new GUID can be generated for the copy if required.

    If the HRESULT error appears when using SSIS Package Store in the Add Existing Package dialog, switch to File system or SQL Server and ensure the package was first exported there via SSMS. The SSIS Package Store represents specific folders managed by the SSIS service; using an incorrect server or path will cause runtime errors.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.