Changing and Saving Config File Results in Memory Leak

ID: Q171413

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 sna3rdparty snaconfig snamanager snasetup kbfix3.00.sp2
Version : WINDOWS:3.0 SP1
Platform : WINDOWS
Issue type : kbbug