SNA Server Leaks Memory If Detailed Logging Is EnabledLast reviewed: February 3, 1998Article ID: Q175273 |
The information in this article applies to:
SYMPTOMSIf the Microsoft SNA Server Default Audit Log Level is set for Detailed Problem Analysis, a memory leak occurs every time a new client connects to SNA Server.
CAUSEThe SNA Server Snadmod.dll file determines the client's logon username and domain name each time a client connects to SNA Server. If the user has already connected, then this information is retrieved from a local cache. If the user has not connected, the Snadmod.dll file calls the Win32 LookupAccountSid() function to retrieve this information. The problem occurs because Snadmod.dll continues to use LookupAccountSid even though the user exists in the local cache. In this case, memory that was allocated for the LookupAccountSid function is not released.
STATUSMicrosoft has confirmed this to be a problem in SNA Server version 3.0. A supported fix is now available for SNA Server 3.0 Service Pack 2, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information. Keywords : kbbug3.00 kbbug3.00.sp1 snaserverservice kbfix3.00.sp2 Version : WINDOWS:3.0 Platform : WINDOWS Issue type : kbbug Solution Type : kbfix kbservicepack |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |