An event is not logged in the Application log before the last available transaction log in the sequence is used in Exchange 2000 Server

Hotfix Download Available
View and request hotfix downloads

View products that this article applies to.

SYMPTOMS

Consider the following scenario. You expect an event to be logged in the Application log before the last available transaction log is used in Microsoft Exchange 2000 Server. This event would remind you to move the present transaction logs to another location to avoid unexpected server shutdown. However, an event is not logged in the Application log before the last available transaction log in the sequence is used.

Back to the top

RESOLUTION

The hotfix that is specified in this article adds the following functionality in Exchange 2000 Server. When the last available transaction log in the sequence approaches, an event that is similar to the following is logged in the Application log:

Event Type: Warning Event Source: ESE
Event Category: Logging/Recovery
Event ID: 514
Description: Information Store (2748) SG2: Log sequence numbers for this instance have almost been completely consumed. To begin renumbering from generation 1, the instance must be shutdown cleanly and all log files must be deleted. Backups will be invalidated.

Note Although the event is logged in the Application log, you must still maintain the transaction log. For example, you can move the present transaction log to another location so that the transaction log sequence can start over.

Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

Because of file dependencies, this hotfix requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For more information about how to obtain Exchange 2000 Server SP3, click the following article number to view the article in the Microsoft Knowledge Base:

301378 (http://support.microsoft.com/kb/301378/ ) How to obtain the latest Exchange 2000 Server service pack

File information

The English version of this hotfix has the file attributes (or later file attributes) 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
   ---------------------------------------------------------
   30-Mar-2005   16:58   6.0.6617.60   2,191,360   Ese.dll

Back to the top

MORE INFORMATION

To work around this issue, you can use the Microsoft Exchange Troubleshooting Assistant tool because it automates the process of verifying the health of your databases and resetting the transaction log sequence.
To download the Microsoft Exchange Troubleshooting Assistant, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=4BDC1D6B-DE34-4F1C-AEBA-FED1256CAF9A&displaylang=en (http://www.microsoft.com/downloads/details.aspx?familyid=4BDC1D6B-DE34-4F1C-AEBA-FED1256CAF9A&displaylang=en)
Then, follow the instructions in the following Microsoft Web pages to reset the transaction log sequence:
http://technet.microsoft.com/en-us/library/aa998611(EXCHG.80).aspx (http://technet.microsoft.com/en-us/library/aa998611(EXCHG.80).aspx)
http://technet.microsoft.com/en-us/library/bb266925(EXCHG.80).aspx (http://technet.microsoft.com/en-us/library/bb266925(EXCHG.80).aspx)

Back to the top