DOCUMENT:Q196270
TITLE   :SNMP Agent Leaks Memory When Queried
PRODUCT :Windows NT
PROD/VER:4.0
OPER/SYS:WINDOWS NT
KEYWORD :kbbug4.00 kbfix4.00 

--------------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Windows NT Workstation version 4.0
 - Microsoft Windows NT Server version 4.0
 - Microsoft Windows NT Server, Enterprise Edition version 4.0
--------------------------------------------------------------------------

SYMPTOMS
========

Severe memory leakage occurs when the SNMP agent is under stress.

CAUSE
=====

This problem occurs because, while processing messages, a buffer was used that
was never freed.

RESOLUTION
==========

A supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next Windows NT 4.0
service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support Services
phone numbers and information on support costs, please go to the following
address on the World Wide Web:

   http://support.microsoft.com/support/supportnet/default.asp

The English version of this fix should have the following file attributes or
later:

   Date      Time    Version      Size    File name     Platform
   -------------------------------------------------------------
   11/20/98  06:11p               247,056 advapi32.dll  (x86)
   02/25/99  05:58p                43,792 perfctrs.dll  (x86)
   11/16/98  05:29p                17,680 snmp.exe      (x86)
   11/17/98  03:21p                 8,976 tapiperf.dll  (x86)
   11/20/98  06:11p               188,176 winlogon.exe  (x86)

   11/20/98  06:10p               404,240 advapi32.dll  (Alpha)
   02/25/99  05:57p                60,688 perfctrs.dll  (Alpha)
   11/16/98  05:29p                27,920 snmp.exe      (Alpha)
   11/17/98  03:21p                14,096 tapiperf.dll  (Alpha)
   11/20/98  06:10p               273,680 winlogon.exe  (Alpha)

NOTE: This hotfix was updated on March 19, 1999. The previous version of 
Perfctrs.dll caused SNMP counters to not work.

This hotfix has been posted to the following Internet location as Smsfixi.exe
(x86) and Smsfixa.exe (Alpha):

   ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/
   hotfixes-postSP4/Sms-fix/

NOTE: If this product was already installed on your computer when you purchased
it from the Original Equipment Manufacturer (OEM) and you need this fix, please
call the Pay Per Incident number listed on the above Web site. If you contact
Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it
is determined that you only require the fix you requested. However, this fee is
non-refundable if you request additional technical support, if your no-charge
technical support period has expired, or if you are not eligible for standard
no-charge technical support.

For more information about eligibility for no-charge technical support, see the
following article in the Microsoft Knowledge Base:

   Q154871 Determining If You Are Eligible for No-Charge Technical Support

STATUS
======

Microsoft has confirmed this to be a problem in Windows NT 4.0.

Additional query words: 4.00 systems management server service sp4
============================================================================

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.