Microsoft KB Archive/166165

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 16:32, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


XFOR: Wrong Presentation Context ID can Cause ISOCOR MTA to Drop Messages Sent from Exchange Server

Article ID: 166165

Article Last Modified on 10/28/2006



APPLIES TO

  • Microsoft Exchange Server 4.0 Standard Edition
  • Microsoft Exchange Server 5.0 Standard Edition



This article was previously published under Q166165


SYMPTOMS

Messages sent by Microsoft Exchange Server version 4.0 or version 5.0 Service Pack 1 (SP1) over an 88 X.400 Connector to an ISOPLEX 1.3 MTA 4.2.4 system may be discarded by the ISOPLEX MTA with the following error message:

ASN1 error in data from EXCHANGE: Error 0 at offset 5.

A non-delivery report (NDR) is not generated.

CAUSE

Depending on the associations, Exchange Server may use an incorrect value for the Presentation Context ID in the APDU encoding.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 4.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K


Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K


Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0 SP1. We are currently researching this issue and will post more information here in the Microsoft Knowledge Base as it becomes available.


Keywords: kbqfe kbhotfixserver kb3rdparty kbbug kbfix KB166165