2005 Agent doesn't start automatically on reboot

We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
machine is rebooted, the SQL Server agent is not automatically started.
It is set to start automatically in the Windows Services dialog. I
see a safe shutdown prior to the reboot, but no messages like it's even
trying to start up. I can start it manually with no problems.
Any ideas what to check or where to go from here?Hi
Have you checked the sql server agent log file in Management studio? Also
check what SQL Server Configuration Manager has for the service and check
that error reporting is selected on the advanced tab.
John
"PSPDBA" wrote:
> We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> machine is rebooted, the SQL Server agent is not automatically started.
> It is set to start automatically in the Windows Services dialog. I
> see a safe shutdown prior to the reboot, but no messages like it's even
> trying to start up. I can start it manually with no problems.
> Any ideas what to check or where to go from here?
>|||Agent log shows:
Message
[241] Startup error: Unable to initialize error reporting system
(reason: The EventLog service has not been started)
However, The EventLog service is also set to automatic.
John Bell wrote:
> Hi
> Have you checked the sql server agent log file in Management studio? Also
> check what SQL Server Configuration Manager has for the service and check
> that error reporting is selected on the advanced tab.
> John
> "PSPDBA" wrote:
> > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > machine is rebooted, the SQL Server agent is not automatically started.
> > It is set to start automatically in the Windows Services dialog. I
> > see a safe shutdown prior to the reboot, but no messages like it's even
> > trying to start up. I can start it manually with no problems.
> >
> > Any ideas what to check or where to go from here?
> >
> >|||Hi
I assume that the EventLog has started correctly?
Making SQL Agent dependent on the EventLog service would ensure that it has
started before SQL Agent starts.
If the service is running as LOCALSYSTEM you could change it to an domain
account.
John
"PSPDBA" wrote:
> Agent log shows:
> Message
> [241] Startup error: Unable to initialize error reporting system
> (reason: The EventLog service has not been started)
> However, The EventLog service is also set to automatic.
> John Bell wrote:
> > Hi
> >
> > Have you checked the sql server agent log file in Management studio? Also
> > check what SQL Server Configuration Manager has for the service and check
> > that error reporting is selected on the advanced tab.
> >
> > John
> >
> > "PSPDBA" wrote:
> >
> > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > machine is rebooted, the SQL Server agent is not automatically started.
> > > It is set to start automatically in the Windows Services dialog. I
> > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > trying to start up. I can start it manually with no problems.
> > >
> > > Any ideas what to check or where to go from here?
> > >
> > >
>|||Yep, it sure has. I was thinking of doing both of those things. I'll
give it a try.
John Bell wrote:
> Hi
> I assume that the EventLog has started correctly?
> Making SQL Agent dependent on the EventLog service would ensure that it has
> started before SQL Agent starts.
> If the service is running as LOCALSYSTEM you could change it to an domain
> account.
> John
> "PSPDBA" wrote:
> > Agent log shows:
> >
> > Message
> > [241] Startup error: Unable to initialize error reporting system
> > (reason: The EventLog service has not been started)
> >
> > However, The EventLog service is also set to automatic.
> >
> > John Bell wrote:
> > > Hi
> > >
> > > Have you checked the sql server agent log file in Management studio? Also
> > > check what SQL Server Configuration Manager has for the service and check
> > > that error reporting is selected on the advanced tab.
> > >
> > > John
> > >
> > > "PSPDBA" wrote:
> > >
> > > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > > machine is rebooted, the SQL Server agent is not automatically started.
> > > > It is set to start automatically in the Windows Services dialog. I
> > > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > > trying to start up. I can start it manually with no problems.
> > > >
> > > > Any ideas what to check or where to go from here?
> > > >
> > > >
> >
> >|||Hi
You didn't say if the service was running under local system or not'
Looking at other posts http://tinyurl.com/rvql2 the service account seems to
be a prime reason for this failure. To change this manually check out
http://support.microsoft.com/?id=283811
John
"PSPDBA" wrote:
> Yep, it sure has. I was thinking of doing both of those things. I'll
> give it a try.
>
> John Bell wrote:
> > Hi
> >
> > I assume that the EventLog has started correctly?
> >
> > Making SQL Agent dependent on the EventLog service would ensure that it has
> > started before SQL Agent starts.
> >
> > If the service is running as LOCALSYSTEM you could change it to an domain
> > account.
> >
> > John
> >
> > "PSPDBA" wrote:
> >
> > > Agent log shows:
> > >
> > > Message
> > > [241] Startup error: Unable to initialize error reporting system
> > > (reason: The EventLog service has not been started)
> > >
> > > However, The EventLog service is also set to automatic.
> > >
> > > John Bell wrote:
> > > > Hi
> > > >
> > > > Have you checked the sql server agent log file in Management studio? Also
> > > > check what SQL Server Configuration Manager has for the service and check
> > > > that error reporting is selected on the advanced tab.
> > > >
> > > > John
> > > >
> > > > "PSPDBA" wrote:
> > > >
> > > > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > > > machine is rebooted, the SQL Server agent is not automatically started.
> > > > > It is set to start automatically in the Windows Services dialog. I
> > > > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > > > trying to start up. I can start it manually with no problems.
> > > > >
> > > > > Any ideas what to check or where to go from here?
> > > > >
> > > > >
> > >
> > >
>