%1 (%2) %3An attempt to open the file “%4” for read only access failed with system error %6: “%7”. The open file operation will fail with error %5.

Details
Product: Windows Operating System
Event ID: 489
Source: ESENT
Version: 5.2
Symbolic Name: OSFS_OPEN_FILE_RO_ERROR_ID
Message: %1 (%2) %3An attempt to open the file “%4” for read only access failed with system error %6: “%7”. The open file operation will fail with error %5.
   
Explanation

An error occurred while a file was being opened.

Probable causes include:

  • The file is locked or in use.
  • A virus checker might have mistakenly quarantined a file, or a backup process might have temporarily denied access.
  • A flat file backup system or anti-virus software might be running against the database, the check file directories, or the M drive.
  • The permissions on the folder (such as MDBDATA) that contains the files for the information stores are not sufficient for the stores to function correctly.
  • A disk input/output (I/O) problem prevented 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 was lost, perhaps temporarily. This issue can occur when the path for the check file (such as E00.chk) is not correct.
  • The path for the log files or the check file was changed before the system was restored.
  • The check file (such as E00.chk) is corrupted.
   
User Action

To solve this problem, do one or all of the following:

If the file is locked or in use:

  • Change the permissions on the folders that contain the information store files to the default permissions.
  • Configure the flat file backup and anti-virus software to not scan the Windows Information Store subdirectories or the M drive.
  • Use an online backup and anti-virus software.

If there is an Input/Output problem, do one or all of the following:

  • Run chkdsk /f /r at the command prompt.
  • Examine the permissions on the folder structure.
  • Troubleshoot any file-level antivirus software running.
  • Check the System Log in Event Viewer for any related I/O or drive events.
  • 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.

If the path was changed:

  • Move the Information Store files back to their original locations and then try to restore again.
  • If the .chk file 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 version.

For more information about this event, see article Q823022 in the Microsoft Knowledge Base.

Related:

Leave a Reply