() The logfile sequence in “” has been halted due to a fatal error. No further updates are possible for the databases that use this logfile sequence. Please correct the problem and restart or restore from backup.

Details
Product: Exchange
Event ID: 492
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>The logfile sequence in “<directory name>” has been halted due to a fatal error. No further updates are possible for the databases that use this logfile sequence. Please correct the problem and restart or restore from backup.
   
Explanation

The database engine is unable to replay the log file sequence. The following information will be in the Description of the event:

Information Store (number) The logfile sequence in [path] has been halted

due to a fatal error. No further updates are possible for the databases that use this logfile sequence. Please correct the problem and restart or restore from backup.

Because this is a generic error, there are no specific errors associated with this event in the Description section of the Event. Look for errors mentioned in the Description section of related events that refer to problems related to opening, creating, deleting, and writing logfiles. The cause of the error depends on the specific error. The most common errors in the Description section of events related to Event ID 492 are as follows:

  • Error -1811 = 0xfffff8ed = JET_errFileNotFound = File not found. The logfile may actually be missing or there may be other causes for this error. For example, the current logfile (e.g., E00.log) may have a mismatching signature between the log and the database. Another reason for Error -1811 includes the Exchange database and log files may have been put on Network Storage, which is not supported. Also, the checkpoint file may be corrupt, or the log drive itself may have failed. The current logfile may have been seized and deleted or quarantined by antivirus software running on the server. There have also been problems seen creating the temp log file for the storage group (e.g., e00tmp.log ). The temp log file itself may become corrupt.
  • Error -510 = 0xfffffe02 = 4294966786 = JET_errLogWriteFail = Failure when writing to log file. Error -510 can be caused by permissions issues, space issues, SAN issues, and other issues affecting reads/writes to the disks.
  • Error -1032 = 0xfffffbf8 = 4294966264 = JET_errFileAccessDenied = Cannot access file – the file is locked or in use. Another process has “stolen” the file. A virus checker may mistakenly quarantine a file, or a backup process may temporarily deny access. An flat file backup system or anti-virus software may be running against the database or check file directories or drive M. This error can also occur if the permissions on the folder that contain the files for the Exchange databases are not sufficient for the stores to function properly.
   
User Action

No further updates are possible for the databases that use this log file sequence. Correct the problem and restart or restore from backup.

Generally, review the event log for related messages. Correct the problem, bring the storage group online, and then restore the database from backup media. Resolutions for common causes are as follows:

  • For Error -1811, make sure the antivirus software is not running against the Exchange database, the SRS database directories, or drive M. Ensure that the database drive has not run out of space. Ensure that the database file is actually present where it is supposed to be.
  • For Error – 510, investigate the root cause of permissions issues, space issues, and other issues affecting reads/writes to the disks.
  • For Error -1032. change the permissions on the folders that contain the information store files to the default permissions. Configure the flat file backup and antivirus software to not scan the Exchange server information store subdirectories or drive M. Use Exchange aware online backup and antivirus software.

Related:

Leave a Reply