Multiple MTA event IDs 2175, 2124, and 2143 are logged by Exchange 2000 Server

After you receive a non-delivery report (NDR) message from an external e-mail server, your Microsoft Exchange 2000 Server computer may log the following three MTA event messages repeatedly until the NDR message expires. The NDR message typically expires in 24 hours.

Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Internal Processing
Event ID: 2175
Date: Date
Time: Time
User: N/A
Computer: Computer_name
Description:
An MTA database server error was encountered while an attribute length. Called from MTA. Procedure: 0. Database error code: ODXOBJEC - I/O Error on object file. Object at fault: 0600005E. Attribute identifier: 29. Value number: ,. Referenced object: 00000000 (00000000 => N/A). Referenced object error 0. [DB Server XFER-IN 15 72] (14)

Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Operating System
Event ID: 2124
Date: Date
Time: Time
User: N/A
Computer: Computer_name
Description:
An MTA database server error was encountered. The object data file caused an I/O error. Object ID: 0600005E. Operating system error: 131. File operation: READ. File offset: 0X81065000. Filename: . Referenced object: 00000000 (00000000 => N/A). Referenced object error 0. [DB Server XFER-IN 15 98] (14)

Event Type: Error
Event Source: MSExchangeMTA
Event Category: Internal Processing
Event ID: 2143
Date: Date
Time: Time
User: N/A
Computer: Computer_name
Description:
A fatal MTA database server error was encountered. Call Microsoft Technical Support. Unrecoverable error: ODXOBJEC - I/O Error on object file. About to terminate. Called from MTA. Procedure 0. Object ID: 0600005E. Attribute ID: 29. Attribute value number: -. Referenced object: 00000000 (00000000 => N/A). Referenced object error 0. [- DB Server XFER-IN 15 101] (16)

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 Exchange 2000 Server 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 telephone numbers and information about support costs, visit the following Microsoft Web site: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

Because of file dependencies, this update requires Exchange 2000 Server Service Pack 3 (SP3). For additional information about how to obtain the latest Exchange 2000 Server service pack, click the following article number to view the article in the Microsoft Knowledge Base:

File information

The English 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
   --------------------------------------------------------------
   28-Oct-2003  03:08  6.0.6527.0      1,798,144  Emsmta.exe       
   28-Oct-2003  02:58  6.0.6527.0         40,960  X400omv1.dll     
				

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

For additional information about the terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base: