Software Center error. 0x80041013 (-2147217389)

Question

Hi.
When some of our users open Software Center they get this error:
Software Center cannot get the current status for some of the software. Software Center will list any items with available status. You can press F5 to refresh the view. If the problem persists, contact your help desk.
More information:
Loading Software Center teturned error code 0x0041013 (-2147217389).
If they try to start an application via the link "Find additional applications from the Application Catalog" the get this error from
SCClient_XXX@xxx_.log file under c:\windows\CCM\logs:
Exception Microsoft.SoftwareCenter.Client.Data.WmiException: Provider load failure    (Microsoft.SoftwareCenter.Client.Common.ClientUXMain at RetreiveDataComplete)
The error code is ProviderLoadFailure   (Microsoft.SoftwareCenter.Client.Data.WmiException at get_ErrorCode)
I have tried to uninstall the SCCM client, cleaned up everything and installed the client again. Tried to reset repository under c:\windows\system32\wbem and installed the client again with no luck.
Any ideas?
Thanks.
MHem

Answer 1

see
http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx
it's an older article, but very likely to be useful.
Note that ConfigMgr2012 clients should be running a nightly ccmeval, which includes an auto-diagnostic of WMI, so, is ccmeval running? Reporting success/health?
Also, this article describes how to re-register the DLLs and recompile MOFs:
http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx
based on the symptom you've mentioned, you need to focus on if the WMI repository is healthy or not, and, if the underlying WMI system (providers, registrations) is healthy.
When you uninstall CCM, the CCM namespace should get deleted, and when you reinstall, the CCM namespace gets re-created, but, if the providers or underlying WMI system is unhealthy, the CCM namespace may not be useable.
Is Windows itself healthy? Has something bad happened to a dependency? Other errors in the event logs?
As Joyce says, check the client installation logs to see if related errors were logged when the client installation occurred.
As an example (similar symptom):
http://social.technet.microsoft.com/wiki/contents/articles/14408.troubleshooting-fim-wmi-provider-load-failure.aspx
In this case, something has changed the ACL, causing the provider to be access_denied.
Do you have custom security policies, or security products, which could be denying the service access to the provider?
Another set of hints/tips here:
http://stackoverflow.com/questions/563150/how-can-i-resolve-a-provider-load-failure-for-wmi-requests
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)