Microsoft KB Archive/822894

= Jet Database Does Not Work Correctly During a Backup or During a Content Indexing Operation =

Article ID: 822894

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition

-





SYMPTOMS
You may find that the JET database memory management feature does not work correctly during a backup or during a content indexing operation on a Windows Server 2003-based computer.



CAUSE
This problem occurs because of the way that the JET database cache size increases or decreases depending on the Transition Fault/sec counter from the operating system. For example, backup is currently performed by using the cache, and this affects the Transition Fault/sec counter. This may cause inconsistencies in how the JET database memory management feature optimizes its memory usage and in how it tries to free up more memory for the operating system.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



RESOLUTION
Microsoft Exchange Server 2003 dynamically determines the default value for the msExchESEParamCacheSizeMin property, based on the amount of physical random access memory (RAM) that is installed in the server. Use the following method only if you intend to change the values to fit the requirements of your server. Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk. To resolve this problem, follow these steps:  Start ADSI Edit from Windows Server 2003 Support Tools. Double-click the Configuration container. Expand CN=Services. Expand CN=Microsoft Exchange. Expand CN= . Expand CN=Administrative Groups.</li> Expand CN= .</li> Expand CN=Servers.</li> Expand  .</li> Right-click CN=InformationStore, and then click Properties.</li> In the Select a property to view box, click msExchESEParamCacheSizeMin.</li> In the Edit Attribute box, type the value that you want to set. You can use the default formula and edit it to fit your situation. Use the following table as a guideline:

Note The value that you use must be a multiple of 32 MB.</li> Click Apply, and then click OK.</li></ol>

You can use the following information to restore the msExchESEParamCacheSizeMin property to its original value:
 * If Exchange 2003 is running on Microsoft Windows Server 2003 and the server has 2 GB or more of RAM, the msExchESEParamCacheSizeMin will be 131072 (512 MB).
 * If Exchange 2003 is running on Windows Server 2003 and the server has 768 MB or more but less than 2 GB of RAM, the msExchESEParamCacheSizeMin will equal &quot;server memory/4*(4*1024)&quot;.
 * If Exchange 2003 is running on Windows Server 2003 and the server has less than 768 MB of RAM, the msExchESEParamCacheSizeMin will equal &quot;server memory/8*(4*1024)&quot;.

Examples

 * Windows Server 2003 with 512 MB of RAM will have a default value for msExchESEParamCacheSizeMin of 16384 (4 KB pages).
 * Windows Server 2003 with 1GB of RAM will have a default value for msExchESEParamCacheSizeMin of 65536 (4 KB pages).
 * Windows Server 2003 with 4 GB of RAM will have a default value for msExchESEParamCacheSizeMin of 131072 (4 KB pages).

If Exchange 2003 is running on Microsoft Windows 2000 Server, then no default value is set for msExchESEParamCacheSizeMin.

Keywords: KB822894

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.