SQL Service Crashes Caused by SQL Agent Permission Issues

Vanitha Dodla (MINDTREE LIMITED) 40 Reputation points Microsoft Vendor
2024-04-02T00:36:09.54+00:00

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?

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,603 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. MikeyQiao-MSFT 325 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".

    0 comments No comments

  2. Olaf Helper 40,576 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