Event id 114 exoledb

Hello

I am experiencing this error. The server is 2003 SBS.Any suggestions on how I resolve this?
Event Type:      Error
Event Source:      EXOLEDB
Event Category:      Events
Event ID:      114
Date:            17/04/2010
Time:            14:01:22
User:            N/A
Computer:      SERVER
Description:
Microsoft Exchange OLEDB has disabled the event binding due to the problems in the event sink. Binding ID = {44294C8C-237E-4FD4-93D9-63D708691D97}. You may need to contact the event sink author and get a fixed or updated copy.

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

Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      Monitoring
Event ID:      9097
Date:            17/04/2010
Time:            14:44:23
User:            N/A
Computer:      SERVER
Description:
The MAD Monitoring thread was unable to connect to WMI, error '0x8004100e'.

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

mail2clkAsked:
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.

Shreedhar EtteCommented:
0
Satya PathakLead Technical ConsultantCommented:
--This event is logged when Microsoft Exchange System Attendant service (Mad.exe) is failing to connect to one of ----the two Windows Management .
--Instrumentation (WMI) namespaces, "root/cimv2" or "root/cimv2/applications/exchange".

--This issue can occur if the Exchange namespace has become unregistered in Windows Management Instrumentation (WMI) on the system.
--Ensure that the Windows Management Instrumentation service is able to start properly and that the WMI
--repository contains the --"root/cimv2/applications/exchange" namespace.
--You can also ensure that MACHINENAME$ has been given access to those namespaces.
--Essentially, you will need to re-register the Exchange namespace in WMI.
--This can be done by running SETUP from the Exchange CD and choosing REINSTALL.
--If prompted to overwrite any files, choose not to overwrite.
0
mail2clkAuthor Commented:
I reinstall Exchange SP2 and this resolved the issue.
0

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
Shreedhar EtteCommented:
That's Good.
0
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
Programming Languages-Other

From novice to tech pro — start learning today.