() An attempt to open the file “” for read only access failed with system error : “”. The open file operation will fail with error .

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

An unexpected error was encountered while trying to open a file.

You will receive the following phrase in the event Description:

An attempt to open the file [path\file name] for read-only access failed with [Error Code and Explanation]. The open file operation will fail with error [Error Code].

The cause depends on the Error listed at the end of the Description section of the event. The most frequent causes are as follows:

  • 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. A flat file backup system or antivirus software may be running against the database, the check file directories, or drive M. This error can also occur if the permissions on the folder (such as MDBDATA) that contain the files for the information stores are not sufficient for the stores to function properly.
  • Error -1022 = 0xfffffc02 = 4294966274 = 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 check file. A disk or controller failure may have 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 490 Event. This issue may occur because the path for the check file (such as E00.chk) is not correct, which may be caused by a drive failure.
  • Error -1023 = 0xfffffc01= 4294966273 = JET_errInvalidPath = Invalid file path. This error can be caused by changing the path for the log files or the check file prior to a restore. This error can also indicate a corrupt check file (such as E00.chk) or a temporary file built during a defragmentation or a repair. In the case of the corrupt files, this error may occur even if the path to the file is correct.
   
User Action
  • For Error -1032, change the permissions on the folders that contain the Exchange database files to the default permissions. Configure the flat file backup and antivirus software to not scan the Exchange database subdirectories, or drive M. Use Exchange-aware online backup and antivirus software.
  • For Error -1022, run “chkdsk /f /r” (without the quotation marks). If chkdsk does not resolve the issue, examine the permissions on the Exchsrvr folder structure. Make sure that SYSTEM has full control of Exchsrvr and all subfolders on each partition that contains Exchange data. If you still cannot mount the databases, troubleshoot any Windows NT file-level antivirus software running on the Exchange server. Check the System Log for I/O or drive errors near the time of the 490 Event. Check and correct the path for the check file (such as E00.chk). Correct the root cause and then restore from online backup if there is a recent backup or as a last resort, perform a repair, Isinteg -fix, and ExMerge to a new Information Store.
  • For Error -1023, place the Exchange database files back in their original locations before performing the restore. Alternatively, if the .chk is corrupt, you may be able to remove it and read all the transactions into the database. If the database remains inconsistent, then restore from online backup if there is a recent backup or as a last resort, perform a repair, Isinteg -fix, and ExMerge to a new Exchange database.

Related:

Leave a Reply