Update to monitor uncommitted transaction log files (819771)

MORE INFORMATION

Cumulative Rollup Information

For additional information about a hotfix rollup that contains this update, click the following article number to view the article in the Microsoft Knowledge Base: The Log Generation Checkpoint Depth performance counter reports uncommitted transaction log files in the number of log files (generations) instead of the number of bytes. The Log Generation Checkpoint Depth performance counter reports how many Extensible Storage Engine (ESE) transaction log files have content that has not yet been committed to the ESE database. This number represents the number of transaction log files that must be added or committed (rolled forward) to the ESE database if the Information Store process (Store.exe) stops responding (hangs). As the log file generation depth increases, the information store startup time increases.

If the transaction log file depth reaches 1000, ESE dismounts all the databases that are in the affected storage group. The transaction log file depth may grow during periods when the server is very busy. However, very large values typically occur when there is a failure. For example, during a backup operation, the backup program may request that Exchange 2000 not roll forward transaction log files so that a consistent backup may be performed. However, if the backup program stops responding, Exchange 2000 may not be instructed to resume rolling forward the transaction log files. In this case, the number of uncommitted transaction log files increases. To resolve this issue, stop and then restart the Information Store service.

A supported feature that modifies the product's default behavior is now available from Microsoft, but it is only intended to modify the behavior that this article describes. Apply it only to systems that specifically need it. This feature may receive additional testing. Therefore, if your system is not severely affected by the lack of this feature, Microsoft recommends that you wait for the next Exchange 2000 Server service pack that contains this feature.

To obtain this feature immediately, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
Component: Extensible Storage Engine

The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   06-Jun-2003  22:04  6.0.6473.0      2,183,168  Ese.dll          
   06-Jun-2003  22:04  6.0.6473.0         40,960  Eseperf.dll      
   22-May-2003  20:01                      6,991  Eseperf.hxx
   22-May-2003  20:01                    107,477  Eseperf.ini   

Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:After you install the update that is described in this article, you must unload and then reload the ESE performance counters to enable the Log Generation Checkpoint Depth counter. To do so:

1. Start a command prompt, and then locate the folder that contains the Eseprf.ini file and the Eseprf.hxx file.
   
   Typically, these files are in the following folder:

   C:\Program Files\Exchsrvr\Bin

2. Type unlodctr.exe ese, and then press ENTER.
3. Type lodctr.exe eseperf.ini, and then press ENTER.
4. Quit the command prompt, and then restart the Exchange 2000 computer.
5. Verify that the new performance counter is installed:
   1. Click Start, point to Programs, point to Administrative Tools, and then click Performance.
   2. Click the Add (+) button.
   3. In the Select counters from computer list, click your Exchange 2000 computer.
   4. In the Performance object list , click Database ==> Instances.
   5. In the Select counters from list list, make sure that the Log Generation Checkpoint Depth item appears.