Microsoft KB Archive/306860

From BetaArchive Wiki
Knowledge Base


XADM: Incorrect Memory Status When Monitoring Status for Available Virtual Memory

Article ID: 306860

Article Last Modified on 2/21/2007



APPLIES TO

  • Microsoft Exchange 2000 Server Standard Edition



This article was previously published under Q306860


SYMPTOMS

When you monitor the server status for available virtual memory in Exchange System Manager, you may receive incorrect warning and critical error messages. The status page may give the wrong error or warning status and may send notifications if configured to do so, even when the available virtual memory is greater than the warning or critical levels that are set.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.

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 about support costs, visit the following Microsoft Web site:

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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

Component: Administrator

File name Version
Exadmin.dll 6.0.4720.69
Mad.exe 6.0.4720.69
Maildsmx.dll 6.0.4720.69
Cdoexm.dll 6.0.4720.69


NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 1.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

Keywords: kbbug kbexchange2000presp2fix kbfix KB306860