Find Effective Solution To Resolve Event Id 489 In Exchange Server

By Author: canryjones
Total Articles: 1
Comment this article

It is quite consistent that Microsoft Exchange Server database file can get struck with errors, now, all of them cannot be recovered under normal mode. The most common errors hitting the database are, data file cannot be accessed. This is a quite recurring error and does not allow users to access any data file. This situation does not even allow user to perform file operation and they are struck in between, the following application event log gets displayed:

Event Type: Error Event

Source: ESE Event

Category: General Event ID: 489 Computer: Computer Name

Description for the above message: (Process name and id), attempt made to open file (path file name) for read-only access is failed with (error code as well as message is displayed). The open file operation will fail along with error and code.

Possible causes and how to resolve the error:

The prime reason for the occurrence of the event 489 is determined by the error code which is displayed at the end of its description. The error is listed below:

Error -1032= ' JET_errFileAccessDenied'= File cannot be accessed

Now ...
... this situation indicates that file is being used for some other purposes or is accessed with a virus checker or a backup program. Other reasons can be insufficient permissions on folder with database files. Now user has to configure the program with database file.

Error -1022='JET_errDiskIO' = Disk I/O error

The required database base page cannot be accessed as I/O error has occurred. Now, this could happen due to disk or controller failure and the path to check file can be wrong. In this case user has to run the run chkdsk /f /r command, check for required permissions on Exchange folder, make sure the path is correct to check file. Also user has to restore the database from backup or initiate a repair process.

Error -1023= 'JET_errInvalidPath' = Invalid file path

For the above error changed path to log files or check file is been disturbed, hence users have to place back the files to their original location and remove damaged files. To get rid of entire data inconsistencies it is quite essential for users to maintain a backup or repair the database with help of Exchange Server Recovery utilities including eseutil/p, isinteg -fix, and ExMerge tools.

In case when Exchange Server utilities for the purpose of repairing EDB file fails to perform any good users can choose for adept third party tool. Kernel for Exchange Server Recovery is instant and output-driven tool meant to perform email recovery as well as Exchange mailbox recovery from damaged EDB and STM files of MS Exchange Server 5, 5.5, 2000, 2003 and 2007.

So, whenever you are in need to deal with entire Exchange Server damage issues making use of repair tool is a viable as well as safe idea. Hard Disk Recovery tool will easily omit damage issues and will allow user to maintain a feasible workflow in Exchange Server.