Discussion Forums/AA Console/Questions
Provider Failure
Adam Ruth
asked this on November 13, 2009 12:08
Provider Failure usually means that there is a DCOM security setting on the target system that needs to be changed.
From your Admin Arsenal console machine go to a command prompt and change directories to your Admin Arsenal directory in Program files\Brisworks
run the following command against a machine that gets the Provider Failure and then against a machine that doesn't. Compare the results:
dcomacls -computer NameOfFailedComputer -viewproperty
dcomacls -computer NameOfSuccessComputer -viewproperty
The Failed computer may have the Authentication and Impersonation values set inappropriately for Remote Management to take place. You want the values
Authentication: Connect
Impersonation: Identify
If the these two values are not, respectively, Connect and Identify then you can use the same tool (dcomacls) to set them.
dcomacls -computer NameOfFailedComputer -property Authentication=Connect -property Impersonation=Identify
A reboot of the target usually needs to take place before the WMI Provider will work.
Comments
Another cause of Provider Load Failure could be that the following path is omitted from the system %PATH% variable:
%WINDIR%\System32\wbem
The target machines has %SystemRoot%\System32\Wbem set in the path variable. Also it has:
Enabled: True
Internet: False
Authentication: Connect
Impersonation: Identify
Reference: False
Any other suggestions?
Another possible cause of Provider Load Failure is corruption in the WMI database. Here's the steps to rebuild it:
As an administrator (and elevated in Vista)
net stop winmgmt
rename the directory %windir%\system32\WBEM\Repository to Repository.old
net start winmgmt
When the WMI service starts back up, it will rebuild its database