Microsoft KB Archive/173618
Article ID: 173618
Article Last Modified on 7/15/2004
- Microsoft SNA Server 4.0
This article was previously published under Q173618
The SNA Windows 95 client gets an application exception in SnaBase when all of the following conditions are met:
- The SNA Windows 95 client is installed on a Windows NT system.
- The SNA Windows 95 client is configured to use IPX/SPX as the transport protocol.
- The SNA Windows 95 client is configured with a client mode of Remote and the sponsor servers are listed by server name.
- The SNA Windows 95 client is configured to use bindery emulation to locate the SNA Server computers.
The application exception in Snabase.exe will generate a Drwtsn32.log file in the Windows NT root directory that will be similar to the following:
In addition, the Windows NT Application Event Log will contain an event similar to the following when this problem occurs:
Service Pack 1 for SNA Server 3.0 added a new feature that allows the integration of SNA Server with Novell's NDS (NetWare Directory Service). This problem was introduced as a result of the NDS changes that were made to the SNA Windows 95 client for SP1. Specifically, the InitNDS() function does not clear the SNANDS32 module handle after the GetNdsTreeAndContext() call failed causing the NdsFindSnaServer() function to call a NULL pointer. The application exception in snabase.exe occurs when the NULL pointer is called.
To work around this problem:
- Configure the SNA Windows 95 client with a client mode of Local and use the SNA Subdomain name to locate the SNA Server computers.
Microsoft has confirmed this to be a problem in the SNA Windows 95 client version 3.0 Service Pack 1 (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: kbbug kbfix kbnetwork KB173618