I have 8 servers in a web farm 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

Hi Gary,

Can you attach the WindowsUpdate.log file under %windir%? It should contain
the error message why it failed.

Also try:
sfc /scannow

Insert WinXP CD and let it scan and replace the files.

Hope this works.

--
Jabez Gan
Windows Server 2003 R2 Beta Mentor
http://www.blizhosting.com
MSBLOG: http://msblog.resdev.net


<gary@gjsolutions.net> wrote in message
news:1133962117.136218.255180@g49g2000cwa.googlegr oups.com...

Jabez,

Thanks for your reply. Here is the end of yesterdays log and today's.
The box is rebooting around 2:45 AM.

05-12-06 21:55:08 3404 a30 AU #########
2005-12-06 21:55:08 3404 a30 AU ## END ## AU: Search for updates
[CallId = {2FEA1876-AF39-4530-9749-429C16B0A8DA}]
2005-12-06 21:55:08 3404 a30 AU #############
2005-12-06 21:55:08 3404 a30 AU AU setting next detection timeout to
2005-12-07 21:10:59
2005-12-06 21:55:13 3404 a30 Report REPORT EVENT:
{D21EB4FA-17B1-487B-822A-C385D95F0B5C} 2005-12-06
21:55:08-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
2005-12-07 02:50:44 3404 ad0 DtaStor FATAL: Failed to initialize
datastore, error = 0xC8000711
2005-12-07 02:50:44 3404 ad0 AU FATAL: Failed to get session from
datastore, error = 0xC8000711
2005-12-07 02:50:47 3404 ad0 Service *********
2005-12-07 02:50:47 3404 ad0 Service ** END ** Service: Service exit
[Exit code = 0x240001]
2005-12-07 02:50:47 3404 ad0 Service *************
2005-12-07 02:54:14 1004 3f0 Misc =========== Logging initialized
(build: 5.8.0.2469, tz: -0500) ===========
2005-12-07 02:54:14 1004 3f0 Misc = Process:
C:\WINNT\system32\svchost.exe
2005-12-07 02:54:14 1004 3f0 Misc = Module:
C:\WINNT\system32\wuaueng.dll
2005-12-07 02:54:14 1004 3f0 Service *************
2005-12-07 02:54:14 1004 3f0 Service ** START ** Service: Service
startup
2005-12-07 02:54:14 1004 3f0 Service *********
2005-12-07 02:54:14 1004 3f0 Agent * WU client version 5.8.0.2469
2005-12-07 02:54:14 1004 3f0 Agent * SusClientId =
'6c20c925-b658-4abc-bf84-be44d14b465c'
2005-12-07 02:54:14 1004 3f0 Agent * Base directory:
C:\WINNT\SoftwareDistribution
2005-12-07 02:54:14 1004 3f0 Agent * Access type: No proxy
2005-12-07 02:55:21 1004 3f0 Agent * Network state: Connected
2005-12-07 02:56:06 1004 3f0 Agent *********** Agent: Initializing
Windows Update Agent ***********
2005-12-07 02:56:06 1004 3f0 Agent *********** Agent: Initializing
global settings cache ***********
2005-12-07 02:56:06 1004 3f0 Agent * WSUS server: <NULL>
2005-12-07 02:56:06 1004 3f0 Agent * WSUS status server: <NULL>
2005-12-07 02:56:06 1004 3f0 Agent * Target group: (Unassigned
Computers)
2005-12-07 02:56:06 1004 3f0 Agent * Windows Update access disabled:
No
2005-12-07 02:56:08 1004 3f0 DnldMgr Download manager restoring 0
downloads
2005-12-07 02:56:08 1004 3f0 AU ########### AU: Initializing Automatic
Updates ###########
2005-12-07 02:56:08 1004 3f0 AU # Approval type: Scheduled (User
preference)
2005-12-07 02:56:08 1004 3f0 AU # Scheduled install day/time:
Thursday at 2:00
2005-12-07 02:56:08 1004 3f0 AU # Auto-install minor updates: Yes
(User preference)
2005-12-07 02:56:08 1004 3f0 AU AU setting pending client directive to
'Install Approval'
2005-12-07 02:56:22 1004 3f0 AU WARNING: AU found no suitable session
to launch client in
2005-12-07 10:38:01 1004 3f0 AU AU found 1 sessions to launch client
into
2005-12-07 10:38:01 1004 3f0 AU Launched new AU client for directive
'Install Approval', session id = 0x0
2005-12-07 10:38:01 3460 d88 Misc =========== Logging initialized
(build: 5.8.0.2469, tz: -0500) ===========
2005-12-07 10:38:01 3460 d88 Misc = Process:
C:\WINNT\system32\wuauclt.exe
2005-12-07 10:38:01 3460 d88 AUClnt Launched Client UI process
2005-12-07 10:38:01 3460 d88 AUClnt AU client got new directive =
'Install Approval', serviceId = {9482F4B4-E343-43B6-B170-9A65BC822C77},
return = 0x00000000
2005-12-07 10:38:01 3460 d88 AUClnt AU client creating default WU/WSUS
UI plugin
2005-12-07 10:38:01 1004 db4 AU AU setting client response for
sessionId 0x0 to 'Pending'

Hi,

You are getting error 0xC8000711. Please try the solutions below:

1. Start > Run
2. Type:
services.msc
3. Make sure that the services:
Automatic Updates
Background Intelligent Transfer Service
Event Log

are set to Automatic.

Hope this helps.

--
Jabez Gan
Windows Server 2003 R2 Beta Mentor
http://www.blizhosting.com
MSBLOG: http://msblog.resdev.net


"Xtradite" <gary@gjsolutions.net> wrote in message
news:1133970146.599615.251640@f14g2000cwb.googlegr oups.com...

Initially BITS was set to Manual so on Monday I set it to Automatic and
started it. Then Tuesday morning I checked the event log and the same
error appeared (AU hung on starting) so I set it back to Manual.

Gary

Hi,

Those 3 services should be set to Automatic, and not Manual or Disable.
Please double check and make sure that it's all set to Automatic.

Also, please see:
http://support.microsoft.com/kb/822798/

Try the methods listed there.

--
Jabez Gan
Windows Server 2003 R2 Beta Mentor
http://www.blizhosting.com
MSBLOG: http://msblog.resdev.net


"Xtradite" <gary@gjsolutions.net> wrote in message
news:1133973780.043841.260620@o13g2000cwo.googlegr oups.com...

Right...like I said I tried it on automatic and then that didn't fix
the problem so I changed it back. I'll set them all to Auto but its
got to be something else.

None of the symptoms listed in the article above are my symptoms and
the one that pertains to the windowsupdate.log that error doesn't
appear in my log. Any other ideas?

Gary

Please see:

http://groups.google.com/group/micro...aa9c6bbc?hl=en

The previous link I gave you is a generic troubleshooting method for WIndows
Update. You can skip the others, but it's recommended that you try Method
1 - 4 .

If all fails,

http://support.microsoft.com/gp/wusupport

--
Jabez Gan
Windows Server 2003 R2 Beta Mentor
http://www.blizhosting.com
MSBLOG: http://msblog.resdev.net



"Xtradite" <gary@gjsolutions.net> wrote in message
news:1134048172.479423.194920@g47g2000cwa.googlegr oups.com...

You think I should change the Cyptographic and Catroot methods to try
to fix the AU error on bootup?