Windows 95 Client Trap in SnaBase Using IPX on Windows NTLast reviewed: March 19, 1998Article ID: Q173618 |
The information in this article applies to:
SYMPTOMSThe SNA Windows 95 client gets an application exception in SnaBase when all of the following conditions are met:
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>). CAUSEService 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.
WORKAROUNDTo work around this problem:
STATUSMicrosoft 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 |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |