Topic Last Modified: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine if the following conditions are true:
- The computer is running Exchange Server 2003.
- The value of msExchESEParamLogBuffers is between 0 and
8,960.
The Exchange Server Analyzer queries the Win32_PerfRawData_MSExchangeIS_MSExchangeIS Microsoft Windows® Management Instrumentation (WMI) class to determine if the following condition is true:
- The value for VMLargestBlockSize is greater than
150,000,000.
The Exchange Server Analyzer determines if either of the following services are running:
- GeoSpanService
- SRDFService
If all of the conditions above are true, an error is displayed.
The Extensible Storage Engine (ESE) uses log buffers to hold transactions in memory before committing them to the transaction logs. If there are not sufficient log buffers you may encounter excessive disk I/Os on the transaction log drive which will decrease performance.
 Caution: |
|---|
| If you incorrectly modify the attributes of Active Directory objects when you use ADSI Edit, the LDP (ldp.exe) tool, or another Lightweight Directory Access Protocol (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. |
-
In Active Directory Service Interfaces (ADSI) Edit, double-click the Configuration container, expand CN=Services, expand CN=Microsoft Exchange, and then expand CN=ExchangeOrganizationName.
-
Expand CN=Administrative Groups, expand CN=AdministrativeGroupName, and then expand CN=Servers.
-
Expand CN=ExchangeServerName, expand CN=InformationStore, right-click CN=Storage Group Name, and then click Properties.
-
In the Select a property to view box, click msExchESEParamLogBuffers.
-
In the Edit Attribute box, type 9000 for msExchESEParamLogBuffers, and then click Set.
-
Click Apply, and then click OK.
-
For the change to go into effect, you must restart the Microsoft Exchange Information Store service.
For more information, see Microsoft Knowledge Base article 328466, "ESE log buffers that are set too low can cause the Microsoft Exchange Information Store service to stop responding" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=328466).