ID: Q175271
The information in this article applies to:
After you upgrade to Microsoft SNA Server 3.0 Service Pack 2, one of the following symptoms may occur while the server is running:
- Users who have active sessions may find their computer suddenly hangs or
stops responding (3270 users may receive perpetual XCLOCK), and new user
connection attempts to either the SnaBase or SNA Server service may
fail.
following error messages:
Event: 624
Source: SNA Server (or SnaBase)
Description: Creating dump file C:\SNA\traces\snadump.log for
Snaservr.exe [or snabase.exe]
Application exception occurred:
App: snaservr.DBG (pid=<process ID>)
When: <date and time>
Exception number: c0000005 (access violation)
The fault entry indicated in routine ntdll!RtlAllocateHeap, or
ntdll!RtlDestroyHeap.
In SNA Server 3.0 Service Pack 2, client logon requests are now handled from multiple threads within the SnaBase or SNA Server service. If two concurrent client logon requests occur that both use the LSA authentication method (that is, Windows 3.x clients, or Windows NT services that run under the local system account), the SnaBase or SNA Server memory heap may become corrupted. This occurs because LSA logon is not thread-safe, so two concurrent LSA logon requests from the same process can result in memory corruption.
Microsoft has confirmed this to be a problem in SNA Server version 3.0 Service Pack 2.
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 : prodsna kbbug3.00.sp2 kbfix3.00.sp3 snabaseservice snaserverservice
Version : WINDOWS:3.0SP2
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfixLast Reviewed: April 22, 1998