Knowledge Base

SNA Server 3.0 Snabase Fails Unexpectedly with Access Violation

Article ID: 166223

Article Last Modified on 10/22/2003


APPLIES TO


This article was previously published under Q166223

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: kbbug kbfix kbnetwork KB166223