Snacfg.exe /Addpartner Option Fails in SNA 3.0 SP1

Last reviewed: March 19, 1998
Article ID: Q170588

The information in this article applies to:

  • Microsoft SNA Server, version 3.0 Service Pack 1 (SP1)

SYMPTOMS

When you add a dependent LU 6.2 session to SNA Server using the Snacfg.exe command line utility using the /Addpartner option, the process appears to complete successfully. However, the following message appears when opening SNA Server Manager after adding the LU:

   Deleting Unpartnered Dependent Lus.

The LU that was added using SNACFG does not appear in SNA Server Manager.

CAUSE

The /Addpartner option in the SNA Server 3.0 Service Pack 1 (SP1) version of Snacfg.exe fails to correctly partner the LU specified when writing to the Com.cfg. Errors in reading partnership records in the Com.cfg lead to problems when subsequent fields are read.

STATUS

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

   S E R V P A C K
Keywords          : snaappc snasetup kbfix3.00.sp2 kbnetwork
Version           : 3.0
Platform          : winnt
Issue type        : kbbug
Solution 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: March 19, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.