Handle Leak in SNAUDB.EXE

Last reviewed: February 10, 1998
Article ID: Q180729
The information in this article applies to:
  • Microsoft SNA Server, versions 3.0, 3.0SP1, 3.0SP2, 4.0

SYMPTOMS

SNA Server Host Account Cache service (that is, SnaDatabase, or Snaudb.exe) handle count grows each time a new logon request occurs. This problem can be observed by monitoring the handle count for the snaudb process using the Windows NT performance monitor. Eventually, the Host Account Cache service will fail, causing host user ID's and passwords to fail to be mapped.

CAUSE

The SNA Server Host Account Cache service (Snaudb.exe) was not closing the event handles it created for every RPC request it received.

STATUS

Microsoft has confirmed this to be a problem in Windows NT SNA Server, versions 3.0, 3.0 Service Pack 1 (SP1), 3.0 SP2, and 4.0.

A supported fix is now available for 3.0 SP2 and 4.0, 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 Product Support Services for more information.

Keywords          : kbbug3.00 kbbug3.00.sp1 prodsna snahostsec kbbug3.00.sp2 kbbug4.00 kbbuglist
Version           : WINDOWS:3.0,3.0SP1,3.0SP2,4.0
Platform          : WINDOWS
Issue type        : kbbug
Solution 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: February 10, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.