SQL Service Crashes Caused by SQL Agent Permission Issues

Vanitha Dodla (MINDTREE LIMITED) 40 Microsoft Vendor

What are the troubleshooting steps to identify and resolve unexpected service terminations with Event id 7036, 7034, and 19019, that I suspect are caused by SQL Agent permission issues? Additionally, how can I prevent this issue from recurring, and if no error logs are triggered, what other methods can I use to diagnose the problem?

MikeyQiao-MSFT 560 Reputation points Microsoft Vendor

2024-04-19T01:30:17.21+00:00

We have not received a response from you. Did the reply could help you? If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.

2 answers

MikeyQiao-MSFT 560 Reputation points Microsoft Vendor

2024-04-02T03:17:52.93+00:00
Hi，@Vanitha Dodla

Run and find the SQL Server version information.

SELECT @@VERSION

Is your SQL Server set up for high availability?

Is this error occurring randomly or on a regular basis?

Was the SQL Server performing a data import when it went down?

How many connections are there in the database? Whether the OLEDB driver is a third-party driver?

Could you please confirm the latest error log from the time of the recent failure?

Please provide the detail about the event error.

To diagnose the problem, you can use SQL Server Profiler. Please pay attention to "Errors and Warnings".
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Olaf Helper 40,896 Reputation points

2024-04-02T05:09:55.8833333+00:00

I suspect are caused by SQL Agent permission issues?

Impossible.

Do you have any hint in SQL Server ErrorLog?

Viewing the SQL Server Error Log
Please sign in to rate this answer.
Vanitha Dodla (MINDTREE LIMITED) 40 Reputation points Microsoft Vendor

2024-04-02T22:13:31.79+00:00

Hello Olaf,

No we didnt find anything in sql error logs

Erland Sommarskog 101.1K Reputation points MVP

2024-04-03T21:12:55.4866667+00:00

So SQL Server is stopping, but there is no trace of this in the errorlog? That's unusual. Are you sure that you are looking in the right log file? The current ERRORLOG has no information. You need to look in ERRORLOG.1 - assuming that last time SQL Server was started, it was after a crash.

Also, what does "SELECT @@version" return?

Vanitha Dodla (MINDTREE LIMITED) 40 Reputation points Microsoft Vendor

2024-04-03T21:59:38.51+00:00

Hello Erland,

Yes we couldn't able to see anything in error logs we checked at the time stamp and anything except agent permissions denied and forced sql to shutdown in SQL agent logs we found this.

SQL service crashed and could not restart due to SQL agent permissions denied. These servers had a normal restart on the previous maintenance weekend.

We need to know

Service restart issue – Why access denied (We have full permissions). How could we gather useful logs for any future iterations for the same type of issue.

Erland Sommarskog 101.1K Reputation points MVP

2024-04-04T06:50:55.3666667+00:00

It is very difficult to understand from your superficial description what actually happened. We would need to see the exact error messages and the log files at the time. The talk about "SQL Server agent permissions denied" sounds funny to me, but as I said, I have not see the actual error messages.

If SQL Server crashed there should also be dump files in the same folder as the LOG directory, although the dump files are difficult to make sense of, unless you are a support engineer at Microsoft.
Sign in to comment