PC DirSync: Import -X Fails for SNADS Gateway

 Last reviewed: May 24, 1996
Article ID: Q126610
The information in this article applies to:
  • Microsoft Mail for PC Networks, versions 3.0a, 3.2, 3.2a, and 3.5

SYMPTOMS

IMPORT.EXE may fail to extract SNADS addresses from a gateway postoffice if the gateway name was installed with one of the following names: 

   MSMAIL
   FAX
   MCI
   X400
   SMTP
   MHS
IMPORT.EXE recognizes these names as specific types of gateways, and they should not be used for the name of the SNADS gateway.

If one of these names is used, the command line 

   IMPORT Admin -ppassword -dm -gSNADS -ftest.txt -x
will fail to create the expected text in the file TEST.TXT. However, no error message will be received.

RESOLUTION

This problem can be corrected by changing the SNADS gateway name to a unique network name.

MORE INFORMATION

During installation of the SNADS gateway, step 3 prompts for the gateway name and the following message appears: 

   Note: This must be a unique network name.
The SNADS installation program will allow input of the gateway names listed above if these gateways are not currently installed. However, IMPORT.EXE will not properly initialize the DGN's for the SNADS gateway if one of these names is used for as the gateway name.

Additional reference words: 3.00a 3.20 3.20a 3.50 dirsync
KBCategory: kbusage
KBSubcategory: MailPCDirSync

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: May 24, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.