SCCM: Failed to instantiate Updates with error 8000401a

[guest]

I am having a problem with some of the clients in my SCCM site. On the ones that I have looked at so far, I am getting a message "Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a" in the execmgr.log. Can anyone tell me what this error means.



I know I just closed the other one yesterday but I found another user with the same error message. here is the logs from the users machine.





Failed to connect to machine policy name space. 0x80004002 execmgr 2/7/2008 3:48:30 PM 1000 (0x03E8)
Failed to connect to user policy name space execmgr 2/7/2008 3:48:31 PM 1000 (0x03E8)
CSoftwareDistPolicyMgr::GetSWDistSiteSettings failed to connect to machine namespace execmgr 2/7/2008 3:48:31 PM 1000 (0x03E8)
Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a execmgr 2/7/2008 3:48:33 PM 1000 (0x03E8)
Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a execmgr 2/7/2008 3:48:33 PM 1000 (0x03E8)
Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a execmgr 2/7/2008 3:48:33 PM 1000 (0x03E8)
The user has logged off. execmgr 2/8/2008 5:03:38 PM 4012 (0x0FAC)
Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (80004002) execmgr 2/8/2008 5:03:53 PM 2052 (0x0804)
Failed to ConnectSettings for ICcmPolicyAgent in CSoftDistPolicyNamespace::ConnectToNamespace execmgr 2/8/2008 5:03:53 PM 2052 (0x0804)
Failed to ConnectToNamespace in CSoftDistPolicyNamespace::GetMachinePolicy execmgr 2/8/2008 5:03:53 PM 2052 (0x0804)
Failed to connect to machine policy name space. 0x80004002 execmgr 2/8/2008 5:03:53 PM 2052 (0x0804)
Failed to connect to user policy name space execmgr 2/8/2008 5:03:53 PM 2052 (0x0804)
CSoftwareDistPolicyMgr::GetSWDistSiteSettings failed to connect to machine namespace execmgr 2/8/2008 5:03:53 PM 2052 (0x0804)
Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a execmgr 2/8/2008 5:03:55 PM 2052 (0x0804)
Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a execmgr 2/8/2008 5:03:55 PM 2052 (0x0804)
Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a execmgr 2/8/2008 5:03:55 PM 2052 (0x0804)
The user has logged off. execmgr 2/8/2008 5:44:10 PM 3452 (0x0D7C)
Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a execmgr 2/8/2008 5:44:19 PM 3180 (0x0C6C)
Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a execmgr 2/8/2008 5:44:19 PM 3180 (0x0C6C)
Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a execmgr 2/8/2008 5:44:19 PM 3180 (0x0C6C)


The last machines I reinstalled the client and that error went away but I am curious as to what this is. The more I look at it and research it to me it looks like it might be having trouble accessing the wmi.



I appreciate any help you might be able to give me.

[guest]

I am getting the same error as shown, and during a software update deployment, not in just one machine, but three.



Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b) execmgr 1/30/2008 6:32:10 PM 3972 (0x0F84)
Failed to ConnectSettings for ICcmPolicyAgent in CSoftDistPolicyNamespace::ConnectToNamespace execmgr 1/30/2008 6:32:10 PM 3972 (0x0F84)
Failed to ConnectToNamespace in CSoftDistPolicyNamespace::GetMachinePolicy execmgr 1/30/2008 6:32:10 PM 3972 (0x0F84)
Failed to connect to machine policy name space. 0x8007045b execmgr 1/30/2008 6:32:10 PM 3972 (0x0F84)
Failed to connect to user policy name space execmgr 1/30/2008 6:32:10 PM 3972 (0x0F84)
CSoftwareDistPolicyMgr::GetSWDistSiteSettings failed to connect to machine namespace execmgr 1/30/2008 6:32:10 PM 3972 (0x0F84)
Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a execmgr 1/30/2008 6:32:10 PM 3972 (0x0F84)
Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a execmgr 1/30/2008 6:32:10 PM 3972 (0x0F84)
Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a execmgr 1/30/2008 6:32:10 PM 3972 (0x0F84)

[guest]

What is involved in rebuilding WMI? I am having an issue where some client won't do a software update scan. I uninstall the client, the force an install of the latest WUA and then re-install the client. Then the update scan works for a day or 2, then fails again. I always get the error "Scan() Failed. Error = 0x80004002. I'm pulling my hair our here. Can not get this resolved going on 4 weeks now.

[guest]

You will find another method online, it never works. Do it this way.





Ccmclean.exe

net stop winmgmt

rename-- Windows\system32\wbem\repository

net start winmgmt

rundll32 wbemupgd, RepairWMISetup



ccmsetup.exe

[guest]

Actually ccmclean is not the recommended way to uninstall the ConfigMgr client. I copied that from an old doc. I have used ccmclean and it seems to work. Use this method instead.



To uninstall the Configuration Manager client

1.Open a Windows command prompt and change the folder to the location in which CCMSetup.exe is located.

2.Type Ccmsetup.exe /uninstall, and then press Enter.

[guest]

ok. Well I've done that. I used ccmsetup.exe /unistall to uninstall the client, then force an install of the latest WUA and then re-install the client. Then the update scan works for a day or 2, then fails again. I always get the error "Scan() Failed. Error = 0x80004002. I'm pulling my hair our here. Can not get this resolved going on 4 weeks now. I've looked everywhere, and no one from microsoft has offered any usefull info other than Wally, but not much he can help with either. I've looked up the error and it says:

No such interface supported. Source: Windows


whatever that means....

[guest]

Technically I don't think this is really even a ConfigMgr issue. Sorta it is because ConfigMgr handles your patches but it's using WSUS to do so and this seems like a WSUS error.



Anyway, here's what a quick Google turns up:





Error 0x80004002
SYMPTOMS

You see the following errors in "%Windir%\WindowsUpdate.log".

FATAL: Failed to get session from datastore, error = 0x80004002
FATAL: Failed to Unserialize from data store, error = 0x80004002
WARNING: Exit code = 0x80004002
WARNING: InitAUComponents Failed, will restart AU in 30 mins, error = 0x80004002
DnldMgr FATAL: DM:CAgentDownloadManager::CheckAllCallDownloadStates: GetSession failed with 0x80004002.

WORKAROUND

Try the following steps; Some of these steps might work. Rename/Delete "%Windir%\WindowsUpdate.log" before you start to see the latest detection.

1. If you have a proxy server -

•Stop Automatic Update Service - "Net stop wuauserv".
•Run the following command: "proxycfg.exe -u".
•Start Automatic Update Service - "Net start wuauserv".
•Force update detection and see if that works.
2. Re-create the Datastore -

•Stop Automatic Update Service - "Net stop wuauserv".
•Rename/delete "%Windir%\SoftwareDistribution" folder.
•Start Automatic Update Service - "Net start wuauserv".
•Force update detection and see if that works.
3. Try to force install WUA.

•Download WUA WindowsUpdateAgent20-x86.exe from http://go.microsoft.com/fwlink/?LinkId=43264.
•and run the following command: "WindowsUpdateAgent20-x86.exe /wuforce".
•Post your results from "%Windir%\WindowsUpdate.log" on microsoft.public.windows.server.update_services.