February 24, 2012 at 4:24 am
Hello All,
I have noticed that SQL Agent does not start automatically after a reboot/shutdown on a few of our servers (SQL server starts up fine). The service is set to automatically start in windows. When we start SQL agent manually, it starts fine.
I have had a look in the logs and a few errors stand out to me
Log Name: Application
Source: SQLSERVERAGENT
Date: 07/02/2012 08:35:47
Event ID: 103
Task Category: Service Control
Level: Error
Keywords: Classic
User: N/A
Computer: Server.domain
Description:
SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="SQLSERVERAGENT" />
<EventID Qualifiers="16384">103</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-02-07T08:35:47.000Z" />
<EventRecordID>1162704</EventRecordID>
<Channel>Application</Channel>
<Computer>server.domain </Computer>
<Security />
</System>
<EventData>
<Data>Unable to connect to server '(local)'; SQLServerAgent cannot start</Data>
</EventData>
</Event>
Log Name: Application
Source: MSSQLSERVER
Date: 07/02/2012 08:35:47
Event ID: 17892
Task Category: Logon
Level: Error
Keywords: Classic
User: domain\server
Computer: server.domain
Description:
Logon failed for login 'domain\user' due to trigger execution. [CLIENT: <local machine>]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSSQLSERVER" />
<EventID Qualifiers="49152">17892</EventID>
<Level>2</Level>
<Task>4</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-02-07T08:35:47.000Z" />
<EventRecordID>1162703</EventRecordID>
<Channel>Application</Channel>
<Computer>server.domain</Computer>
<Security UserID="S-1-5-21-1220945662-507921405-1060284298-9196" />
</System>
<EventData>
<Data>Domain\User</Data>
<Data> [CLIENT: <local machine>]</Data>
<Binary>E4450000140000000E000000530046002D00530051004C002D004400450056002D0030003200000000000000</Binary>
</EventData>
</Event>
Has anyone got any ideas? Any help would be much appreciated
Thanks,
Dan 😛
February 24, 2012 at 4:28 am
looks like you have a logon trigger enabled, i would suggest looking at that and trying to add the agent account access to login.
February 24, 2012 at 4:55 am
If the service starts ok manually and the logon trigger is doing something that's complicated/dependent on another windows service that's in the process of coming up when the server gets rebooted, you might want to experiment with the Automatic (Delayed Start) option, which will effectively make the SQL Agent the last thing to start.
February 24, 2012 at 5:27 am
This sounds like it could help. I'll take a look into this. Thanks.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply