Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Event IDs 9983 and 9016 are logged when you try to use the MOM Operator Console to monitor Exchange 2000 Server health


View products that this article applies to.

Symptoms

When you try to use the Microsoft Operations Manager (MOM) Operator Console to monitor Microsoft Exchange 2000 Server health, the following Error events may be logged in the event log for MOM. This problem occurs after you install hotfix 870923 and Microsoft Operations Manager (MOM) 2005 or the MOM 2000 agent on a computer that is running Microsoft Exchange 2000 Server.

Event 9983

Type: Error
Provider Name: Script-generated Data
Event Number: 9983
Provider Type: Generic Provider
Source: Exchange MOM
Raises Alert: True
Event Id: dd4c2730-778c-4acb-bcfc-819af82da12d

Description: Cannot verify availability of the following test account:
Exchange Server: "Server name"
MDB: "Messaging database name"
Mailbox: "Mailbox name"
due to the following error
Error ID: 0x80040605(-2147219963)
Error text: Failed to initialize CDO smart pointer. Make sure CDO 1.2.1 is installed and registered on this server.
This event was generated by the script: "Exchange 2000 - MAPI logon verification" Domain: VPCDOM

Event 9016

Type: Error
Provider Name: Script-generated Data
Event Number: 9016
Provider Type: Generic Provider
Source: Exchange MOM - MailFlow

Description:
The script aborted its execution due to the following error: 0x80040154(-2147221164) Unexpected error code received from 'EMPMS.MailFlowSender', description: Failed to initialize CDO smart pointer. Make sure CDO 1.2.1 is installed and registered on this server. This event was generated by the script: "Exchange 2000 - Mail flow sender" Domain: VPCDOM

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

Because of file dependencies, this hotfix requires Exchange 2000 Server Service Pack 3 (SP3). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
301378� How to obtain the latest Exchange 2000 Server service pack

Restart requirement

You have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date         Time   Version           Size     File name
--------------------------------------------------------------
17-Jun-2005  01:54  6.0.6617.74       720,896  Cdo.dll          
16-Jun-2005  10:52  6.0.6617.74       749,568  Mapi32.dll


You may also experience these symptoms if the Exchange server has its default permissions locked down for added security. In this situation, you may find that the MOM Mailbox access account may have insufficient permissions on the Exchange server. To verify this, you can use the Filemon tool to monitor file access with a filter set for "empm*". To obtain the Filemon tool, visit the following Sysinternals Web site:If permissions are an issue, the Filemon tool may show many "Access Denied" errors for attempts to write *.mmp temporary files and when you try to access core CDO and MAPI files in the following directories:
  • \exchsrvr\bin
  • \winnt
  • \winnt\system32
Alternatively, as a quick test, you can add the MOM Mailbox access account to a group that has rights to log on locally and access the relevant files and folders.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

↑ Back to the top


Keywords: KB900098, kbqfe, kbhotfixserver, kbpubtypekc, kbbug, kbexchange2000presp4fix, kbfix, kbexchmonitoring, kbautohotfix

↑ Back to the top

Article Info
Article ID : 900098
Revision : 8
Created on : 2/14/2007
Published on : 2/14/2007
Exists online : False
Views : 246