S
StanFaeSLC
Hi there.
I hope this is the right forum/category.
We have had an ongoing issue with our PCs displaying errors indicating corrupt WMI. In the sccm client “execmgr” log-file, the following entry appears:
“Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a”
The Technet article at the link below suggest that this indicates a corrupt WMI:
http://social.technet.microsoft.com.../thread/471d1211-5dbe-481f-aa85-2690b8089070/
This can be fixed uninstalling the sccm client, repairing WMI, then reinstalling sccm.
However, as this issue has now appeared fairly regularly, I am keen to know if there could be any underlying cause for this? Could there be anything in our environment which might be causing WMI to become corrupt, or is this something we will have to learn to live with?
Our organisation covers a wide geographic area, and as the recommended fix, as per link above, required sccm client to be removed & re-installed, we cannot fix this problem remotely.
Also, while I can easily collect the execmgr.log files using sccm software inventory, there doesn’t appear to be any quick method of scanning these logs for the “Failed to instantiate …” entry, which would allow us to ascertain the scope of the problem. (See technet forum thread here: - http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/1ae884cc-dda3-4ffa-b640-e19b382c03e0)
We run XP SP3 on our PCs, and have an estate of approx 5000 PCs.
Any suggestions what might be causing this, how we could fix it remotely, or how to scan the execmgr log file throughout the estate to ascertain the scope of the problem?
Thanks
Stan
Continue reading...
I hope this is the right forum/category.
We have had an ongoing issue with our PCs displaying errors indicating corrupt WMI. In the sccm client “execmgr” log-file, the following entry appears:
“Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a”
The Technet article at the link below suggest that this indicates a corrupt WMI:
http://social.technet.microsoft.com.../thread/471d1211-5dbe-481f-aa85-2690b8089070/
This can be fixed uninstalling the sccm client, repairing WMI, then reinstalling sccm.
However, as this issue has now appeared fairly regularly, I am keen to know if there could be any underlying cause for this? Could there be anything in our environment which might be causing WMI to become corrupt, or is this something we will have to learn to live with?
Our organisation covers a wide geographic area, and as the recommended fix, as per link above, required sccm client to be removed & re-installed, we cannot fix this problem remotely.
Also, while I can easily collect the execmgr.log files using sccm software inventory, there doesn’t appear to be any quick method of scanning these logs for the “Failed to instantiate …” entry, which would allow us to ascertain the scope of the problem. (See technet forum thread here: - http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/1ae884cc-dda3-4ffa-b640-e19b382c03e0)
We run XP SP3 on our PCs, and have an estate of approx 5000 PCs.
Any suggestions what might be causing this, how we could fix it remotely, or how to scan the execmgr log file throughout the estate to ascertain the scope of the problem?
Thanks
Stan
Continue reading...