October 12, 2010 at 6:59 am
Hi, did anyone get this ...
SQL Server Agent won't start up when using SQL Server Configuration Manager but will using Windows Services ...
My maintenance plan didn't want to execute and had an error of not having access to the server and I changed the account under which the agent wasa running in the Config Manager and well it didn't want to start. After numerous attempts I tried in Win Services an to my surprise it works there ...
Checked all Event viewer and SQL logs and there is no login failed or anything concerning my failed attempts to start up the SQL Agent ...
MCITP: Database Administrator 2005
MCTS SQL Server 2008
MCP SQL 2012/2014
MCSA SQL Server 2012/2014
MCSE Data Management and Analytics
June 11, 2018 at 3:55 pm
Ok this drove me a little nuts, this might help you
SQL Server Agent will not start and MSODCBSQL13 Driver cannot be found
I did fix my particular issue, hopefully this helps somebody else
I had the developer edition of SQL 2017 installed but could not get SQL Server Agent to start at all.
I ended up reverting to the 2016 developer edition but had the same problem. Found out the MSODBCSQL13 driver could not be found, this showed up under the log viewer for NT. So I download MSODBCSQL13.1. But it tells me I have a higher version and exits the installation. So I uninstalled the Microsoft ODBC driver 17 and 13.1 from the system and re-downloaded Microsoft ODBC driver 13 and installed it.
I rebooted the computer and I could finally get SQL Server Agent to start. This happens under SQL Developer Edition 2016 and 2017 so chances are something with the configuration ONLY recognizes the original ODBC13 driver for SQL Server.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply