mmoya
asked on
SQL Server Aegnt Not Running - SQL Server 2008
Any thoughts as to why I can't start SQLServer Agent service? All the services were able to run except for this service. I reviewed the sqlagent.out log and here's the error message.
2011-03-30 11:33:53 - ! [298] SQLServer Error: 27, Registry information is corrupt or missing. Make sure the provider installed and registered correctly. [SQLSTATE 08001]
2011-03-30 11:33:53 - ! [298] SQLServer Error: 27, Client unable to establish connection [SQLSTATE 08001]
2011-03-30 11:33:53 - ! [165] ODBC Error: 0, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
2011-03-30 11:33:53 - ! [000] Unable to connect to server '<server>'; SQLServerAgent cannot start
2011-03-30 11:33:53 - ! [298] SQLServer Error: 27, Registry information is corrupt or missing. Make sure the provider installed and registered correctly. [SQLSTATE 08001]
2011-03-30 11:33:53 - ! [298] SQLServer Error: 27, Client unable to establish connection [SQLSTATE 08001]
2011-03-30 11:33:53 - ! [165] ODBC Error: 0, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
2011-03-30 11:33:53 - ! [382] Logon to server '<server>' failed (DisableAgentXPs)
2011-03-30 11:33:53 - ? [098] SQLServerAgent terminated (normally)
2011-03-30 11:33:53 - ! [298] SQLServer Error: 27, Registry information is corrupt or missing. Make sure the provider installed and registered correctly. [SQLSTATE 08001]
2011-03-30 11:33:53 - ! [298] SQLServer Error: 27, Client unable to establish connection [SQLSTATE 08001]
2011-03-30 11:33:53 - ! [165] ODBC Error: 0, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
2011-03-30 11:33:53 - ! [000] Unable to connect to server '<server>'; SQLServerAgent cannot start
2011-03-30 11:33:53 - ! [298] SQLServer Error: 27, Registry information is corrupt or missing. Make sure the provider installed and registered correctly. [SQLSTATE 08001]
2011-03-30 11:33:53 - ! [298] SQLServer Error: 27, Client unable to establish connection [SQLSTATE 08001]
2011-03-30 11:33:53 - ! [165] ODBC Error: 0, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
2011-03-30 11:33:53 - ! [382] Logon to server '<server>' failed (DisableAgentXPs)
2011-03-30 11:33:53 - ? [098] SQLServerAgent terminated (normally)
Which account is configured to start the Sql Agent Service. It has enough rights?
ASKER
It's a domain admin account that is a local admin of the server plus has the following rights via local policy.
Act as part of the operating system
Adjust memory quotas for a process
Bypass traverse checking
Log on as a batch job
Log on as a service
Replace a process level token
Act as part of the operating system
Adjust memory quotas for a process
Bypass traverse checking
Log on as a batch job
Log on as a service
Replace a process level token
The service is recently installed, or it was running well and then it was damaged.
Please send information about OS and SQL versions, including upgrades.
Please send information about OS and SQL versions, including upgrades.
ASKER
No, this is brand new install never started. OS=Server 2008 R2 with SP1, SQL Server 2008, no upgrades because it's a brand new install.
If it is a new installation, the easy way is reinstalling, but if you want to try to identify the installation problem, then the first step is to obtain more information:
- SQL version (you may use "select @@version" in Management Studio
- verify if there where additional errors, in Windows Logs (Event viewer) when the agent service is starting
- Include SQLAgent.out (In the log folder)
- Restart SQL Server and try to start agent and export the Current SQL Server Log in SSMC
- SQL version (you may use "select @@version" in Management Studio
- verify if there where additional errors, in Windows Logs (Event viewer) when the agent service is starting
- Include SQLAgent.out (In the log folder)
- Restart SQL Server and try to start agent and export the Current SQL Server Log in SSMC
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
.
Please tell us how to solve the problem.
I would also be interested to know how you solved the problem. I'm experiencing the exact same thing.
ASKER
Was able to solve the issue.