lgallion
asked on
Event ID 9099
Hi Everyone,
My Windows 2003 Standed, and Exchange 2003 Enterprise server gets the Event id 9099 every 5 minutes. The error is in the following: The MAD Monitor was unable to read the state of services. Error:"ox80070005". I seached on line and one article said I need regiser cdowfevt.dll. So I typed regsvr32 -i cdowfevt.dll. It came out a message: cdowfevt.dll was loaded, but the DIIInstall Entry Point was not found". The registration failed.
Does anybody know a way to fix the problem? Thank you very much ahead to help me!
My Windows 2003 Standed, and Exchange 2003 Enterprise server gets the Event id 9099 every 5 minutes. The error is in the following: The MAD Monitor was unable to read the state of services. Error:"ox80070005". I seached on line and one article said I need regiser cdowfevt.dll. So I typed regsvr32 -i cdowfevt.dll. It came out a message: cdowfevt.dll was loaded, but the DIIInstall Entry Point was not found". The registration failed.
Does anybody know a way to fix the problem? Thank you very much ahead to help me!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
vff
sdfsdfwedcxwedcz
You can use the site www.eventid.net to get detail from the event. Here is some comment from the site for the ID
Event ID: 9099
Source MSExchangeSA
Type Error
Description The MAD Monitoring thread was unable to read the state of the services, error '<error number>'
Mihai Andrei (Last update 11/29/2005):
As per Microsoft: "The Monitoring thread will recover from these errors if they are isolated. If you receive more than six of these events every hour, then the underlying cause needs to be investigated". See MSEX2K3DB for additional information about this event.
Ionut Marin (Last update 10/14/2003):
This issue may occur if the workflow event sink, Cdowfevt.dll, is not correctly registered. See M326011 and M810861 for more details.
Event ID: 9099
Source MSExchangeSA
Type Error
Description The MAD Monitoring thread was unable to read the state of the services, error '<error number>'
Mihai Andrei (Last update 11/29/2005):
As per Microsoft: "The Monitoring thread will recover from these errors if they are isolated. If you receive more than six of these events every hour, then the underlying cause needs to be investigated". See MSEX2K3DB for additional information about this event.
Ionut Marin (Last update 10/14/2003):
This issue may occur if the workflow event sink, Cdowfevt.dll, is not correctly registered. See M326011 and M810861 for more details.
To Page Editor - leew
Please remove my above comment as it might not comply with the rules of www.eventid.net site.
Thanks!
Please remove my above comment as it might not comply with the rules of www.eventid.net site.
Thanks!
If he has fixed the problem, I think he should let us know how.
ASKER
The problem still has not been resolved after several attempts by Microsoft's techs, but they are still working on it. That is why I haven't posted any follow up. I am going to accept gvlob's answer as the best attempt to solve the problem. Thanks.
Thank you for the follow up. Please let us know once they come up with a solution for you.