SNA Server 3.0 Snabase Fails Unexpectedly with Access Violation

Last reviewed: April 14, 1997
Article ID: Q166223
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, version 3.0

SYMPTOMS

The SNA Server 3.0 SnaBase service may fail unexpectedly with an access violation. The failure may occur in a random location, and may not cause a Drwtsn32.log entry to be created.

When this failure occurs, current users who are connected through SNA Server can continue to work, but new users are unable to establish a new session until SNA Server is restarted.

CAUSE

The SnaBase service was causing corruption of its local process memory heap, leading to an access violation when the corrupted heap memory is accessed (via RtlAllocateHeap) or deallocated (via RtlDestroyHeap).

RESOLUTION

An update to SNA Server 3.0 is available to correct this problem. To resolve this problem, obtain the hotfix mentioned below.

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):

   S E R V P A C K
 

	
	


Keywords : kbbug3.00 kbfix3.00.sp1 kbnetwork prodsna snabaseservice
Version : 3.0
Platform : WINDOWS
Issue type : kbbug
Resolution 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: April 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.