Troubleshoot Event ID 623

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

This topic describes the steps to troubleshoot Event ID 623.

Before You Begin

To perform this procedure, the account you use must be delegated the following:

• Administrator permission for the computer that is running Microsoft Exchange Server 2007

For more information about permissions, about delegating roles, and about the rights that are required to administer Exchange 2007, see Permission Considerations.

Procedure

To troubleshoot Event ID 623, follow these steps:

1. Use exCoNameNoMk Operations Manager to monitor for “623” events. For more information, see How to Create a Monitor

2. Use the Microsoft Exchange Best Practices Analyzer Tool to resolve any outstanding critical issues. For example, verify that antivirus software is installed and running correctly. For more information, see Tune Up Exchange Server with the Best Practices Analyzer.

3. Verify the integrity of the Information Store level and JET. To do this, follow these steps:

   1. To verify the integrity of the Information Store level, run the following command at a command prompt: ISINTEG -S*<Server_Name>*-FIX -TEST ALLTESTS. For more information, see Isinteg.

   2. To verify Jet integrity, run the following command at a command prompt: eseutil /g. For more information, see Eseutil.

4. Try to track a large message as it is going through the store. For more information about how to do this, see the following Microsoft blog and Microsoft Knowledge Base articles:

   • Messages that are larger than global size limits can affect server performance

   • Large Messages Affect Server Performance

   • E-mail client users experience a decrease in performance, and event 623 is logged when you receive a large message in Exchange Server 2003

   • You may experience slow client performance if the version store runs out of memory in Exchange Server 2003

   • Client latencies occur when Exchange 2000 Converts Mail from MAPI to MIME format

5. Verify that online maintenance is being finished. Also verify that the online maintenance schedule does not conflict with online backup times. Widen the online maintenance window during off-peak hours if the online maintenance is not finishing.

6. Disk I\O performance issues can cause a slow read transaction and can cause Event ID 623 to occur. Use the Microsoft Exchange Performance Troubleshooting Analyser Tool to analyse and fix any Exchange Server performance issues. For more information, see Microsoft Knowledge Base article 923893, Description of the Exchange Server Performance Troubleshooting Analyzer tool.

   Note

   You have to restart Performance Monitor after you make the registry setting to see the additional counters.

For More Information