dbTalk Databases Forums  

SQLServerAgent could not be started

microsoft.public.sqlserver.setup microsoft.public.sqlserver.setup


Discuss SQLServerAgent could not be started in the microsoft.public.sqlserver.setup forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
M.K
 
Posts: n/a

Default SQLServerAgent could not be started - 08-06-2009 , 12:23 AM






HI,

Whenever my Server Machine (Windows 2008 Server) restarts. My SQL Server
2008 DB engine & every thing starts normally. But the SQLSERVER AGENT
(Configured to be Automatic) do not starts & I have to start it Manually by
right click & start it through Management Studio.

The message in Windows log is:
SQLServerAgent could not be started (reason: Unable to connect to server
'(local)'; SQLServerAgent cannot start).


Seems no problem of SYSTEM ACCOUNT unable to start. In that case, it must
not have allowed the Manual Start of SQL Server then. Maybe SQLServer agent
trying to start before start of MS SQLSERVER.

Any idea?

Reply With Quote
  #2  
Old   
Erland Sommarskog
 
Posts: n/a

Default Re: SQLServerAgent could not be started - 08-06-2009 , 01:48 AM






M.K (mianksaeed (AT) yahoo (DOT) com) writes:
Quote:
Whenever my Server Machine (Windows 2008 Server) restarts. My SQL Server
2008 DB engine & every thing starts normally. But the SQLSERVER AGENT
(Configured to be Automatic) do not starts & I have to start it Manually
by right click & start it through Management Studio.

The message in Windows log is:
SQLServerAgent could not be started (reason: Unable to connect to
server '(local)'; SQLServerAgent cannot start).


Seems no problem of SYSTEM ACCOUNT unable to start. In that case, it
must not have allowed the Manual Start of SQL Server then. Maybe
SQLServer agent trying to start before start of MS SQLSERVER.
You could try to configure it to start "Automatic (delayed)"


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Reply With Quote
  #3  
Old   
M.K
 
Posts: n/a

Default Re: SQLServerAgent could not be started - 08-06-2009 , 08:01 AM



Tried with "Automatic(delayed)" but didn't worked.
Below is the text of SQLAGENT.OUT file:-

2009-08-06 21:50:16 - ! [298] SQLServer Error: 848, SQL Server Network
Interfaces: The system detected a possible attempt to compromise security.
Please ensure that you can contact the server that authenticated you.
[SQLSTATE HY000]
2009-08-06 21:50:16 - ! [298] SQLServer Error: 848, Cannot generate SSPI
context [SQLSTATE HY000]
2009-08-06 21:50:16 - ! [000] Unable to connect to server '(local)';
SQLServerAgent cannot start
2009-08-06 21:50:16 - ! [298] SQLServer Error: 848, SQL Server Network
Interfaces: The system detected a possible attempt to compromise security.
Please ensure that you can contact the server that authenticated you.
[SQLSTATE HY000]
2009-08-06 21:50:16 - ! [298] SQLServer Error: 848, Cannot generate SSPI
context [SQLSTATE HY000]
2009-08-06 21:50:16 - ! [382] Logon to server '(local)' failed
(DisableAgentXPs)
2009-08-06 21:50:17 - ? [098] SQLServerAgent terminated (normally)





"Erland Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote

Quote:
M.K (mianksaeed (AT) yahoo (DOT) com) writes:
Whenever my Server Machine (Windows 2008 Server) restarts. My SQL Server
2008 DB engine & every thing starts normally. But the SQLSERVER AGENT
(Configured to be Automatic) do not starts & I have to start it Manually
by right click & start it through Management Studio.

The message in Windows log is:
SQLServerAgent could not be started (reason: Unable to connect to
server '(local)'; SQLServerAgent cannot start).


Seems no problem of SYSTEM ACCOUNT unable to start. In that case, it
must not have allowed the Manual Start of SQL Server then. Maybe
SQLServer agent trying to start before start of MS SQLSERVER.

You could try to configure it to start "Automatic (delayed)"


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000:
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Reply With Quote
  #4  
