Microsoft KB Archive/186258

From BetaArchive Wiki
Knowledge Base


XFOR: NDR on Message from Outlook via Microsoft Mail Connector

Article ID: 186258

Article Last Modified on 10/28/2006



APPLIES TO

  • Microsoft Exchange Server 5.5 Standard Edition



This article was previously published under Q186258


SYMPTOMS

An Outlook 8.0x or Outlook 8.5 client running on Windows NT 4.0 Workstation with language settings set to an East European language gets a non-delivery report (NDR) when sending to Exchange. The Outlook client is connected to a Microsoft Mail postoffice, and the postoffice is connected to Exchange using the Microsoft Mail Connector, as follows:

   Outlook -> Postoffice -> Microsoft Mail Connector -> Exchange Server
   5.5
                


The following messages are written to the Windows NT Application Event log:

   Event ID: 2025

   Source: MSExchangeIS Private
   Type: Information
   Category: Transport Delivery
   The delivery of a message failed due to error 80004005.
   A non-delivery report is being sent to the message's originator.


   Event ID: 1026

   Source: MSExchangeIS Private
   Type: Warning
   Category: Transport General
   An error occurred with the following call stack:
   EcCreateMessage():      0080004005
   EcUnpackMDBEF():        0080004005
   EcMessageFromMDBEF():   0080004005
   EcRecipFromMDBEF():     0080004005


   Event ID: 290

   Source: MSExchangeMTA
   Type: Warning
   Category: X.400 Service
   A non-delivery report (reason code transfer-failure and diagnostic code
   Omit any diagnostic code)
   is being generated for message C=US;A=XYZ;P=TEST;L=ID-00000075.
   It was originally destined for
   DN:/o=Org/ou=Site/cn=Recipients/cn=Exchange123 (recipient number 1),
   and was to be redirected to . [MTA DISP:RESULT 14 136] (12)
                

RESOLUTION

To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For more information, please see the following article in the Microsoft Knowledge Base:

191014 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack


STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 2.


Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe KB186258