MSSQLSERVER 2005 service failed to start only on Windows startup

MSSQLServer service will not start when I startup Windows Server 2003
Std, but when I start the service manually, it works.
Here is the event (ID: 7000, Source: Service Control Manager) recorded:
The SQL Server (MSSQLSERVER) service failed to start due to the
following error:
%%6057960
I don't see anything in the SQL Server Logs for the initial attempt to
startup. Anyone have any ideas? I had set the service's Recovery for
First Failure to "Restart the Service" with "Reset Service after" set
to 5 minutes, but it hasn't worked.
Any ideas?Hi
I have not seen your error, it seems like the error message is not well
formed!
Has the server been starting ok previously?
Have you installed any patches/updates since it was last re-started?
If you change the service account does it start?
Are any other services failing to start?
John
"ccjjharmon@.gmail.com" wrote:

> MSSQLServer service will not start when I startup Windows Server 2003
> Std, but when I start the service manually, it works.
> Here is the event (ID: 7000, Source: Service Control Manager) recorded:
> The SQL Server (MSSQLSERVER) service failed to start due to the
> following error:
> %%6057960
>
> I don't see anything in the SQL Server Logs for the initial attempt to
> startup. Anyone have any ideas? I had set the service's Recovery for
> First Failure to "Restart the Service" with "Reset Service after" set
> to 5 minutes, but it hasn't worked.
> Any ideas?
>|||John,
I was wondering if the message was complete or not too...
It is a relatively new server (few months old) - but it has been
happening really since we installed yet... I am not sure if it ever
started up as a service on reboot.
No patches/updates since last restart (but Windows Update has them
downloaded - they just haven't been installed yet).
I haven't tried changing the service account... but didn't think to
because it starts when I manually start it - just not when all services
normally startup automatically.
SQLServerAgent also doesn't start - but all other services set to
Automatic startup go fine.|||I also checked to make sure the recent event mirrored the same text as
previous events and it does ... BUT the same error was only recorded
two other times (twice on 4/7). Before then, this event was instead
recorded (but I believe SQL Server still wasn't started as a service
automatically):
The SQL Server Integration Services service failed to start due to the
following error:
Waiting for a process to open the other end of the pipe.
Hope this info helps...
Chris