Old   
Russell Fields
 
Posts: n/a

Default Re: SQLServerAgent could not be started - 08-06-2009 , 10:09 AM



M.K,

The core problem is that it cannot (at that time at least) generate the SSPI
context.

Questions: Are you running SQL Server Agent service using the same login
that you use for SQL Server? Are you using Local System for either? At
startup, is the SQL Server's clock out of synch with the domain controllers?
etc.

Here is a Microsoft document on troubleshooting this problem.
http://support.microsoft.com/kb/811889

Here is a SQL Server Central article from a few years ago (SQL Server 2000)
that several people have found helpful, including resolving the SQL Agent
problems. Be sure to follow the "Join the discussion" link to read the
experiences posted.
http://www.sqlservercentral.com/arti...picontext/929/

Hope that helps,
RLF

"M.K" <mianksaeed (AT) yahoo (DOT) com> wrote

Quote:
Tried with "Automatic(delayed)" but didn't worked.
Below is the text of SQLAGENT.OUT file:-

2009-08-06 21:50:16 - ! [298] SQLServer Error: 848, SQL Server Network
Interfaces: The system detected a possible attempt to compromise security.
Please ensure that you can contact the server that authenticated you.
[SQLSTATE HY000]
2009-08-06 21:50:16 - ! [298] SQLServer Error: 848, Cannot generate SSPI
context [SQLSTATE HY000]
2009-08-06 21:50:16 - ! [000] Unable to connect to server '(local)';
SQLServerAgent cannot start
2009-08-06 21:50:16 - ! [298] SQLServer Error: 848, SQL Server Network
Interfaces: The system detected a possible attempt to compromise security.
Please ensure that you can contact the server that authenticated you.
[SQLSTATE HY000]
2009-08-06 21:50:16 - ! [298] SQLServer Error: 848, Cannot generate SSPI
context [SQLSTATE HY000]
2009-08-06 21:50:16 - ! [382] Logon to server '(local)' failed
(DisableAgentXPs)
2009-08-06 21:50:17 - ? [098] SQLServerAgent terminated (normally)





"Erland Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote in message
news:Xns9C5F585306DD3Yazorman (AT) 127 (DOT) 0.0.1...
M.K (mianksaeed (AT) yahoo (DOT) com) writes:
Whenever my Server Machine (Windows 2008 Server) restarts. My SQL Server
2008 DB engine & every thing starts normally. But the SQLSERVER AGENT
(Configured to be Automatic) do not starts & I have to start it Manually
by right click & start it through Management Studio.

The message in Windows log is:
SQLServerAgent could not be started (reason: Unable to connect to
server '(local)'; SQLServerAgent cannot start).


Seems no problem of SYSTEM ACCOUNT unable to start. In that case, it
must not have allowed the Manual Start of SQL Server then. Maybe
SQLServer agent trying to start before start of MS SQLSERVER.

You could try to configure it to start "Automatic (delayed)"


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000:
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Reply With Quote
  #5  
Old   
M.K
 
Posts: n/a

Default Re: SQLServerAgent could not be started - 08-06-2009 , 09:59 PM



Thanks for help. Will look at the links you sent for troubleshoot the issue
& would try the solution.


"Russell Fields" <russellfields (AT) nomail (DOT) com> wrote

Quote:
M.K,

The core problem is that it cannot (at that time at least) generate the
SSPI context.

Questions: Are you running SQL Server Agent service using the same login
that you use for SQL Server? Are you using Local System for either? At
startup, is the SQL Server's clock out of synch with the domain
controllers? etc.

Here is a Microsoft document on troubleshooting this problem.
http://support.microsoft.com/kb/811889

Here is a SQL Server Central article from a few years ago (SQL Server
2000) that several people have found helpful, including resolving the SQL
Agent problems. Be sure to follow the "Join the discussion" link to read
the experiences posted.
http://www.sqlservercentral.com/arti...picontext/929/

Hope that helps,
RLF

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.