Microsoft KB Archive/896001

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

Article ID: 896001

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-





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.



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) : 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.

Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

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

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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 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



STATUS
Microsoft has confirmed that this is a problem in Exchange 2000 Server.

Additional query words: XADM

Keywords: kbqfe kbhotfixserver kbexchstore kbfix kbexchange2000presp4fix kbbug kbpubtypekc KB896001

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.