XCON: Message Transfer Agent Repeatedly Fails to Start with Event 155 or Event 164

This article was previously published under Q273646
This article has been archived. It is offered "as is" and will no longer be updated.
The message transfer agent (MTA) does not start after repeated attempts (usually after first logging an attempt to perform database recovery), and the last MTA error logged in the application event log is Event 155 or Event 164, which reports that an object with an invalid DN could not be read from the directory. The Event 155 may be similar to the following:
Event Type: Error
Event Source: MSExchangeMTA
Event Category: Directory Access
Event ID: 155
Date: 9/7/2000
Time: 2:28:49 AM
User: N/A
Computer: WSILVER-MSG-01
An error occurred while reading information for directory name (DN) from the directory. [MTA XFER-IN 11 38] (12)
This behavior may occur when the MTA is not shut down cleanly and has messages in its queues. Specifically, if the MTA is shut down after a fatal error during object parsing, it is possible that the object in the database is saved partly parsed. Then, when you try to restart the MTA, the MTA uses binary data from one of the message properties as a distinguished name for the Active Directory object lookup.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: MTA

File nameVersion

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.

Article ID: 273646 - Last Review: 10/21/2013 01:27:04 - Revision: 1.3

  • Microsoft Exchange 2000 Server Standard Edition
  • kbnosurvey kbarchive kbbug kbfix kbqfe KB273646