Troubleshooting "FATAL: 0x80070005: ERROR:"
|
Troubleshooting "FATAL: 0x80070005: ERROR: Remote update handler container process created (PID: xxxx), but exited before signaling event"
The problem is that one or more client machise is failing to install updates. If you look at the WindowsUpdate.log file, you'll find entries similar to the following: 2005-08-12 09:49:16 856 690 Agent ************* 2005-08-12 09:49:16 856 690 Agent ** START ** Agent: Installing updates [CallerId = AutomaticUpdates] 2005-08-12 09:49:16 856 690 Agent ********* 2005-08-12 09:49:16 856 690 Agent * Updates to install = 1 2005-08-12 09:49:16 856 690 Agent * Title = <NULL> 2005-08-12 09:49:16 856 690 Agent * UpdateId = <Some GUID> 2005-08-12 09:49:16 856 690 Agent * Bundles 1 updates: 2005-08-12 09:49:16 856 690 Agent * <Some GUID> 2005-08-12 09:49:17 856 690 Handler Attempting to create remote handler process as <Some User> in session 0 2005-08-12 09:49:17 1180 788 Misc =========== Logging initialized (build: 5.8.0.2469, tz: -0400) =========== 2005-08-12 09:49:17 1180 788 Misc = Process: C:\WINNT\system32\wuauclt.exe 2005-08-12 09:49:17 1180 788 AUClnt FATAL: Error: 0x80070005. wuauclt handler: failed to spawn COM server 2005-08-12 09:49:17 856 690 Handler FATAL: 0x80070005: ERROR: Remote update handler container process created (PID: 1180), but exited before signaling event 2005-08-12 09:49:17 856 690 Agent * WARNING: Exit code = 0x80070005 2005-08-12 09:49:17 856 690 Agent ********* 2005-08-12 09:49:17 856 690 Agent ** END ** Agent: Installing updates [CallerId = AutomaticUpdates] 2005-08-12 09:49:17 856 690 Agent ************* 2005-08-12 09:49:17 856 690 Agent WARNING: WU client failed installing updates with error 0x80070005
This error is caused by a DCOM access problem on the machine. The root problem is usually one of two things: First Possible Cause: An incompatible default DCOM impersonation level. To verify that your default level is appropriate and fix the problem, follow these steps
On a Windows 2000 machine: 1) launch "dcomcnfg.exe" 2) choose "Default Properties" 3) in the "Default Impersonation Level" combo box (at the bottom), choose "Impersonate" or "Identify".
On a Windows XP SP2 machine: 1) launch "dcomcnfg.exe" 2) navigate to "Component Services\Computers\My Computer" 3) right click on "DCOM Config" and choose "Properties" 4) choose the "Default Properties" tab 5) select "Impersonate" or "Identify".
If you have a specfic need to choose "Delegate" you choose that option as well, but I would not recommend it as the default choice if it is not required.
Second Possible Cause: Corrupt default access permisisons on the machine It is possible for the default DCOM access permissions on the machine to be corrupted. This can sometimes happen if the DCOMCnfg tool is used to view or edit the default access permission ACLs.
You can check for this situation and resolve this issue by doing the following:
1. launch regedit.exe 2. Locate the following key: HKEY_LOCAL_MACHINE\Software\Microsoft\Ole 3. Look for the value "DefaultAccessPermission" (NOT DefaultLaunchPermission)
If this value exists, it is possible that the value has been corrupted or is incorrect. If you don't have the need for specific default permissions, you can restore the original permissions on the machine by deleting this value (do not delete the entire reg key, just that one value.)
===================== This posting is provided "AS IS" with no warranties, and confers no rights. =====================
Last Modified 9/20/05 1:28 PM
|