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

Details
Product: Exchange
Event ID: 490
Source: ESE
Version: 8.0
Symbolic Name: OSFS_OPEN_FILE_RW_ERROR_ID
Message: %1 (%2) %3An attempt to open the file “%4” for read / write access failed with system error %6: “%7”. The open file operation will fail with error %5.
   
Explanation

This Warning indicates that an attempt to open the file path\filename for read and write access failed with the system error.

The file is either a .chk file such as E00.chk or a database file such as priv1.edb or priv1.stm.

The cause depends on the error listed at the end of the Description section of the event. The most frequent causes are listed below.

  • Error -1032 = 0xfffffbf8 = 4294966264 = Jet_errFileAccessDenied = Cannot access file. The file is locked or in use. Another process has locked the file. Antivirus software 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 or check file directories. 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 I/O error. The -1022 error is a generic error that appears whenever a disk 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 = Not valid 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

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

  • 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 to scan the Exchange store subdirectories. Use Exchange-aware online backup and antivirus software. For more information, see the Microsoft Knowledge Base article 328841, Exchange and Antivirus Software.

  • For error -1022, run chkdsk /f /r. If Chkdsk does not resolve the issue, examine the permissions on the C:\Program Files\Microsoft\Exchange Server folder structure, where C:\ is the directory to which you installed Exchange 2007. Also, make sure that System has full control of the Exchange Server folderand all subfolders on each partition that contains Exchange data. If you still cannot mount the databases, troubleshoot any 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, run isinteg -fix, and use ExMerge to place the data to a new database. For more information, see 314917, Understanding and Analyzing -1018, -1019, and -1022.

  • For error -1023, place the Exchange store 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, run isinteg -fix, and use ExMerge to place the data to a new database.

  • For information about ESE error codes other than the ones explained in this topic, see the following Microsoft Knowledge Base articles:

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Leave a Reply