Exchange - MAD.exe monitoring error

Hi,
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
Description:
The MAD Monitoring thread was unable to read the CPU usage information, error '0x80041033'.

For more information, click http://www.microsoft.com/contentredirect.asp.

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
Description:
Process INETINFO.EXE (PID=2516). DSAccess needs to close a connection to the Domain Controller sk2exw2k3.bluecanyonpartners.com due to error 0x80040951.

For more information, click http://www.microsoft.com/contentredirect.asp.


llib21Asked:
Who is Participating?
 
GranModCommented:
PAQed with points refunded (350)

GranMod
Community Support Moderator
0
 
oldhammbcCommented:
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??

Cheers

Dave J
0
 
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.
0
 
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.