Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WMI Access denied, MAD monitoring thread error

Status
Not open for further replies.

Mick44

IS-IT--Management
Apr 20, 2004
2
AU
I have been researching this problem for months without any success.
The initial indication was in the Event log for Microsoft Exchange 2003.
Every five minutes the followwing error was being generated.
"The MAD monitoring thread was unable to read the state of the services. Error 0x80041003"
I researched this error with Microsoft KB and google and did find a couple of referfences that also alluded to the WMI.
I noticed under Computer Management, Services and Applications, WMI Control under properties that there were two errors:
Win32_Processor WMI: access denied
Win32_OperatingSystem WMI: access denied

This error occurred on the Win 2003 server running Exchange BUT it was ALSO on another Win 2003 server. What they have in common is that they are BOTH Domain Controllers. We have three other Win 2003 Servers which are not domain controllers and they don't have any errors in the WMI control properties.
Seems then to be a permissions problem related to Domain Controllers

Anyone got any ideas on thsi one? Help would be appreciated.

Michael Bright
Oxley College
Bowral NSW Australia
 
What troubleshooting you have done so far? Try registering some dlls again.

Try (using e.g. Start/Run, or a command prompt):

regsvr32 %windir%\system32\atl.dll
regsvr32 %windir%\system32\netshell.dll
regsvr32 %windir%\system32\hnetcfg.dll
regsvr32 %windir%\system32\netcfgx.dll
regsvr32 %windir%\system32\netman.dll

 
I think my *other answered that. My alterego tends to ramble on a bit, so let's summarize:

1. It's WBEM access denied error.
2. It's happening only on domain controllers
3. DCOM permissions and File & Folder permissions are tighter on Domain controllers
4. It looks a lot like you can't open the COM+ catalog files.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top