X400: X400ADM.EXE Crashes to MS-DOS, Database Is Corrupted

 Last reviewed: October 20, 1997
Article ID: Q115362
3.20 MS-DOS kbusage kbbug3.20

The information in this article applies to:

  • Microsoft Mail Gateway to X.400, version 3.2

SYMPTOMS

If you start X400ADM.EXE, select the Local MTA button, enter a name and put a period and a comma at the end of the name, then enter the Country Code and Admd Name and select OK, the program crashes to MS-DOS with the message: 

   Path not found in line 0 of module LOCALMTA at address 9B84:06DA
If you restart X400ADM.EXE and select the Local MTA button, you see that the database is corrupted: 

  -the Country Code entry is in the Admd Name field
  • the Admd Name entry is moved to the Prmd Name field
  • the MTA's (name) entry is gone from the OUTGOING subdirectory

    CAUSE

    The comma is not a valid Name field character because the program interprets commas as separators--in this case for the Name and Password fields. For example: 

       MTA01,,,us, ATTMAIL,
    When this happens the data in the Country Code and Admd Name fields is displayed in the next field down (Country Code to Admd Name; Admd Name to Prmd Name).

    RESOLUTION

    Remove commas from MTA field entries.

    The failure is most spectacular in the MTA name, but a comma causes the same confusion in any MTA information field, since the underlying data file is delimited with commas.

    • Additional reference words: 3.20
    KBCategory: kbusage kbbug3.20
    KBSubcategory: MailGWX400

    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: October 20, 1997
    © 1998 Microsoft Corporation. All rights reserved. Terms of Use.