Skip to main content
To homepage To homepage
Solved

SSIS Packages do not run after TX Update

  • January 9, 2026
  • 4 replies
  • 42 views
kerry_bespoke
Contributor
Forum|alt.badge.img

We have recently updated a TimeXtender version from 20.1047 to 20.10.74 and was successful for Development and QA but after updating Production the SSIS Packages are not executing. Development and QA have the same version of SQL as Production.

 

The execution of SSIS Packages is setup through External tasks.

 

The only relevant information I have found so far regarding this issue is here (https://legacysupport.timextender.com/hc/en-us/articles/360000169786-Troubleshooting-Upgrade-Issues) but am not sure how the steps under heading ‘Cannot deploy or execute SSIS packages’ would resolve the issue.

 

Anyone else run into this?

Best answer by rory.smith

Hi,

you might want to check for permission issues in Event Viewer: https://learn.microsoft.com/en-us/sql/integration-services/service/integration-services-service-ssis-service?view=sql-server-ver17#event-logged-when-permissions-are-missing . You also might need to look into DCOM settings if those have been customized for your Production deployment (there is some sparse info on the same webpage).

It could be useful to start TimeXtender as your service user and try to manually run a package from the GUI. Additionally, it is good to see if you can trigger the package from CLI: https://learn.microsoft.com/en-us/sql/integration-services/ssis-quickstart-run-cmdline?view=sql-server-ver16

The steps on your link simply ensure that the new TX version is always run as Administrator. You may have noticed that starting with SSIS 2016 or so, SSMS also needs to be run as Administrator in most cases to be able to connect to SSIS. If you install a new version of TimeXtender, that is a separate install next to the old one.

Kerry // Bespoke Analytics

4 replies

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+8
  • rory.smith
  • TimeXtender Xpert
  • Answer
  • January 12, 2026

Hi,

you might want to check for permission issues in Event Viewer: https://learn.microsoft.com/en-us/sql/integration-services/service/integration-services-service-ssis-service?view=sql-server-ver17#event-logged-when-permissions-are-missing . You also might need to look into DCOM settings if those have been customized for your Production deployment (there is some sparse info on the same webpage).

It could be useful to start TimeXtender as your service user and try to manually run a package from the GUI. Additionally, it is good to see if you can trigger the package from CLI: https://learn.microsoft.com/en-us/sql/integration-services/ssis-quickstart-run-cmdline?view=sql-server-ver16

The steps on your link simply ensure that the new TX version is always run as Administrator. You may have noticed that starting with SSIS 2016 or so, SSMS also needs to be run as Administrator in most cases to be able to connect to SSIS. If you install a new version of TimeXtender, that is a separate install next to the old one.

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

​@kerry_bespoke can you please show how the SSIS packages have been setup with some screenshots? Also can you please confirm which version of SSIS are you running? Can you please send the error message you get when executing?

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

​@kerry_bespoke I will go ahead and mark Rory’s answer above as best answer, if you need any further help with this please let us know. Thanks :)

kerry_bespoke
Contributor
Forum|alt.badge.img
  • kerry_bespoke
  • Author
  • Contributor
  • January 20, 2026

​@rory.smith  -  Thank you for getting back to me and I apologize for not following up. Both suggestions were incredibly helpful and we did find out that the issue was Production had a different.NET version which was causing issues due to the scripts used within the SSIS Packages.

​@Christian Hauggaard - sorry for not getting back to you and thank you for following up on this and marking Rory’s comment as the best answer.

 

Kerry // Bespoke Analytics
    Terms and ConditionsCookie settingsAccessibility statement