SNA 3.0 Win 3.x Client Fails to Initialize Due to Security.dll

 Last reviewed: April 14, 1997
Article ID: Q165700
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, version 3.0

SYMPTOMS

When starting an SNA application on the SNA Server 3.0 Windows 3.x client, the computer may stop responding (hang) or an access violation may occur.

CAUSE

When the SNA Server Windows 3.x client application (or Wnap.exe) starts, the SNA client attempts to initialize the Windows NT security support provider interface that is contained in Security.dll. If the client computer has a different Security.dll somewhere else in the path, the wrong Security.dll will cause the SNA client to fail to initialize.

RESOLUTION

An update to the SNA Windows 3.x client is available to correct this problem. With the update applied, the SNA client loads the Security.dll located in the WbinPath setting that is in the [WNAP] section of the Win.ini file, instead of any Security.dll that is located in the path.

STATUS

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

   S E R V P A C K

Keywords : kbbug3.00 kbfix3.00.sp1 kbnetwork prodsna snasecurity snawin3x
Version : 3.0
Platform : WINDOWS
Issue type : kbbug
Resolution 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: April 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.