XADM: Invalid Parameters When Using X.121 Field in X.400 Address

Last reviewed: April 9, 1997
Article ID: Q156722

The Information in this article applies to:

Microsoft Exchange Server, version 4.0

SYMPTOMS

This problem occurs when you send a message from Microsoft Exchange to a fax by means of an X.400 address (form 1 variant 3) such as the following:

   C=FR;A=ATLAS;X.121=93312345678

A non- delivery report (NDR) is returned from the remote X.400 system, with the following:

   diagnostics = 11 : invalid parameters.

Sending to X.121=93312345678 is correctly handled by remote systems.

CAUSE

In the first case, the P2 O/R name is incorrectly coded; it contains only C=FR;A=ATLAS. The X.121 field is missing.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange 4.0 U.S. Service Pack. 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

Keywords : kbbug4.00 kbfix4.00.sp4 kbusage XADM
Version : 4.0
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.