() An attempt to move the file “” to “” failed with system error : “”. The move file operation will fail with error .

Details
Product: Exchange
Event ID: 486
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>An attempt to move the file “<file name>” to “<file name>” failed with system error <error code>: “<error message>“. The move file operation will fail with error <error code>.
   
Explanation

If the Exchange Server database service is denied access to its own log files (*.log), errors similar to the following may be seen:

An attempt to move the file [path\filename] failed with [error code]. Generally, the error refers to a failure to rename the current log file such as E00.log to the latest log file in the storage group such as E0001499.log or to rename E00tmp.log to E00.log. Common causes of this event include:

  • In the Description section of Event ID 486, you may see Error -1811 = JET_errFileNotFound. The log file may actually be missing or there may be other causes for this error. For example, E00.log file 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.
  • Another process has “stolen” the file. A virus checker may mistakenly quarantine a file, or a backup process may temporarily deny access. In this case, you may see Error -1032 in the Description section of Event ID 439. Error -1032 is equivalent to JET_errFileAccessDenied, which is defined as cannot access file – the file is locked or in use.
  • A disk or controller failure has occurred, and access to the entire drive has been lost, sometimes temporarily. Check the system log for I/O or drive errors near the time of the 486 Event. In this case, you may see Error -1022 in the description of Event ID 486. Error -1022 = JET_errDiskIO = Disk IO error. The -1022 error is a generic error that appears whenever a disk input/output (I/O) problem prevents Exchange from gaining access to a requested page in the database or to a transaction log.
  • Permissions have been removed from the folder where the file resides.
  • The file has been marked read-only.
  • The folder containing the file has been renamed or deleted.
  • The device drivers installed with the operating system for the server hardware can cause these errors.
   
User Action
  • Check for alerts related to full disks and resolve as necessary.
  • To troubleshoot such errors, you must discover what has suddenly blocked the database service from access to its files. In many cases, restarting the affected server “breaks” the lock if you are unable to find another way to do it.
  • Confirm sufficient access to the disks.
  • Make sure that the device drivers and manager software that comes with the hardware are totally installed and up to date.
  • If the database is still running, you may have to use Move Mailbox or ExMerge to move the mailboxes to another server.
  • If the database will not mount, you may need to restore from online backup. If there is no valid backup, as a last resort, you may need to repair the database with Eseutil /P, run isinteg -fix until all fixes are removed, and then mount the database and ExMerge to a new, blank database.

Related:

Leave a Reply