SQL Server Agent is not starting after in place upgrade of SQL server from 2012 to 2019

Question

SQL Server Agent is not starting after in place upgrade of SQL server from 2012 to 2019  I have done in place upgrade of SQL server from SQL 2012 Standard Edition (64-bit) SP4 to Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64)   Sep 24 2019 13:48:23   Copyright (C) 2019 Microsoft Corporation  Standard Edition (64-bit) on Windows Server 2019 Datacenter 10.0

Answer 1

Hi Prajakta, Welcome to Q&A Forum; this is a great place to get support, answers, and tips. Thank you for posting your question; I'll be more than glad to help you out.

It sounds like a problem with permissions on the some files (might be the data/log file or the errorlog file)... please take a look into your eventviewer on that machine... you should find an error entry when the agent won't start, it might look like this one:

source: source: https://www.mssqltips.com/sqlservertip/6322/sql-server-agent-service-wont-start-due-to-access-denied/ As you can see, that message also states why it fails => permission on agent error log In this post, you will also find additional help on how to (hopefully) fix your problem. https://www.mssqltips.com/sqlservertip/6322/sql-server-agent-service-wont-start-due-to-access-denied/

I hope my answer is helpful to you, Your Bjoern Peters

If the reply was helpful, please upvote and/or accept it as an answer, as this helps others in the community with similar questions. Thanks!

Answer 2

Hi @Prajakta Joshi,

Restart the SQL Server Agent service: Sometimes, simply restarting the SQL Server Agent service can resolve this issue.

I analyze it from two aspects:

The SQL Server Agent service account does not have permission to write to the msdb database.

Check the file permissions on the msdb database files: Ensure that the SQL Server service account has the appropriate permissions to read and write to the msdb database files. You can check the file permissions by right-clicking on the msdb database in SSMS, selecting Properties, and then navigating to the Files tab. If the SQL Server service account does not have the appropriate permissions, click on the Edit button and add the account to the list of Group or user names, and grant it the necessary permissions. Finally, restart SQL Server Agent service.

The msdb database is corrupt or damaged.

In single-user mode, check and repair any errors using DBCC checkdb, and then set the database to multi-user mode again.

If none of the above solutions work, you may need to perform a repair installation of SQL Server to fix any missing or corrupted components that may be causing the SQL Server Agent to fail to start. To perform a repair installation, run the SQL Server installer and select the "Repair" option.

If msdb is corrupted, your best choice is to restore the backup, if there is no backup and DBCC checkdb is useless, then you may need to rebuild msdb.

Best regards,

Seeya

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".