During undoing of a logged operation in database ‘%.*ls’, an error occurred at log record ID %S_LSN. Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.

Details
Product: SQL Server
Event ID: 3314
Source: MSSQLServer
Version: 10.0
Component: SQLEngine
Symbolic Name: ERR_LOG_RID2
Message: During undoing of a logged operation in database ‘%.*ls’, an error occurred at log record ID %S_LSN. Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
   
Explanation

This is the rollup error for undo recovery. There should be a previous error logged in the Windows event log indicating the specific failure.

   
User Action

Restore database, file or page from backup or repair database.

Related:

process name (process id) %3The log signature of the existing logfile file name doesn’t match the logfiles from the backup set. Logfile replay cannot succeed unless all signatures match.

Details
Product: Exchange
Event ID: 457
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) %3The log signature of the existing logfile file name doesn’t match the logfiles from the backup set. Logfile replay cannot succeed unless all signatures match.
   
Explanation

Mismatched log files have been detected. You are restoring

to a recovery server that has a different set of log files. Log file replay

cannot succeed unless all signatures match.

You will receive the following phrase in the event

Description:

Information Store (number) The log signature of the

existing logfile E0n.log does not match the logfiles from the backup set. Logfile

replay cannot succeed unless all signatures match.

The basic reason for the event is that the E0n.log file (the

current log file for the storage group, such as E00.log) has a different log

signature than the log files that have been restored from the online restore. 

A typical scenario for this to happen is as follows.  All the information

store service files have been removed. In order to restore an online backup of

an Exchange computer, you must have the Microsoft Information Store

running. If you have not checked “Do not mount this store at start-up” on the

Database tab, and you start the Information Store service, then a new E00.log

file is created.  The log signature for this file does not match the

signatures of the log files from the backup, and the Information Store fails to

replay logs and mount the databases.

   
User Action

Dismount all the databases in the storage group.  Do

an offline backup and then remove all Information Store log files and check files

for the storage group.  Check “Do not mount this store at

start-up” on the Database tab for all databases in the storage group. 

Start the Information Store service.  Uncheck “Do not mount this store at

start-up” on the Database tab for all databases in the storage group. Perform

the online restore.

Related:

() The logfile is damaged and cannot be used. If this logfile is required for recovery, a good copy of the logfile will be needed for recovery to complete successfully.

%1 (%2) %3Corruption was detected during soft recovery in logfile %4. The failing checksum record is located at position %5. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable.

Details
Product: Exchange
Event ID: 465
Source: ESE
Version: 8.0
Symbolic Name: LOG_CORRUPTION_DURING_SOFT_RECOVERY_ID
Message: %1 (%2) %3Corruption was detected during soft recovery in logfile %4. The failing checksum record is located at position %5. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable.
   
Explanation

This Error event indicates that corruption was detected in the log file during soft recovery. This log file is damaged and unusable. Soft recovery is an automatic transaction log file replay process that occurs when a database is remounted after an unexpected stop. The soft recovery process only replays logs from the transaction log file path specified for the storage group that contains the affected databases. Affected databases are described as having been shut down in a dirty state. Soft recovery uses the checkpoint file to determine which transaction log file to start with when it sequentially replays transactions into databases. This process makes the databases up to date with all recorded transactions.

   
User Action

To resolve this error, do one or more of the following:

  • Unless the log file specified is the current log file in use, restore the log file from a backup copy.

  • Use the Exchange Server Database Utilities (Eseutil.exe) tool with the /R and /A switches to recover a database with missing log files. For more information, see Eseutil /R Recovery Mode.

If you are having difficulty resolving the issue, contact Microsoft Product Support. For information about contacting support, visit the Contact Us page of the Microsoft Help and Support Web site.

Related:

() The database engine has begun replaying logfile .

Details
Product: Exchange
Event ID: 301
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <number>The database engine has begun replaying logfile <file name>.
   
Explanation

The database engine has begun replaying logfile [path]\[logfile name].

This event is a common event that is seen both in an online Exchange-aware restore of an information store database, and in an offline restore if there are logfiles that need to be replayed when starting the database.

   
User Action

In normal circumstances, no user action is required.

Check the application event log in the Microsoft Windows NT Event Viewer for any errors or anomalies that might occur when the database starts. An ESE Event ID 301 is displayed for each log file that is replayed. Watch carefully for errors and warnings during the recovery process. If the restore fails to complete, check the log for corrupt or missing log files. You need to determine exactly where the failure occurred.

The resolution depends on the exact events and errors in the Description of the events and you may need to do further research in the Microsoft Knowledge Base. In some cases, you may need to restore from an earlier backup. If there is no valid backup and only as a last resort after research all other options, you may need to repair the database.

Related: