Post reply

Unable to start SQL Agent service

  • May 31, 2012 at 6:06 am

    #256800

    Hi All,

    I have installed SQL2008 R2 on Win 2k8 Enterprise Edi.

    The server is not on domain, its on local work group.

    When I try to connect to Data base Engine using SQL authentication i.e. sa it allows to connect.

    But when I try to connect using window authentication is gives error login failed with error code 18452. (The account for login is SRVNM\Administrator)

    SQL Database service is running under.\Administrator.

    SQL Agent not working.

    If I try to start the SQL Agent service and check event viewer it give following error.

    SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. [CLIENT: <local machine>].

    I tried with in buit local services also but no luck.

    Googled for this but no luck.

    Any help would be really appriciated.

    Thanks in Advance

  • May 31, 2012 at 6:42 am

    #1495179

    It could be due to two machines on the network with the same name.

    http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/343e15a5-a577-437c-9693-66e303f0c0eb

    Check your event log, see if you have the kerberos mentioned in the above.

    Also try google for '0x8009030c' looks like many hits for this specific error.

  • May 31, 2012 at 6:53 am

    #1495184

    Hi,

    There is no Kerboros there in eventviewer log

  • May 31, 2012 at 7:08 am

    #1495190

    I've seen that SSPI error occur when a Windows password has recently expired or been changed.

    Also, please will you check that the time of your most recent SQLAgent.OUT file coincides with the time of your most recent attempt to start SQL Server Agent, and post the contents of the file?

    John

  • May 31, 2012 at 7:26 am

    #1495202

    Hi,

    Here is the content of the SQLAgent.out file.

    2012-05-31 14:38:23 - ! [000] Unable to connect to server '13179-HP7100'; SQLServerAgent cannot start

    2012-05-31 14:38:23 - ! [298] SQLServer Error: 18452, Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [SQLSTATE 28000]

    2012-05-31 14:38:23 - ! [382] Logon to server '13179-HP7100' failed (DisableAgentXPs)

    2012-05-31 14:38:24 - ? [098] SQLServerAgent terminated (normally)

    Please suggest

  • May 31, 2012 at 7:34 am

    #1495209

    I've just noticed that you said the server is not in a domain. I think that's your problem - it sounds as if you're trying to run SQL Server Agent under a domain account. If that's not the case, what account does it run under? What access does that account have to SQL Server? Is there any reason you can't add you server to a domain?

    John

  • May 31, 2012 at 8:00 am

    #1495231

    Did you rename the computer at some point?

    I ask because it doesn't look like the computer name is the same between here:

    The account for login is SRVNM\Administrator

    and here:

    Unable to connect to server '13179-HP7100'; SQLServerAgent cannot start

    Although if you tried running the Agent using the Local Service account, I would expect it to have worked. Maybe (for testing) try running it as the Local System, instead.

    Also, make sure that ANY changes you're making to the service are being done through the SQL Server Configuration Manager, and NOT the "Services" section of Computer Management.

    Jason A.

  • May 31, 2012 at 8:00 am

    #1495234

    Hi,

    The services running under local Administrator.

    I am setting up some local environment that's the only reason Its not on domain. I dont want to take to domain. I hope i answered your question.

    Please suggest

  • May 31, 2012 at 8:06 am

    #1495242

    Hey Jasona,

    You pointed well. I tried with local service but it gave same error.

    I think this m/c is renamed. Could you please help me figure out what need to be done such scenario.

    Thanks

  • May 31, 2012 at 8:14 am

    #1495249

    You should try to help yourself, and post back if you come across anything you don't understand. I bet that if you typed "How to rename SQL Server" into your favourite search engine, you'd find what you're looking for.

    John

  • May 31, 2012 at 8:20 am

    #1495257

    Thanks for your kind suggestion.

    I point here is to look for a solution if I am missing anything.

    As I know how to rename the sql instance. Just sending it for your reference

    http://msdn.microsoft.com/en-us/library/ms143799.aspx

    I also checked the new name for the instance it 13179-HP7100.

    Thanks and appriciate your suggetions John.

  • May 31, 2012 at 9:10 am

    #1495307

    Well, for giggles I renamed an SQL Server I have, to see if that would break the Agent service.

    I changed nothing, didn't follow the steps when done to rename an SQL Instance, nothing.

    The Agent service (running as Local System) started up fine. So I may be barking up the wrong tree with your issue.

    So, at this point, I've only got two ideas for you:

    1. If this isn't a production SQL, and you can take it down, uninstall SQL Server completely, then re-install.

    2. If you can't do #1, you might want to consider a support call to Microsoft.

    Sorry I can't be more help at this point...

    Jason A.

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply