Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
btamulis
Yak Posting Veteran
64 Posts |
Posted - 2006-05-13 : 12:16:03
|
| I installed SQL2005 (first time). I have a couple of problems that perplex me.I can connect to my instance when starting up SQL Management Studio no problem. After connecting, I can manually backup and restore DBs, no problem.However, when I attempt to start SQL Server Agent - I get the follwoing message:Unable to start service SQLAgent$GREATPLAINSV80 on server USIND-BAT3835N1.===================================The SQLAgent$GREATPLAINSV80 service on USIND-BAT3835N1 started and then stopped. (ObjectExplorer)------------------------------Program Location: at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.Service.Start()The error log is as follows:Date,Source,Severity,Message05/13/2006 12:08:57,,Information,[098] SQLServerAgent terminated (normally)05/13/2006 12:08:56,,Error,[382] Logon to server 'USIND-BAT3835N1\GREATPLAINSV80' failed (DisableAgentXPs)05/13/2006 12:08:56,,Error,[298] SQLServer Error: 772<c/> Cannot generate SSPI context [SQLSTATE HY000]05/13/2006 12:08:56,,Error,[298] SQLServer Error: 772<c/> SQL Network Interfaces: The Local Security Authority cannot be contacted [SQLSTATE HY000]05/13/2006 12:08:56,,Error,[000] Unable to connect to server 'USIND-BAT3835N1\GREATPLAINSV80'; SQLServerAgent cannot start05/13/2006 12:08:56,,Error,[298] SQLServer Error: 772<c/> Cannot generate SSPI context [SQLSTATE HY000]05/13/2006 12:08:56,,Error,[298] SQLServer Error: 772<c/> SQL Network Interfaces: The Local Security Authority cannot be contacted [SQLSTATE HY000]I researched using Microsoft SQL Home knowledge base for error 772, cannot generate SSPI context and [SQLSTATE HY000] and didn't find anything that seems to apply. Why can I connect to the database engine but not start SQL ServerAgent? |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-14 : 02:49:26
|
| because they can run on different security contextthe errors you posted may either mean:1. you are running the sqlserveragent using localsystemaccount but have removed the builtin\administrator account in the sql server2. you are running the sqlserveragent using a domain account but failed to add that domain account in the sql server loginscheck the event logs, these might give you more cluesHTH--------------------keeping it simple... |
 |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2006-05-14 : 13:22:13
|
Try going into the surface area configuration tool and enable the Agent XP's.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
exorcist
Starting Member
1 Post |
Posted - 2008-03-27 : 06:10:37
|
| Have you checked SQL Server Configuration Manager?You would be surprised to find that sometimes protocols are disabled.I have had a simular problem starting the Agent, when closely observing the situation I found out that under SQL Native Client Configuration -> Client Protocols, all of the protocols were disabled.Try enabling at least TCP/IP.Hope this helps. |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-03-29 : 00:52:45
|
| Add sql agent service account to sysadmin role. |
 |
|
|
|
|
|
|
|