Microsoft KB Archive/326011

= The System Attendant generates Event ID 9098 and 9099 messages every five minutes =

Article ID: 326011

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q326011



SYMPTOMS
After you install Exchange 2000, Setup seems to finish successfully; 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 MAD 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 MAD 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\applications\exchange

&quot;C:\WINNT\System32\WBEM\wbemcons.mof&quot; failed, returning error code 1 (Incorrect function.). ScCreateProcess

(N:\admin\src\libs\exsetup\hiddenw1.cxx:1763)

Error code 0XC103798A (31114): An internal component has failed.

[16:20:06] CInsParser::ScProcessLine

(N:\admin\src\libs\exsetup\hiddenw1.cxx:1226)

Error code 0XC103798A (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

&quot;C:\WINNT\System32\WBEM\wbemcons.mof&quot;;600000)

CInsParser::ScProcessLine (N:\admin\src\libs\exsetup\hiddenw1.cxx:486)

Error code 0XC103798A (31114): An internal component has failed.

[16:20:06] Registry file name: 'c:\documents and

settings\administrator\local settings\temp\setup\i386\exchange\Misc.ins' CRegistryManager::ScProcessFile (N:\admin\src\udog\setupbase\tools\regmgr.cxx:95)

Error code 0XC103798A (31114): An internal component has failed.

[16:20:06] Filename = '%sourcedir%\Misc' CBaseAtom::ScAddRegistryKeys (N:\admin\src\udog\setupbase\basecomp\baseatom.cxx:1208)

Error code 0XC103798A (31114): An internal component has failed.

[16:20:06] CAtomMisc::ScServicePackUpdate (N:\admin\src\udog\exsetdata\components\server\a_misc.cxx:161)

Error code 0XC103798A (31114): An internal component has failed.

[16:20:06] mode = 'Update' (61957) CBaseAtom::ScSetup (N:\admin\src\udog\setupbase\basecomp\baseatom.cxx:782)

Error code 0XC103798A (31114): An internal component has failed.

[16:20:06] ***** RETRYING THE FAILED OPERATION *****

[16:20:08] Completed Update of Microsoft Exchange Messaging and Collaboration 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 C103798A

Register Cdowfevt.dll Manually
 Click Start, and then click Run. In the Open box, type cmd, and then click OK. Make sure that the component that failed is installed. For example, the Wbemcons.mof file and the Wbemcons.dll file should be installed during Windows installation. At the command prompt, type the following text, and then press ENTER:

c:\winnt\system32\wbem\mofcomp.exe -n:root\cimv2\applications\exchange &quot;c:\winnt\system32\wbem\ &quot;

NOTE:  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 then 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 &quot;Symptoms&quot; section, type root\cimv2\applications\exchange.
 * 1) 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).
 * 1) Compare these classes with the classes in your installation of Exchange 2000:
 * 2) * CommandLineEventConsumer
 * 3) * ExchangeClusterResource
 * 4) * ExchangeConnectorState
 * 5) * ExchangeLink
 * 6) * ExchangeQueue
 * 7) * ExchangeServerState
 * 8) * LogFileEventConsumer
 * 9) * NTEventLogEventConsumer
 * 10) * 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 then click Manage.
 * 2) Double-click Services and Applications.
 * 3) Right-click WMI Control, and then click Properties.
 * 4) Click the Security tab, and then compare the security settings with your installation of Exchange 2000:
 * 5) * Administrator - Allow Enable Account
 * 6) * Administrators - inherited Allow All
 * 7) * Authenticated Users - Allow Enable Account
 * 8) * Domain Admins - Allow Enable Account
 * 9) * Enterprise Admins - Allow Enable Account
 * 10) * Everyone - Allow Enable Account, inherited Allow Provider Write
 * 11) * Exchange Domain Servers - Allow Enable Account
 * 12) * Exchange Services - Allow Enable Account
 * 13) *  - Allow Enable Account
 * 14) *  - 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.
 * 1) When you are prompted to overwrite the more recent file, click No.
 * 2) After Setup is complete, reapply the latest Exchange 2000 service pack.

Keywords: kbprb KB326011

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.