README.TXT: Patch 46 for SNA Server 2.0

Last reviewed: April 17, 1997
Article ID: Q115384

The information in this article applies to:
  • Microsoft SNA Server for Windows NT, version 2.0

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

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.

******************* Beginning of Readme ***************************

Product: Microsoft SNA Server for Windows NT v2.0 Update: Patch #46 Status: Confirmed

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

- Includes Patch #3, 8, 26, 38 (see NOTE !)

NOTE: If you apply the SNADMOD.DLL from this patch onto a

      Windows NT machine, you must also apply the SNABASE.EXE
      included with Patch #38, or SNABASE will fail to start.

Date: May 24, 1994

Modules updated:

  \CLIENTS\WIN3X\WDMOD.DLL  05/20/94  04:51p   60,928
  \SYSTEM\SNADMOD.DLL       05/08/94  10:31p   494,080
  \CLIENTS\WINNT\SYSTEM\SNADMOD.DLL   (same as above)

Bugs fixed:

2212 Fix to allow APPC apps to support more than one TP name

If an APPC application issued an Allocate on one TP name, then later issued a Receive_allocate using a different TP name, this subsequent Receive_allocate would hang, even if a matching Allocate was received by SNA Server.

1918 Trap when internal tracing is active, and DLOAD error occurs (Patch 26)

When SNA Server internal tracing is activated on "SNA Applications" on a Windows NT machine, and a APPC dynamic load (DLOAD) request fails, an application exception occurs.

1945 Mishandling of parameters passed to an Invokable TP (Patch 26)

Parameters specified for the invokable TP (within the Parameters subkey of the Windows NT service) were not being passed correctly to the invokable TP when automatically started by SNA Server.

1737 RECEIVE_ALLOCATE on APPC service TP name never attaches (Patch #3)

1755 Server spins in tight loop if it can't access config file (Patch #8)

Update Procedure:

- On the server and Windows NT client machines, stop the SnaBase service,

  apply Patch #38 (specifically, \system\snabase.exe and
\system\snanw.dll),

  then copy the following module:

    copy \SYSTEM\SNADMOD.DLL to the server's <snaroot>\SYSTEM directory

- On a Windows 3.x client machine, stop the SNA Server client software
  and apply the following updated module:

    copy \CLIENTS\WIN3X\WDMOD.DLL to the <winroot>\SYSTEM directory

- Restart the server and client software

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

SNA Server 2.0 patches are located on:

  • Library #2 of the MSSNA Compuserve forum.
  • The Internet server under BUSSYS\SNASRVR\SUP-ED\FIXES\ (supported patches) OR on BUSSYS\SNASRVR\UNSUP-ED\FIXES\ (unsupported patches).


Additional query words: prodsna
Keywords : kbnetwork ntdistrib
Version : 2.0
Platform : WINDOWS


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