Exchange - MAD.exe monitoring error

I started getting this error this morning. I have updated the default domain controller policy, impersonate a client after authentication, and restarted exchange services. The first error occurs every 3 minutes but the second error just came up as well.

Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      Monitoring
Event ID:      9104
Date:            4/23/2006
Time:            7:07:07 AM
User:            N/A
Computer:      SK2EXW2K3
The MAD Monitoring thread was unable to read the CPU usage information, error '0x80041033'.

For more information, click

Event Type:      Warning
Event Source:      MSExchangeDSAccess
Event Category:      LDAP
Event ID:      2115
Date:            4/23/2006
Time:            5:25:51 PM
User:            N/A
Computer:      SK2EXW2K3
Process INETINFO.EXE (PID=2516). DSAccess needs to close a connection to the Domain Controller due to error 0x80040951.

For more information, click

Who is Participating?

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

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.

From a quick nosey around the web it looks like WMI is having problems on the server.
Apparently installing exchange service pack 2 should fix these kinds of errors.
Have you already installed sp2??


Dave J
llib21Author Commented:
SP2 was installed in November.

I have not rebooted the server (power cycled) after defining the impersonate as a client after authentications. I will be rebooting in the next few minutes and will update.
llib21Author Commented:
I solved this problem by setting the impersonate level on My Computer Icon under Component Services\DCOM Config\Computer--> Default Properties tab. Also, set the DC Security Policy--> Security Settings\User Rights Assignment\Impersonate a Client after authentication--> must be defined and contain Service and Administrators (not administrator) account.  Rebooted server afterwards and error went away.

Please close the question.
PAQed with points refunded (350)

Community Support Moderator

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
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

From novice to tech pro — start learning today.