ESE Log Generation Checkpoint Depth - Red(>60000) - Edge Transport
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Operations Manager includes a performance data collection engine that is used to query performance counter objects on computers that are running Exchange Server 2007. For this Operations Manager rule, data is collected using the performance counter specified in the Details table.
To review the value of the performance counter that generated this alert, do one of the following:
If you are using Microsoft Operations Manager 2005, from the Operator Console, select this alert, and then click the Properties tab. Review the description of the alert that includes the variables specific to your environment.
If you are using System Center Operations Manager 2007, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event Source |
MSExchange Database ==> Instances |
Counter Name |
Log Generation Checkpoint Depth |
Instance Name |
<All> |
Sample Interval (in seconds) |
900 |
Server Role |
Ex. Edge Transport |
Critical Error Threshold |
>60000 |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Edge Transport/Transport |
MOM Rule Name |
ESE Log Generation Checkpoint Depth - Red(>60000) - Edge Transport. |
Explanation
The Log Generation Checkpoint Depth performance counter represents the work, in a count of log files, that will need to be redone or undone to the database files if the process crashes.
This alert indicates that the ESE Log Generation Checkpoint Depth is larger than 60,000.
When this alert is logged, messages are being received faster than they can be written to the transport queue database. Other symptoms that may occur when this threshold is reached are reduced intra-site, inter-site, and external mail flow. This alert may be caused by one or more of the following conditions:
Message volume is exceeding server capacity.
Applications other than Microsoft Exchange Server are accessing or placing file locks on the transaction log files.
Hard disks are not performing at a level to meet the disk I/O requirements of your Exchange environment.
User Action
To resolve this alert, do one or more of the following:
Run the Microsoft Exchange Mail Flow Troubleshooter. To access the Mail Flow Troubleshooter, click Toolbox in the Exchange Management Console.
If you believe that an application is accessing or placing locks on the transaction log files, stop running the suspected application to determine if that is the cause of the problem. In addition, consider configuring the application so that it does not access the Microsoft Exchange folder and all subfolders.
Important The Microsoft Exchange Transport service will not start if another application locks mail.que, which is the queue database file. After the Microsoft Exchange Transport service starts, no other application can access or lock mail.que, but the log files can be accessed and locked by other applications.
Evaluate disk I/O performance. For information about how to monitor disk performance with Performance Monitor, see Microsoft Knowledge Base article 102020, How to Monitor Disk Performance with Performance Monitor.
If disk performance is the issue and other storage is available, consider moving the transport mail.que file and your transaction log files to a different location. To do this, perform the following procedure:
Note
The following procedure assumes that Exchange Server 2007 is installed to the C:\ drive on your computer.
Stop the Microsoft Exchange Transport service.
Navigate to the C:\Program Files\Microsoft\Exchange Server\bin folder. Save a copy of the EdgeTransport.exe.config file to an alternate location in case you need to revert to it after implementing this procedure.
Edit the EdgeTransport.exe.config file.exe.config file that is located in the C:\Program Files\Microsoft\Exchange Server\bin folder. Specifically, change the QueueDatabasePath value and the QueueDatabaseLoggingPath value to alternate locations.
Save the changes to the C:\Program Files\Microsoft\Exchange Server \bin\ EdgeTransport.exe.config file.
Copy the files from the C:\Program Files\Microsoft\Exchange Server \TransportRoles\data\queue folder to the alternate folder that you specified in step 3.
Restart the Microsoft Exchange Transport service.
Monitor Microsoft Exchange server queues to confirm operability and improved performance.
Verify that the number of log files in the TransportRoles\data\queue folder decreases.
If you are unable to identify and resolve the problem and if the Log Generation Checkpoint Depth performance counter continues to increase, contact Microsoft Technical Support. For information about how to contact support, visit the Contact Us page of the Microsoft Help and Support Web site.
For More Information
To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Microsoft Help and Support Web site.
If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.