process name (process id) nameDatabase number requires logfiles number-value in order to recover successfully. Recovery could only locate logfiles starting at %7.

Details
Product: Exchange
Event ID: 452
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) nameDatabase number requires logfiles number-value in order to recover successfully. Recovery could only locate logfiles starting at %7.
   
Explanation

One or more log files is missing. The recovery process of

the database requires log files to continue.

 

You will receive the following phrase in the event

Description:

Information Store (number) [guid] Database [path\filename]

requires logfiles [e.g.] 26709-26712 in order to recover

successfully. Recovery could only locate logfiles starting at  [e.g.] 26713.

 

Causes of missing logfiles are many and varied. Some

common causes are listed below.

  • Cause 1 – An online restore fails due to logfiles

    missing from the temporary folder that is specified in the Microsoft Windows

    2000 Backup program under temporary location for log files.

  • Cause 2 – A hardware failure causes loss of logfiles in

    the logfile sequence required for the restore.

  • Cause 3 – After repairing the priv1.edb database

    with Eseutil /p, you receive Event ID 454 when trying to start the public

    information store. The errors indicate that a problem is occurring when

    trying to replay the log files when the public information store is trying to

    mount. This error can occur if after running eseutil /p against priv1.edb, you

    do not remove the transaction logs. Then if you do not run eseutil /p
    against pub.edb, the pub1.edb file is looking for a different set of log files

    than the priv1.edb file. Therefore, Event ID 454 reports the files as

    “missing”.

   
User Action

Generally, verify whether or not the log files have been

moved or deleted. If the log files have been deleted, restore them from backup

media. If they have been moved, move them to the appropriate location. The

event text will specify the required files.

Here are some specific resolutions for the common causes

above.

  • Resolution 1 – Attempt to locate the missing logfiles and

    place them in the appropriate folder and run Eseutil /cc (hard recovery) or

    run Eseutil /cc /t (using the /t

    switch) to specify another location for all the necessary logs together in one

    folder and mount the database. If the logfiles cannot be located,

    restore from an earlier backup or as a last resort, repair the database, run

    Isinteg -fix, and ExMerge the results to a blank database.

  • Resolution 2 – Restore from an earlier backup or as a

    last resort, repair the database, run Isinteg -fix, and ExMerge the results to

    a blank database.

  • Resolution 3 – Repair the public information store.

    Remove all the transaction logs. Run Isinteg -fix against the private

    store and then against the public store. ExMerge the results of the

    private store to a new blank private store. Save all public folders to .pst

    files and then bring the information back from .pst files to a new blank

    public store or request Pubmerge from Microsoft Product Support Services.

Related:

Leave a Reply