Windows 95 Client Trap in SnaBase Using IPX on Windows NT

 Last reviewed: March 19, 1998
Article ID: Q173618

The information in this article applies to:

  • Microsoft SNA Server, version 3.0 Service Pack 1 (SP1)

SYMPTOMS

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: 

   Application exception occurred:
      App: exe\snabase.DBG (pid=<process id #>)
      When: <date> @ <time>
      Exception number: c0000005 (access violation)
In addition, the Windows NT Application Event Log will contain an event similar to the following when this problem occurs: 

   Event ID: 4097
   Source: DrWatson
   Description: The application, exe\snabase.DBG, generated an application
   exception error.
   The error occurred on <date> @ <time>. The exception generated was
   c0000005 at
   address 00000000 (<no symbols>).

CAUSE

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.

WORKAROUND

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.

STATUS

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          : snaipx snawin95 kbfix3.00.sp2 kbnetwork
Version           : win95:3.0
Platform          : Win95
Issue type        : kbbug
Solution 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: March 19, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.