Application Exception When AppleTalk Clients Try Connecting

 Last reviewed: April 17, 1997
Article ID: Q147712
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, versions 2.11 and 2.11 SP1

SYMPTOMS

The SNA Server stops responding (hangs) and Appletalk client computers are unable to attain session connections. In the Event Viewer, the following application events appear: 

   Event ID: 624
   Source: SNADUMP.LOG
   Description: A process SNABASE.EXE ended abnormally due to a protection
   violation, or similar condition.

   Event ID: 4097
   Source: Dr. Watson Log
   This application, SNABASE.DBG generated an applicaiton error. The error
   occurred on <date>. The exception generated was C0000005 at address
   <address>.
A portion of the DRWTSN32.LOG file states the following: 

   App: snabase.DBG (pid=160)
        When: <date> @ <time>
        Exception number: c0000005 (access violation)
NOTE: Your DRWTSN32.LOG file will appear somewhat different than this example.

CAUSE

The SNAAT.DLL send routine is not checking to see if the L-Table is already in a closing state. Therefore, it tries to access its pending queue, which has been released. This causes the application exception in SNABASE.EXE.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 2.11 and 2.11 Service Pack 1. This problem was corrected in the latest Microsoft SNA Server 2.11 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

Additional query words: prodsna
Keywords : kbbug2.11 kbbug2.11.sp1 kbfix2.11.sp2 kbnetwork ntnetserv
Version : 2.0 2.1 2.11 2.11sp1
Platform : WINDOWS

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 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.