@ZoeHui-MSFT ,I have enabled all logging but nothing has been written to logfile .Let's say even if Proxy account doesn't have access to Package Location directory ,it should fail right ! but it is neither failing nor actually doing anything .Just keep on running with out actually running any tasks in the SSIS Package.
SQL Server Agent Jobs running forever involving SSIS packages
I have several jobs scheduled on my Production server (SQL Server 2017). All the jobs involving executing SSIS packages are taking forever to run.
The jobs involving executing stored procedures and T-SQL scripts are running fine. All this started happening since two days back suddenly over the weekend. Before that everything was working since many years. No updates/security patches to the server during weekend.
When I tested the same jobs on the development server, they are working fine. All the jobs are scheduled to run at different times over the day. I don't even see anything in SQL Server Activity monitor.
I have created a very basic SSIS package to truncate a empty table and created a job to call this newly created package. After starting the job, it was running forever .
All working fine on server except jobs calling SSIS packages.
I have been running all these Jobs using Proxy account since many years .I tried to run the Job using another proxy account which has permissions ,still the same problem. Also tried restarting SQL Server Agent and SSIS service ,but nothing helped .
We are using File system deployment .SSIS packages are placed on some network location and being called from the Job.
My test package is running good when I tried to run in my local machine in Visual studio.
Can anyone give some ideas about what's going on the server please?