SCCM Client Problem
Wally,
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.
Carol Allen
Answers
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
- Marked As Answer byEric Mowery [MSFT] Thursday, February 05, 2009 8:47 PM
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
-
Open a Windows command prompt and change the folder to the location in which CCMSetup.exe is located.
-
Type Ccmsetup.exe /uninstall, and then press Enter.
- Marked As Answer byEric Mowery [MSFT] Thursday, February 05, 2009 8:47 PM
-
All Replies
I'm having the exact same problem at a client site right now. I have not totally assessed the issue yet...A quick check with dev indicates the only time they've seen this has been with WMI issues on the client. He asked for a full set of client logs. I'm getting a special email alias set up that we can use to get logs sent to use until the forums provide some ability to attach files.
For now, you could check WMI to see if you are having issues and I'll let you know the account when I get confirmation that it is available.
Wally,
By any chance have the email alias been set up so that I can forward some of the logs.
Carol Allen
Sure, sccmlogs@microsoft.com
Obviously be sure that the logs include the problem so all can be looked at :-)
Hey Wally how are you doing?
I was wondering if you found anything out about the client with the errors. I am seeing a bunch of clients with the below errors in the execmgr.log
Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a
Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a
Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a
Thanks
Yamini
- Nothing yet, let me ping the devs again.
Oh, and Hi Yamini - hope all is well with you.
FYI:
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)
RamonWally,
I have at least one client that is having the same issue. Two questions, would it be helpful if I sent the logs from this client to the list that you posted? If so, then which logs if not all of them. It may also be helpful to note that this particular client is installed and sees the MP, but the MP does not reflect that the client is installed.
We already have logs from Carol, it is just a matter of getting the devs to find the time to look at this. Really this is a product support issue, as the devs are working on the next major release of Configuration Manager. They had asked for them a couple of weeks ago, but now may be on coding windows, so not having the time to look at logs for Configuration Manager 2007 :-(
I'm still trying to get them to look. Otherwise, if someone has the ability to open a case with product support, they may be able to get an answer more quickly (unfortunately).
- Was this resolved? If so how? I am seeing a client with the same issue.
The only response I've gotten from dev on this is:
Although this is not the exact set of logs matching the below pasted logs. But I see similar issues here as well. The user log off and shutdown in progress whenever I see these errors. And it is expected to see these kind of intermittent errors in timing conditions with system shutdown. There should not be any net negative effect though. If we are really seeing that user is not getting notification when he is logged on. Or some programs are not being executed then we may need to investigate further.
If things sort themselves out, then as expected. Otherwise, dev says further investigation is needed. My guess is a full set of client logs as this is occuring, a statement of what the problem is (not just that I see this error in the logs), and the repro steps if possible.
kewl, thanks Wally.
I went ahead and rebuilt WMI and re-installed the client to be on the safe side.
- 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.
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
- Marked As Answer byEric Mowery [MSFT] Thursday, February 05, 2009 8:47 PM
- Where is can I get Ccmclean.exe? I have already installed the ConfigMgr 2007 Toolkit and I've searched the computer and there is no "Ccmclean.exe"
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
-
Open a Windows command prompt and change the folder to the location in which CCMSetup.exe is located.
-
Type Ccmsetup.exe /uninstall, and then press Enter.
- Marked As Answer byEric Mowery [MSFT] Thursday, February 05, 2009 8:47 PM
-
- Ahh, 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.... I dunno if your problem is actually WMI. I was just saying if you wanna rebuild WMI do the steps I sent. Except I sent the 2003 way of removing the client and adding it back. For 2007 it would be
ccmsetup.exe /unistall
net stop winmgmt
rename-- Windows\system32\wbem\repository
net start winmgmt
rundll32 wbemupgd, RepairWMISetup
ccmsetup.exe
- Thanks for the info. Tried it. The client scans once succesfully, then second scan gets error 0x80004002 again.
I didn't think WMI was the issue. Your error indicates the machine isn't connecting to the server correctly. I am sure you have recreated the local datastore? You don't have a proxy server do you? I seem to recall some issues with proxies early on but I think that was resolved.
I would call PSS.
- Thanks for the help! I'm a little new to SMS/SCCM. What do you mean by "recreating the local DataStore"? I will call PSS though!
Thanks again! 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.
-
We tried the WMI rebuild that failed.. But in our case this is only affecting the Win 2003 64Bit Domain controllers. Other Domain controllers that are Win2003 32bit are fine. Also any non DC Win 2003 64Bit servers are fine. We thought this might be a GPO issue but since we have all DC’s the same container that was ruled out.
Reinstalling the client from scratch the error is still produced and the client basically fails to install. EXECMGR.log shows the errors and stops at that point. This seems to be a major bug and was considering opening a MS case on this. WSUS fix might address the clients that are already installed but does not affect the newly installed clients.
Hopefully someone finds an answer.
I see this issue on all my clients - even newly installed ones, and the WMI fix does not solve the issue. I also don't see the windowsupdate.log errors reported above.
I noticed it started after I turned on the software updates component yesterday, and told clients to get updates from the active SUP on the site server. I've turned it off to see if that was the trigger, but this is a showstopper issue, obviously, as I can't really continue using SCCM with all the clients dead to the world.
I should note that after I see the "Failed to instantiate UI Server" errors in my execmgr.log, my client basically goes dead. It never logs another entry in any log, none of the manual policy update actions work. I've seen some instances where people get these errors but the client still works...this is not one of them.
Thanks,
Andrew
- Did anyone ever get any feedback on the fix for this? I am also experiencing the same errors as reported in this thread.
- I have heard that they are similar to errors "WTSQueryUserToken[2](SessionID=0) failed with GLE=1245" which appeared when SMS 2003 SP3 was upgraded, which could be ignored, see MS article and MyITForum post
Wally can you confirm/deny that, there seems to be quite a few people enquiring about the Failed to instantiate UI errors, but nothing definitive has been posted on various forums for this.
Would sending in a complete set of logs help to analyse it?
Thanks.
Ricky.
- I seem to get this error on a huge percentage of clints in the estate. I don't think it causes any issues but would be interested to know what's causing it and if any fix has been fonud.
Pesky WMI!
Cheers all.
Mark. - I'm not sure if this helps anyone, but I had the same errors appear after I imaged a PC which was connected to a Cisco IP phone. I noticed that there was no MAC address reference under the System Properites tab in the Configuration Manager Client. The phone would mask the MAC address of the PC so SCCM could not deloy the policy settings to the client...
This created 'Failed to instansiate UI Server' and 'Software Client Agent Settings for the client are missing from WMI' errors in the execmgr.log file.
Regards,
Alistair - I know this is an old thread but has there been any solution for this problem? Seeing on a lot of our workstations.
- The MAC could be an issue or maybe not. I have a computer with this problem and it has a MAC address.
Anyone seen any kind of resolution to this problem yet? Did anyone ever initiate a problem ticket with Microsoft? - Hi,I have noticed one problem similar to this.After Patch Deployment through SCCM the Servers are not being rebooted.The Software updates are being deployed on them, Evaluation is also successful, but post deployment the Servers are not being rebooted. While I have checked the logs, I found the following under ccmexec.log & reboot coordinator.log:CRebootCoordinator:Reboot Coordinator received a SERVICEWINDOWEVENT START Event RebootCoordinator 7/16/2009 6:00:00 PM 5604 (0x15E4)Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a RebootCoordinator 7/16/2009 6:01:16 PM 6976 (0x1B40)Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a RebootCoordinator 7/16/2009 6:01:16 PM 6976 (0x1B40)Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a RebootCoordinator 7/16/2009 6:01:16 PM 6976 (0x1B40)Failed to instantiate VApp UI Server {00AAB372-0D6D-4976-B5F5-9BC7605E30BB} with error 0x8000401A RebootCoordinator 7/16/2009 6:01:16 PM 6976 (0x1B40)Unable to notify client UI of jobs started. Code 0x80040154 RebootCoordinator 7/16/2009 6:01:16 PM 6976 (0x1B40)Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a RebootCoordinator 7/16/2009 6:04:21 PM 8664 (0x21D8)Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a RebootCoordinator 7/16/2009 6:04:21 PM 8664 (0x21D8)Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a RebootCoordinator 7/16/2009 6:04:21 PM 8664 (0x21D8)Failed to instantiate VApp UI Server {00AAB372-0D6D-4976-B5F5-9BC7605E30BB} with error 0x8000401A RebootCoordinator 7/16/2009 6:04:21 PM 8664 (0x21D8)Unable to notify client UI of completed jobs. Code 0x80040154 RebootCoordinator 7/16/2009 6:04:21 PM 8664 (0x21D8)CRebootCoordinator:Reboot Coordinator received a SERVICEWINDOWEVENT END Event RebootCoordinator 7/16/2009 11:55:00 PM 6148 (0x1804)Seems to be some WMI error. I have followed the process mention in the earlier part of this section for one server. But I don't know whether it is succeed or not? How do I check that? Also how do I do this for all server? then it would be very tough to take one-by-one manually and apply the fix.Please Help!!!!
- I just ran into this myself. I was seeing false-negative results on some patches. The clients all seem to work just fine, they're sending inventory, they're getting software, but they don't appear to be returning update status properly.
So, I tried a client repair. No good.
I tried a WMI repair. No good.
I uninstalled and reinstalled the client completely. No good.
The only thing that worked was (using SCCM Client Center from Roger Zander) using the "Recreate Repository" button which totally rebuilds the WMI repository and does a client repair.
Number2 - (John Nelson)
Microsoft MVP - System Center Configuration Manager
http://number2blog.com
