README.TXT: Patch 54 for SNA Server 2.0

Last reviewed: April 24, 1996
Article ID: Q119651
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, version 2.0

SUMMARY

The following is the README.TXT file that accompanies SNA Server 2.0 patch 54 (SNA20.P54):

Note that this article reflects the text of a static document. Therefore, some of the information in this article may be outdated. For example, as of May 20, 1996, Microsoft no longer maintains support forums on CompuServe.

MORE INFORMATION

******************* Beginning of Readme *************************** Product: Microsoft SNA Server for Windows NT v2.0 Update: Patch #54 (includes Patch #6, 41) Status: Confirmed

PKZIP 2.04g format -- uncompress using the "-d" option.

Date: August 2, 1994

Modules updated:

 \SYSTEM\SNACFG.DLL     07/29/94  06:26p  227,328 (2.0.0.149)

Bugs fixed:

2530 Saving COM.CFG fails with many APPC LU's.

The SNA Server Admin program may report "handle is invalid" when attempting to save the configuration file, if over 250 APPC LU/LU/mode partnerships are defined. This problem was caused by the server configuration record length exceeding an internal limit of 64K. With this update, this internal limit is removed.

2174 Allow XIDs ending in 00000 (Patch 41)

Admin prohibits both local and remote XIDs from ending in 00000, displaying:

Error: 3907

The last five digits of the Local Node ID are invalid. These digits, also called the Node Number, can be any five hexadecimal digits except 00000, which is reserved.

This patch allows for the last five digits to be "00000"

1579 Fix to interoperate with unreleased APPN Network Nodes (Patch 6)

In certain unreleased versions of APPN Network Node products, these products do not accept XID's which exceed 60 bytes in length. The default XID sent by SNA Server is now below 60 bytes in length.

Update Procedure:

On all Windows NT machines where SNA Server Admin is run:

- stop SNA Server Admin, if it is running.

- copy the attached module to the <SnaRoot>\SYSTEM directory

- re-run SNA Server Admin, open the configuration file, and re-save

  the configuration to apply the change.

- in order for SNA Server to pick up this change, all SNA Servers
  (SnaServer service) affected by this configuration file change
  will need to be stopped and restarted (i.e. all servers which
  appear as "Out of Date" within SNA Server Admin will need to
  be restarted).

*********************** End of Readme *******************************

SNA Server 2.0 patches are located on:

  1. Library #2 of the MSSNA CompuServe forum.

  2. The Internet server under BUSSYS\SNASRVR\SUP-ED\FIXES\ (supported patches) OR on BUSSYS\SNASRVR\UNSUP-ED\FIXES\ (unsupported patches).


Additional reference words: prodsna 2.00
KBCategory: kbnetwork
KBSubcategory: ntdistrib


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