SNA 3.0 Win 3.x Client Fails to Initialize Due to Security.dll (165700)
The information in this article applies to:
- Microsoft SNA Server 3.0, when used with:
- the operating system: Microsoft Windows NT
This article was previously published under Q165700 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):
| Modification Type: | Major | Last Reviewed: | 10/22/2003 |
|---|
| Keywords: | kbbug kbfix kbnetwork KB165700 |
|---|
|