Skip to main content

sms: wbem_e_provider_load_failure causing odd sms client issues...

these are just as cryptic as it sounds since you don't really have any idea which provider is failing to load. the actual failure message looks like this: 0x80041013 - WBEM_E_PROVIDER_LOAD_FAILURE. your ccmexec.log may have exhibit strange errors like this:
Error loading service settings. Code 0x80041013 Phase 0 initialization failed (0x80041013) Service initialization failed (0x80041013)
if you're seeing these strange error messages, here's something you can try to fix it up:
  1. switch over to %windir%\system32\wbem.
  2. register all of the .dlls in this directory. here's a way that microsoft support stated:
    • for /f %s in ('dir /b *.dll') do regsvr32 /s %s
  3. issue the following two commands:
    • wmiprvse /regserver
    • winmgmt /regserver
if this doesn't resolve it, try the steps again. this time, add in step 2b (below). i'm not sure under what condition this occurs, but we found that we had to register tscfgwmi.dll. you'd perform it doing this:
2b. regsvr32 %windir%\system32\tscfgwmi.dll
please let me know if this works for you. i'm curious how many others have experienced it.
Labels:

Comments

  1. Anonymous6/5/09, 11:10 PM

    OK, I googled this error message and found this blog. Any chance of more un-savy users to figure this out?

    ReplyDelete
  2. Marcus Oh6/6/09, 12:36 PM

    not sure i follow... you mean you don't understand the post?

    ReplyDelete
  3. Barry12/9/09, 4:01 AM

    Seems to be working for me, SMS Agent started ok. I found that restarting WMI was often enough to sort it out for a while. However it then died after. I shall see how those fixes get on, oddly it only happens on some servers and not them all... mm

    ReplyDelete
  4. Marcus Oh12/9/09, 8:30 AM

    yes, i think it depends on the level of corruption. wmi is way too sensitive in my opinion. hoping all the hardening steps introduced in later service packs, hotfixes, and operating systems will put a cork in that problem permanently. thanks for the comment, barry.

    ReplyDelete

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
11 comments
more »

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off
3 comments
more »

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m
3 comments
more »