Re: SQLServerAgent could not be started

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



M K

Here is a lengthy thread on the error you are getting. For these users it was a DNS problem. JPOPP seems to be the one who understands, so look to his responses and what follows.
http://forums.windowsitpro.com/web/forum/messageview.aspx?catid=54&threadid=42133&STARTPAGE=1&FTVAR_FORUMVIEWTMP=Linear

Also, running as Local System is not a best practice, both because of its power on the server and its limitations on the domain. The best practice is to define a domain login, grant it appropriate rights on the server and on the domain, and use it to run SQL Server and SQL Agent. See:
http://www.sqlservercentral.com/articles/Administration/pickingserviceaccounts/2351/

RLF

"M.K" <mianksaeed@xxxxxxxxx> wrote in message news:esXMKHzFKHA.3948@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

Posting again with a little detail. (with answers to Mr. Russell Fields)
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.
SQL Server Agent service is using the same login that is being used by SQL Server, using Local System for both.
SQL Server's clock is synced with the domain controller's.

Find below the SQLAGENT.OUT file text:

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)



.



Relevant Pages

  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall the SQL server from the SBS 2k3 server from add/remove programs ... Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT) ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 C
    ... I also checked the individual patch levels for the .NET drivers, SQL Server ... The SQL Server is fully patched, however Windows Update reported that the OS ... Lock pages in memory -- I guess you might have taken care of it as well. ...
    (microsoft.public.sqlserver.clustering)
  • RE: migrating from wmsde to sql server
    ... Click Start, point to All Programs\Microsoft SQL Server, and then click ... then click New SQL Server Registration. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall the SQL server from the SBS 2k3 server from add/remove programs ... Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT) ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • Re: Best replication architecture?
    ... Looking for a SQL Server replication book? ... So if it is subscribing to Publisher 1, ...
    (microsoft.public.sqlserver.replication)