WMI ADAP failed to connect to namespace

I periodically receive the following warning:

WMI ADAP failed to connect to namespace \\.\root\cimv2 with the following error: 0x80080005

I believe that this may be a symptom of a larger problem with my SBS2003 PE installation.  Any suggestions?
ericallanobergAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
What were the events logged when this happens?  Canceling the pop-up message should generate a couple more system event messages.  

Jeff
TechSoEasy
ericallanobergAuthor Commented:
Event Type:      Warning
Event Source:      WinMgmt
Event Category:      None
Event ID:      43
Date:            3/11/2006
Time:            11:46:13 AM
User:            N/A
Computer:      AIS00051ENGSERV
Description:
WMI ADAP failed to connect to namespace \\.\root\cimv2 with the following error: 0x80080005

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Warning
Event Source:      WinMgmt
Event Category:      None
Event ID:      60
Date:            3/11/2006
Time:            11:46:13 AM
User:            N/A
Computer:      AIS00051ENGSERV
Description:
WMI ADAP was unable to process the performance libraries: 0x80041001

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I think you're on the right track... were the PE and the Server Media different language versions?

Jeff
TechSoEasy
C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

ericallanobergAuthor Commented:
No.  In addition, the Help and Support Center is likewise not functioning from my SBS2003 so I am unable to utilize the indicated links.  Doing a manual search on the error description did not yield a definitive solution.
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Okay,  I did a bit of digging and came up with these steps.  Please realize that I cannot replicate your problem, so this is fully untested, but it did make sense to me:

go to:

C:\WINNT\system32\wbem\Repository

in there you will find a file named:

$WinMgmt.CFG  --- rename this file to $WinMgmt.CFG.old

SHUT DOWN... and Power Back Up again... when you log back in it will give you the same message once... wait till the OK button appears (this should restart WinMgmt.exe)...
CLICK OK... and you should be good to go...

if for some reaspon WinMgmt.exe doesn't automatically start you can double-click it at:

C:\WINNT\system32\wbem\winmgmt.exe


Jeff
TechSoEasy

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ericallanobergAuthor Commented:
Jeff,
Your suggestion does not seem to be appropriate for SBS2003.  Have you another?
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Why would you say that it's not appropriate?  Your WMI configuration seems to be corrupt from those error messages.  Trying my suggestion wouldn't hurt, since you can always go back in Safe Mode and change the name of the $WinMgmt.CFG back to it's original name.

Jeff
TechSoEasy
ericallanobergAuthor Commented:
Jeff,
I did not mean to imply that your suggestion was not a good one but the my SBS2003 installation does not have a WINNT folder.  I have since figured out that C:\WINNT\system32\wbem\Repository should be C:\Windows\system32\wbem\Repository.  I will try your solution ASAP.
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Sorry, I should have put %WINDOWS% instead.  :-)
ZadkinCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I will leave the following recommendation for this question in the Cleanup topic area:
    Accept: TechSoEasy {http:#16351980}

Any objections should be posted here in the next 4 days. After that time, the question will be closed.

Zadkin
EE Cleanup Volunteer
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.