Event type: error
Event Source: MSExchangesa
Event type: monitoring
Event ID: 9099
date:
2004-9-9
Event: 14:39:32
User: N / A
Computer: Dell2600
description:
MAD monitoring thread cannot read the status of the service, error "0X
80041033
"
.
XADM: System Attendant Genereates Event ID 9098 and 9099 Messages Every FiveUtes
Suitable
This Article Was previously Published Under Q326011
Symptoms
After You Install Exchange 2000, Setup Seems To Finish Success; However, The System Attendant Logs One or Both of The Following Event ID Messages In The Application Event Log Every Five Minutes:
Event Type: Error
Event Source: MSExchangesa
Event category: Monitoring
Event ID: 9098
Description: The MONITORING THREAD WAS UNABLE TO Read ITS Configuration from the ds, error '0x80041010'
-or-
Event Type: Error
Event Source: MSExchangesa
Event category: Monitoring
Event ID: 9099
Description: The MONITORING THREAD WAS UNABLE TO Read ITS Configuration from the ds, error '0x80041010'
IF you Examine The Exchange Server Setup Progress.log file, The Following Entries Are Logged:
C: /Winnt/system32/wbem/mofcomp.exe -n: root / cimv2 / application / excitations / exchange
"C: /winnt/system32/wbem/wbemcons.mof" failed, returbunning error.). SccreateProcess
(N: /admin/src/libs/exsetup/hiddenw1.cxx: 1763)
Error Code 0xC
103798A
(31114): An Internal Component Has Failed.
[16:20:06] cinsparser :: scprocessLine
(N: /admin/src/libs/exsetup/hiddenw1.cxx: 1226)
Error Code 0xC
103798A
(31114): An Internal Component Has Failed.
[16:20:06] Processing File 'C: / Documents and Settings / Administrator / Local Settings / Temp / Setup / i386 / Exchange / Misc.ins', At Or Near Line 13
(CreateProcess: C: / Winnt / System32 / WBEM; C: /Winnt/System32/wbem/mofcomp.exe -n: root / cimv2 / applications / Exchange "c: /winnt/system32/wbem/wbemcons.mof"; 600000 )
Cinsparser :: scprocessLine (n: /admin/src/libs/exsetup/hiddenw1.cxx: 486)
Error Code 0xC
103798A
(31114): An Internal Component Has Failed.
[16:20:06] Registry File Name: 'C: / Documents and
SETTINGS / TEMP / SETUP / I386 / Exchange / Misc.ins' CREGISTRYMANAGER :: ScprocessFile (n: /admin/src/udog/setupbase/tools/regmgr.cxx: 95)
Error Code 0xC
103798A
(31114): An Internal Component Has Failed.
[16:20:06] filename = '% SOURCEDIR% / Misc' CBasetom :: SCADDREGISTRYKEYS (N: /ADMIN/src/udog/setupbase/basecomp/basetom.cxx: 1208)
Error Code 0xC
103798A
(31114): An Internal Component Has Failed.
[16:20:06] Catommisc :: scservicePackupdate (n: /admin/src/udog/exsetdata/components/server/a_misc.cxx: 161)
Error Code 0xC
103798A
(31114): An Internal Component Has Failed.
[16:20:06] Mode = 'update' (61957) CBasetom :: scsetup (n: /admin/src/udog/setupbase/basecomp/basetom.cxx: 782)
Error Code 0xC
103798A
(31114): An Internal Component Has Failed.
[16:20:06] ***** Retrying the failed Operation *****
[16:20:08] Completed Update of Microsoft Exchange Messaging and Collaboction Services Component
[16:21:31] Completed Update of Microsoft Exchange System Management Tools Component
[16:23:09] setup completed
Cause
This issue may Occur if the workflow event Sink, CDOWFEVT.DLL, IS NOT CORRECTLY Registered.
Resolution
To resolve this issue, Complete The Procedures in The Following SectionS in The Order That They Are Presented.
Update the version of cdowFevt.dll
Make sure that the version of Cdowfevt.dll is 6.0.4418.43 or later For additional information about how to replace Cdowfevt.dll, click the article number below to view the article in the Microsoft Knowledge Base:. 296095 XADM: System Attendant Reports Event 9098 Error 80041010 Or Setup Does Not Work with error C
103798A
Register cdowfevt.dll manually
1. Click Start, And The Click Run.
2. In The Open Box, Type Cmd, And The Click OK.
3. At the command prompt, Type The Following Text, And the Press Enter: C: /Winnt/System32/wbem/mofcomp.exe -n: root / cimv2 / application / exchange "C: / Winnt / System32 / WBEM / Component_name "NOTE: Component_name is the failed component (for example, Wbemcons.mof) that was reported by the Exchange Server Setup Progress.log file This file is located at the root of drive C.This command forces the registration of the component..
Although the registration of Cdowfevt.dll succeeds, Setup may report error code 1 (Incorrect Function) when it processes the registration of the Windows Management Instrumentation (WMI) components. If you receive this error, continue to the next section.
Verify The Directory Structure and Component Registration
Use Wbemtest.exe to DETERMINE IF THE COMPONENTS Are Registered and if The Directory Structure In WMI WAS Built. To do so, follow these steps:
1. AT A Command Prompt on The Exchange 2000 Server, Type Wbemtest, and the press Enter.
2. Click Connect.
3. In the Server / Namespace box, type the namespace in which the registration failed. For example, based on the Exchange Server Setup Progress.log file entry that is listed in the "Symptoms" section, type root / cimv2 / applications / exchange .
4. Click Login, click Enum Classes, click Recursive, and then click OK.The classes that do not have an underscore (_) before them have been created in this directory (that is, they are not inherited) .5. Compare these Classes with the classes in Your Installation Of Exchange 2000:
· CommandLineEventconsumer
· ExchangeClusterResource
· ExchangeConnectorstate
· Exchangelink
· ExchangeQueue
· ExchangeServerstate
· Logfileeventconsumer
· NTEVENTLOGEVENTCONSUMER
SMTPEVENTCONSUMER
Check the security settings on the Virtual DIRECTORY
IF Registration of the WMI Component Still Fails, Check The Security Settings on The Virtual Directory. To do so, follow these steps:
1. Right-Click My Computer, And the Click Manage.
2. Double-Click Services and Applications.
3. Right-Click WMI Control, And The Click Properties.
4. Click The Security Tab, And The Compare The Security Settings with your installation of Exchange 2000:
Administrator - Allow Enable Account
Administrators - Inherited Allow All
· Authenticated Users - Allow Enable Account
Domain admins - Allow Enable Account
·
Enterprise
Admins - Allow Enable Account
· Everyone - Allow Enable Account, Inherited Allow Provider Write
· Exchange Domain Servers - Allow Enable Account
· Exchange Services - Allow Enable Account
· Service Account - Allow Enable Account
· Exchange Server Name - Allow Enable Account
Complete the process
1. After you have the correct version of the Cdowfevt.dll file and the registration of the WMI components is successful, run Exchange 2000 Setup.You receive a message that states that the destination file exists and is more recent than the source.2. When you are prompted to overwrite the more serious file, click no.
3. After setup is Complete, Reapply The Latest Exchange 2000 Service Pack.
Source Document
XADM: Event ID 9100, 9101, 9102, And 9104 Messages Are Logged in The Application Event LOG
Suitable
Symptoms
Although Exchange 2000 Appears to Be Functioning Correctly, One or More of the Following Event ID Messages Is Logged in The Application Event Log:
Event Type: Error
Event Source: MSExchangesa
Event category: Monitoring Event
ID: 9100
Description: The MAD Monitoring Thread WAS Unable to read the queue information, error '0xc00402be'.
-or-
Event Type: Error
Event Source: MSExchangesa
Event category: (2)
Event ID: 9100
Description: The MAD Monitoring Thread Was Unable To Read The Queue Information, Error '' 0x
800706A
6 ''.
-or-
Event Type: Error
Event Source: MSExchangesa
Event category: Monitoring
Event ID: 9100
Description: The MAD Monitoring Thread Was Unable to read the queue information, error '' 0x80041001 ''.
-or-
Event Type: Error
Event Source: MSExchangesa
Event category: (2)
Event ID: 9101
Description: The Mad Monitoring Thread Was Unable To Read Disk Information, Error '0x80010108'.
-or-
Event ID: 9102
Source: msexchangesa
TYPE: Error
Category: Monitoring
Description: The MAD Monitoring Thread Was Unable To Read The State of Cluster Resources, Error '0x80010108' .- OR-
Event ID: 9104
Event Type: Error
Event Source: MSExchangesa
Event Category: (2) Description: The Mad Monitoring Thread Was Unable To Read The CPU Usage Information, Error '0x80010108'.
Cause
This issue occurs because the monitoring thread that is run by the System Attendant service (Mad.exe) can not query Microsoft Windows Management Instrumentation (WMI) for the state of any of the following items:
§ Cluster Resources
§ CPU Usage Inform
§ Instances of the Exchangelink Class or Other Classes Provided by The Exchange WMI Provider (exwmi.dll)
The Errors May Be Caused by One of the Following Issues:
§ Corruption in the WMI Infrastructure
§ Transient Problems with the WMI INFRASTRUCTURE
§ Network connection Issues
To identify the exact cause of the event, see the error code in the "Description" section of the event. For example, event ID 9102 with the error 0x80010108 translates to RPC_E_DISCONNECTED. This error means that the remote procedure call (RPC) connection was Lost, Possibly Because of Network Connectivity Issues. For more information, see "error cots" section article.
Resolution
.. If these events occur occasionally, they can be safely ignored However, if they occur frequently (for example, every five minutes), you should investigate the cause of the event To do so, follow these steps:
1. Make Sure That WMI Is Installed Correctly. For Additional Information About WMI, See Windows 2000 Online Help.
2. Use the Windows Management Instrumentation Tester (Wbemtest.exe) to make sure that WMI is responding, the Exchange 2000 namespace still exists, the appropriate class exists, and the Exchange WMI provider can enumerate instances of that class. Wbemtest.exe is installed In the% windir% / system32 / wbem folder in your Windows system folder. for more information about how to use us Wbemtest, See Windows 2000 Online Help.3. Check Network Connectivity.
More information
For Additional Information About Interprening WMI Error Codes, Click The Following Article Numbers To View The Articles in The Microsoft Knowledge Base:
295821 xgen: Windows Management Instrumentation Error Return Codes
278952 WMI SINK Interface Methods May Return Invalid Error Codes
Related Events
Event ID: 9098
Event Source: MSExchangesa
Event Type: Error
Event category: Monitoring
Description: The MONITORING THREAD WAS UNABLE TO Read ITS Configuration from the ds, error '0x80041010'
Event ID: 9099
Event Source: MSExchangesa
TYPE: Error
Event category: Monitoring
Description: The Mad Monitoring Thread Was Unable to read The State of the Services, error '0x80010108'.
Error Codes
§ 0x80041010 = WBEM_E_INVALID_CLASS
§ 0x80010108 = rpc_e_disconnected
§ 0x
800706A
6 = RPC_S_INVALID_BINDING
§ 0x80041001 = WBEM_E_FAILED
Source document
