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

Details
Product: Exchange
Event ID: 485
Source: ESE
Version: 8.0
Symbolic Name: OSFS_DELETE_FILE_ERROR_ID
Message: %1 (%2) %3An attempt to delete the file “%4” failed with system error %6: “%7”. The delete file operation will fail with error %5.
   
Explanation

This Warning event indicates that an unexpected error was encountered while trying to delete a file. The file name can refer to a .chk file, a tmp.log file, or a temp.edb file.

The cause depends on the error listed at the end of the Description section of the event. The following are known causes of this event:

  • 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 that contain the files for the Exchange 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. When this happens, Exchange may not be able to write, read, delete, open, or create Exchange log, check, or database files. Check the System log for I/O or drive errors near the time of the 485 event. This issue may also 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 a valid file path. This error can be caused by changing the path for the working directory or the check file in the Exchange System Manager. If the location in the registry shows the old location instead of the new location, error -1023 may result.

   
User Action

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

  • For error -1032, change the folders that contain the Exchange store files to default permissions. Configure the flat file backup and antivirus software to not scan the Exchange store subdirectories. Use Exchange-aware online backup and antivirus software.

  • For error -1022, run chkdsk /f /r. If Chkdsk does not resolve the issue, examine the permissions on the Exchsrvr folder structure. Ensure that System has full control of the C:\Program Files\Microsoft\Exchange Server folder, where C:\ is the directory to which you installed Exchange 2007, 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).

  • For error -1023, place the Exchange store files back in their original locations or change the location in the registry.

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

  • Fix the root cause first. If the databases are inconsistent and you cannot run soft recovery, you may need to restore from online backup. As a last resort, you may need to repair the database with eseutil /p, run isinteg -fix, and then use ExMerge or Move Mailbox or .pst files to move the mailboxes to a new store, delete the current database, create a new one, and then use ExMerge or Move Mailbox or .pst files to move the mailboxes back into the blank database.

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