Topic Last Modified: 2005-11-18

The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine the value for the msExchESEParamLogFileSize attribute of the InformationStore container. If the Exchange Server Analyzer finds that the value for the msExchESEParamLogFileSize attribute does not equal 5120, an error is displayed.

This value applies to all storage groups on the server. This particular error arises if the value of this attribute has been changed from its default (5120 KB or 5 MB). This is the only value supported, and should never be changed.

You must correct the value by using a utility such as the Active Directory Service Interfaces (ADSI) Edit snap-in, the LDP (ldp.exe) tool, or any other Lightweight Directory Access Protocol (LDAP) version 3 client.

If you incorrectly modify the attributes of Active Directory objects when you use ADSI Edit, the LDP tool, or another LDAP version 3 client, you may cause serious problems. These problems may require that you reinstall Microsoft Windows Server™ 2003, Exchange Server 2003, or both. Modify Active Directory object attributes at your own risk.

To correct this error

  1. Open an Active Directory editor, such as ADSI Edit, and locate the InformationStore object for this Exchange Server computer in Active Directory.

    The msExchESEParamLogFileSize attribute can be found at:

    CN=Configuration, DC=Domain, CN=Services, CN=Microsoft Exchange, CN= OrganizationName , CN=Administrative Groups, CN= AdministrativeGroupName , CN=Servers, CN= ServerName , CN=InformationStore

  2. Double-click the msExchESEParamLogFileSize attribute and set its value to 5120.

  3. Close the Active Directory editor and restart the Microsoft Exchange Information Store service for the change to take effect.

For more information about using LDP.exe to edit Active Directory attributes, see the Microsoft Knowledge Base article 260745, "XADM: Using the LDP Utility to Modify Active Directory Object Attributes" (

For more information about working with ADSI Edit, see the topic "Adsiedit.msc: ADSI Edit" in the Windows Server Help.