0
votes

After doing a restart to fix some performance issue on a 2017 SQL Server, couple of jobs (kicking off SSIS package) have been failing, all stuck pending execution state. Same issue persists when I manually start the job or execute the package from SSISDB.

The job is set to run using SQL Agent Service, other jobs running a T-Sql statement have been running fine.

1
have you checked in services manager that SSIS Service is running? - Jayvee
Yes it's running, just checked again - iMajek
If the packages are running as part of a SQLAgent job, check the job for what user it's running as. Check those permissions, and that could be your problem. - perry147
The job is using SQL Server Agent Service Account, I don't think this is where the problem is because when I execute the package directly in SSISDB, I get the same error - iMajek

1 Answers

0
votes

It was a permission issue but still don't understand how and why, no changes were made on the server, I was also unable to deploy SSIS package from VS to SSISDB/Integration Services Catalogue.

Repairing the SQL Server via the installation centre seems to have resolved the issue.