SQL Server Agent (Unable to Terminate Job - Access Denied)
Question
Sunday, June 7, 2020 3:54 PM
Hello all,
I am faced with a problem today that has me stumped me and could do with some advice or guidance.
The SQL Server Agent error log is reporting "[136] Job [name] reported: Unable to terminate process 290c launched by step 1 of job [name] (reason: Access is denied)". This error is being reported on about 40% of the current jobs on the server.
The SQL Server is version "13.0.5698.0" Standard Edition (64-bit). The production server has had no recent changes to it.
The jobs in question are doing basic SSIS data collection and bulk inserts into various databases/tables. Most of the jobs run overnight but some run every 15 minutes which are basically change data capture processes. There has been no changes to these solutions in weeks. All of these agent jobs have been running okay for weeks (since January).
I am using an SSIS proxy account to execute the jobs.
I have run the jobs (using the database engine service account) manually and they successfully complete every time.
I thought the packages may have been corrupted within the database so I redeployed to msdb.
I am now only receiving sporadic errors detailed above. During one execution they complete successfully other times they do not? This has been happening since yesterday.
What I am concerned about is that the msdb database may be corrupt itself but I'm really not sure how to confirm this. I have system backups available if I require them.
I have checked the data source systems and the data destination systems which are reporting no errors to speak off.
Any assistance or advice would be greatly received.
Stephen
All replies (1)
Monday, June 8, 2020 6:47 AM âś…Answered | 1 vote
Hi Stephen,
>> What I am concerned about is that the msdb database may be corrupt itself but I'm really not sure how to confirm this.
Please use DBCC CHECKDB to check if msdb is corrupt.
>> Unable to terminate process 290c launched by step 1 of job [name] (reason: Access is denied)".
The error "Access is denied" makes me think that it is either running the job step as a specific login who doesn't have proper permissions. You can try to recreate the proxy account, give the right permission to the proxy account. Or you can change the SQL agent service account to the account that you can manually execute the jobs successfully, and change the job steps to execute the jobs under SQL server agent service account.
Someone has the same issue, the issue was resolved by pushing all pending windows updated patches to be installed. After this SQL Agent was restarted and jobs behavior was normal again.
Best regards,
Cathy
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com