| Microsoft Exchange Server database file can | | | | like, a virus checker or a backup program. |
| often develop errors, which it finds unable to | | | | Another cause can be insufficient permissions on |
| remove by normal repair methods. Inability to | | | | folder containing database files to let the store to |
| open a database file is one such error. An | | | | function correctly. |
| Exchange Recovery tool comes handy when your | | | | Thus, you need to configure the program using |
| Exchange database becomes corrupted and you | | | | the database file to not scan the Exchange |
| have no backup to restore. | | | | Server directories and/or to change the folder |
| The further discussion depicts a commonly | | | | permissions to the default ones. |
| occurring problem when trying to open an | | | | Error -1022='JET_errDiskIO' = Disk I/O error |
| Exchange database file. In such situations, you can | | | | The requested database page cannot be |
| encounter unexpected error and file open | | | | accessed due to an I/O error. It could be because |
| operation might fail. On viewing the application | | | | of disk or controller failure or because the path to |
| event log, you may observe the below event log: | | | | check file is incorrect. |
| Event Type: Error | | | | You should run chkdsk /f /r command, check |
| Event Source: ESE | | | | valid permissions on Exchsrvr folder, ensure the |
| Event Category: General | | | | correct path to check file, and troubleshoot |
| Event ID: 489 | | | | file-level anti-virus software scanning. After this, |
| Computer:Computer Name | | | | you need to either restore the database from |
| Description: Process name [process id] file name: | | | | backup or repair the database using Exchange |
| An attempt to open the file [path\file name] for | | | | Recovery Tool- eseutil/p, isinteg -fix, and |
| read-only access failed with [Error Code and | | | | ExMerge. |
| Explanation]. The open file operation will fail with | | | | Error -1023= 'JET_errInvalidPath' = Invalid file path |
| error [Error Code]. | | | | Possible causes are changed path to log files or |
| Cause and Resolution | | | | check files before restoring and corrupted check |
| The actual cause of event 489 can be | | | | files or temporary files created while a |
| determined by the error code ('error_code') | | | | defragmentation or a repair. |
| displaying at the end of its 'Description' section. | | | | Therefore, you need to place back the files to |
| Below are the possibly occurring error codes along | | | | their original locations and remove the corrupted |
| with their causes and solutions: | | | | files. To correct database inconsistency, you need |
| Error -1032= ' JET_errFileAccessDenied'= File | | | | to either restore the database from backup or |
| cannot be accessed | | | | repair the database using eseutil/p, isinteg -fix, and |
| The file is in use by some other process or utility | | | | ExMerge tools. |