XADM: Memory Leak in Directory Service of Exchange Server

 Last reviewed: February 12, 1998
Article ID: Q177875
The information in this article applies to:
  • Microsoft Exchange Server version 5.0

SYMPTOMS

When an Exchange Server computer has been running for a long time, it may have a small memory leak in the directory service component. This can be observed by using Performance Monitor and checking the private byte counter of the Microsoft Exchange directory service process (Dsamain.exe). The observed symptom is that the counter increases over a time frame of days.

CAUSE

The Exchange directory service allocates memories from heap, which should be freed when the task is finished or during shutdown of the directory service. However, some of the allocated memory is not freed properly.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0.

This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. 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
Additional query word: DS 
Keywords          : kbbug5.00 kbfix5.00.sp2 XADM kbbuglist
Version           : WinNT:5.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix kbpatch

================================================================================

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 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.