Automatic Updates service has hung on starting. However, it does start! Can't get rid of the error.

I have 8 servers in a web farm (Windows 2000 and 2003) and every
morning after the nightly
reboot I will get the error message below:


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
Date: 12/7/2005
Time: 2:55:21 AM
User: N/A
Computer: SERVERNAME
Description:
The Automatic Updates service hung on starting.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


The order that the services are starting is this:


Event Log, various compaq drivers, SNMP, NIC Agents, Server Agents
(HP), Storage Agents (HP), Fondation Agents (HP)...then I get the
above. The event in the log immediately following is this:


Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 12/7/2005
Time: 2:55:21 AM
User: N/A
Computer: SERVERNAME
Description:
Application popup: Service Control Manager : At least one service or
driver failed during system startup. Use Event Viewer to examine the
event log for details.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Like I said there is no problem running Windows Updates. The service
actually does start. Its just annoying because its showing up in MOM
every day. Any ideas on how to get rid of this error? Thank you!!


Gary

"Xtradite" <> wrote in message
news: oups.com
....
>I have 8 servers in a web farm (Windows 2000 and 2003) and every
> morning after the nightly
> reboot I will get the error message below:
>
>
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7022
> Date: 12/7/2005
> Time: 2:55:21 AM
> User: N/A
> Computer: SERVERNAME
> Description:
> The Automatic Updates service hung on starting.


Are there any entries in the WindowsUpdate.log at the same time?
Perhaps there are better clues there?


---