Monitoring notifications that apply to routing groups do not work and event ID 9098 is logged after you configure notifications in Exchange Server 2003 SP1

View products that this article applies to.

SYMPTOMS

After you configure a monitoring notification that applies to any server in the routing group or to any connector in the routing group, the monitoring task is not initialized. The following error event is logged in the application event log every five minutes:

Source: MSExchangeSA
Category: Monitoring
Type: Error
Event ID: 9098

Description:
The MAD Monitoring thread was unable to read its configuration from the DS, error '0x8000ffff'.

Back to the top

CAUSE

This problem occurs because the datxROUTING_GROUP_DN attribute is not added to the array that the directory object (DOB) reads attribute names from. Therefore, the datxROUTING_GROUP_DN attribute value is not read into the DOB.

Back to the top

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

836993 (http://support.microsoft.com/kb/836993/EN-US/ ) How to obtain the latest service packs for Exchange Server 2003

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS (http://support.microsoft.com/default.aspx?scid=fh;%5Bln%5D;cntactms)

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

This hotfix requires Microsoft Exchange Server 2003 Service Pack 1.

Restart requirement

You must restart the Exchange services to install this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The global version of this hotfix has the file attributes (or later) 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
   --------------------------------------------------------------
   18-Jun-2004  03:24  6.5.7232.3      8,902,656  Mad.exe

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. This problem was first corrected in Exchange Server 2003 Service Pack 2.

Back to the top

MORE INFORMATION

The DOB is used to cache the Active Directory directory service object attributes that are read from Active Directory.

For additional information about Microsoft software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base:

824684 (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

817903 (http://support.microsoft.com/kb/817903/ ) New naming schema for Exchange Server software update packages

Back to the top