Article ID: 260554
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange Server 5.5 Standard Edition, when used with:
- Microsoft Windows 2000 Standard Edition
- Microsoft Mail for PC Networks 3.5
This article was previously published under Q260554
SYMPTOMS
When you use Microsoft Mail Server (MS Mail) and the Microsoft Mail Connector with Exchange Server 5.5 on a computer running Windows 2000 Server, the Async.exe program in Exchange Server may leak memory if the following conditions exist:
- Multiple post offices exist on the computers running MS Mail.
- A local post office exists on Exchange Server.
- Post offices on MS Mail are connecting to Exchange Server 5.5 by using the Microsoft Mail Connector.
- Post offices on MS Mail are configured as remote post offices for each other as follows:
- The post offices on MS Mail connect to post offices on Exchange Server directly.
- The post offices on MS MAIL connect to post offices on MS Mail indirectly.
- You send e-mails to some recipients on other post offices on MS Mail.
In Windows 2000 Performance Monitor, the Task List utility, and the Process Viewer utility, an increase in memory usage is displayed.
CAUSE
This issue can occur because the method of memory management in Windows 2000 Server is different than the method that Microsoft Windows NT 4.0 uses, and the Microsoft Mail Connector in Exchange Server 5.5 may not release the memory if it is installed on a computer that is running Windows 2000 Server. This causes the memory leak.
RESOLUTION
To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
191014 XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.
Keywords: kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix KB260554
