Q171413: Changing and Saving Config File Results in Memory Leak

Article: Q171413
Product(s): Microsoft SNA Server
Version(s): WINDOWS:3.0 SP1
Operating System(s): 
Keyword(s): kbenv kbnetwork
Last Modified: 13-JUN-2001

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

- Microsoft SNA Server, version 3.0 SP1 
-------------------------------------------------------------------------------


SYMPTOMS
========

When you make a change to the Config file, SnaBase and other services reload the
Config file. Sometimes the old memory is not released. SnaBase leaks memory
after saving the Config file.

CAUSE
=====

The memory allocated to groups is not being freed.

STATUS
======

Microsoft has confirmed this to be a problem in SNA Server version 3.0 Service
Pack 1 (SP1). 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


Additional query words:

======================================================================
Keywords          : kbenv kbnetwork 
Technology        : kbAudDeveloper kbSNAServSearch kbSNAServ300SP1
Version           : WINDOWS:3.0 SP1
Issue type        : kbbug
Solution Type     : kbfix

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