Forum Discussion
Identical SQL Jobs failing (SSIS package)
I have a SQL Server 2022 application running on 2 nodes redundantly, one of the jobs (SSIS) is failing on the primary node saying the service account can not find the specified file, the exact same job, works fine on the secondary node using the same service account (domain account). Job works fine when running through visual studio using the same domain account (SQL Server Agent account)
I can browse into the path were the job file is stored from both nodes using the service account. I recreated the job by using the script from the job that works fine but still no success. I copied the SSIS package file locally into the server but i still have the same issue. any ideas? Thanks in advance!
The process could not be created for step 1 of job 0x72DB1C3372A2974DAA7D83AED24F078F (reason: The system cannot find the file specified). The step failed.
mendee1 ,
Please, Provide a Script for the SQL Server agent job. You can remove any confidential information.
This is required to know the execution hierarchy along with the execution context.
Please, explain what do you mean by 'I copied the SSIS package file locally into the server but i still have the same issue'?
And specify the exact SQL Server deployment? Is it Always On availability groups?
Also, Provide the windows event viewer info at the same time the execution fails.
(reason: The system cannot find the file specified). The step failed.mendee1 , then I guess the installation on the 2 nodes are different and one one node a dependency is misssing like a specific data provider. But I don't know what the SSIS packages do and so I can't say, what may is missing.
- wouldnt the job history show that there was a missing provider or something like that?
mendee1 Not in job history, but may be in the job step history, it has more details.
And if you work with SSIS catalog, then in the execution reports.
