Changing and Saving Config File Results in Memory Leak (171413)



The information in this article applies to:

  • Microsoft SNA Server 3.0 SP1

This article was previously published under Q171413

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


Modification Type:MajorLast Reviewed:6/29/2004
Keywords:kbbug kbenv kbfix kbnetwork KB171413