Migrating VS2019 SSIS Pkg to SQL Server 2022 - Error Encountered

Question

Migrating VS2019 SSIS Pkg to SQL Server 2022 - Error Encountered

sidney l 21

I am trying to migrate an SSIS PKG that was developed using VS2019 for SQL Server 2019 on Windows Server 2019. Now we have this new test server with the following components installed:

Windows Server 2022 Datacenter
SQL Server 2022 Enterprise
VS 2019

I copied the SSIS Project from the old server to the new server. Opened it with VS2019 since it was created in VS2019 as I'm trying to take the least resistance path hoping things would work. So I opened it without any problems and ran it successfully in VS2019 with the TargerServerVersion still set to 2019 but loaded the data into SQL 2022.

When I setup a .bat file to run this SSIS PKG via dtexec, I get this error

Error: 2025-04-11 09:32:52.14

Code: 0xC001700A

Source: Package

Description: The version number in the package is not valid. The version number cannot be greater than current version number.

My guess is that it needs to have the TargetServerVersion = SQL Server 2022 but VS2019 doesn't support SQL 2022 and my requirement is I can't have VS2022 on the new server. So it works fine in VS2019 but not at command line.

How can I make this SSIS work on the new server using dtexec?

Thank you

sidney l 21 Reputation points

2025-04-14T21:16:16.3533333+00:00

Is there anyone out there who could help me with this error?

Accepted answer

1 additional answer

Your answer

sidney l 21 Reputation points

2025-04-14T21:16:16.3533333+00:00

Is there anyone out there who could help me with this error?

Answer 1

Michael Taylor 58,696

Firstly, you should really never install VS on a production server. There is no reason to do this. It could negatively impact the server, requires you keep it up to date and is a potential access point for malicious software. So my recommendation is you remove VS from the SQL server.

As for the target version, I don't think that is the issue. SQL 2022 can run SSIS packages targeting SQL 2019. All you need to do is deploy the SSIS package to the SQL 2022 instance and it should run. Did you actually deploy the SSIS package to your server or are you just trying to run it manually? The easiest way to deploy it is to open it in VS, right click the package in Solution Explorer and select the option to Deploy. It should deploy everything needed for that SSIS package to run.

Once you've deployed then run SSMS, go to the SSISDB database and find the SSIS package. Then execute the package. If it runs then everything is deployed properly.

Things to consider here:

If the SSIS package is using shared data sources then you'd need to ensure that the appropriate data sources are also deployed.
If you are using runtime configuration files (parameter files I think they are called) then you need to ensure they are deployed as well.
If you're running into errors then enable diagnostic logging on the package on the server so you can get to the actual errors.
If you rely on any third party components in SSIS then they have to be deployed first. This is outside the package deployment.
Check to see what bitness your SSIS package is running under. Ensure that everything you rely on supports that bitness. I think VS uses 64-bit by default, but I could be wrong.

To develop SSIS packages going forward you should install VS 2022 on a development server. Copy your SSIS package to it and develop against that. Note that you can still target your SQL 2022 instance running wherever, that's the purpose of the Connection Manager. Once you have your package ready to go then, as mentioned earlier, you can have VS deploy to the SQL server for production use. Alternatively you can use a CLI or SSMS to deploy the package by hand.

sidney l 21 Reputation points

2025-04-15T20:45:04.6433333+00:00

@Michael taylor You said "Did you actually deploy the SSIS package to your server or are you just trying to run it manually?" I was running the .dtsx using the x32 bit version of the 'dtexec.exe' on this 'Test' server at the command prompt. This package contains x32 bit drivers. So I had to run everything in x32 bit mode including in VS2019. What exactly is meant by "Description: The version number in the package is not valid. The version number cannot be greater than current version number."? Where is the mismatch?
Michael Taylor 58,696 Reputation points

2025-04-15T21:10:09.5166667+00:00

I don't know where the mismatch is. That is why I recommended to deploy the package. If the package cannot be deployed then it cannot run.

My gut instinct is that your SSIS package has a dependency on something that is newer than what is on the SQL Server. But without looking at the dependencies in your package there is no way to know what. Hence why I also mentioned that any third party dependencies you have need to be installed on the server.
sidney l 21 Reputation points

2025-04-16T12:21:26.6766667+00:00

The current 'PackageFormatVersion' in my .dtsx file is 8 which is for SQL Server 2019 and 9 is for SQL 2022. The error message almost made it sound like I have a SSIS package (PackageFormatVersion = 9) trying to run it against SQL Server 2019 (PackageFormatVersion = 8). Well I don't have any newer components except what's new on this 'Test' server is Win2022, SQL2022 with VS2019. I'll continue to dig into this and will follow up if I'm able to find the root cause. Thanks for your help @Michael taylor
Michael Taylor 58,696 Reputation points

2025-04-16T13:57:26.19+00:00

Again, you're using a batch file to run a CLI tool to run your SSIS package. Anything in that pipeline could be wrong. Have you tried just deploying your SSIS package to the server as is typically done and then running it directly from SSMS? If it works there then the issue is your batch file or how it is trying to run the package. If deploy/run directly from the server doesn't work then it is a package issue. Some things that come to mind is using a hard coded path to DTSExec. DTSExec is versioned with SQL and the path contains the version #. You'd need to be using the newer DTSExec CLI to run against a newer SQL version. Those are the kinds of things that running directly from SQL would help identify.

Otherwise enable diagnostic logging in the package and see what the error logs show.

Answer 2

sidney l 21

@Micheal Taylor That was it! I ran it with the incorrect version of 'dtexec.exe' So the error message indeed was accurate. I wasn't even aware of multiple versions of 'dtexec'. Consider it was a self-inflicted pain!! :) Thanks for that tip.

Share via

Migrating VS2019 SSIS Pkg to SQL Server 2022 - Error Encountered

1 additional answer

Your answer