Hey folks, I’m having a real headache with my SSIS packages after upgrading from SQL Server 2019 to 2022. Everything seems to be in order, except that these packages just won’t run. I’ve tried several methods:
- Upgrading and deploying the SSIS project
- Exporting the current project and redeploying it
- Building packages for all server versions and deploying them sequentially
Unfortunately, every attempt results in error 27203. I confirmed that the server version is correct and even ran a query on the operations_messages table, but nothing showed up. In the SSMS Log File viewer, I found the following details:
Application: ISServerExec.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
Has anyone else encountered this issue or found a workaround to successfully deploy SSIS projects on SQL Server 2022? Any help would be greatly appreciated!
Having dealt with similar issues during SQL Server upgrades, I can share some insights that might help. First, ensure that the SSIS catalog is properly upgraded to 2022. Sometimes, the catalog doesn’t automatically update during the server upgrade process. You can verify this by checking the version of the SSISDB database.
Another crucial step is to review the SSIS service account permissions. After the upgrade, these might need adjusting. Ensure the account has the necessary rights to access all resources used by your packages.
If these don’t resolve the issue, consider creating a new SSIS catalog and migrating your projects there. This approach has worked for me in the past when facing stubborn deployment problems post-upgrade.
Lastly, double-check that all dependencies, such as custom components or third-party tools used in your packages, are compatible with SQL Server 2022. Incompatibilities can cause unexpected errors like the one you’re experiencing.
hey man, have u looked into the file permissions? that exception makes me think theres a file access issue goin on. maybe check if the SSIS service account can reach all the necessary files and folders. also, try runnin the package in dtexec with debug mode on - might show more detailed errors. good luck!
hmm, intresting issue youve got there! have you tried checking the SSIS service logs for any clues? sometimes they hide sneaky error messages that dont show up elsewhere. also, maybe try running the package in SSDT with SQL Server 2022 configuration? could reveal some compatibilty hiccups. what other troubleshooting steps have you taken so far?