Resolving Event ID 489 in Exchange Server

Microsoft Exchange Server database file can often develop errors, which it finds unable to remove by normal repair methods. Inability to open a database file is one such error. An Exchange Recovery Tool comes handy when your Exchange database becomes corrupted and you have no backup to restore.

The further discussion depicts a commonly occurring problem when trying to open an Exchange database file. In such situations, you can encounter unexpected error and file open operation might fail. On viewing the application event log, you may observe the below event log:

Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 489
Computer:Computer Name
Description: Process name [process id] file name: An attempt to open the file [path\file name] for read-only access failed with [Error Code and Explanation]. The open file operation will fail with error [Error Code].

Cause and Resolution

The actual cause of event 489 can be determined by the error code ('error_code') displaying at the end of its 'Description' section. Below are the possibly occurring error codes along with their causes and solutions:

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

The file is in use by some other process or utility like, a virus checker or a backup program. Another cause can be insufficient permissions on folder containing database files to let the store to function correctly.

Thus, you need to configure the program using the database file to not scan the Exchange Server directories and/or to change the folder permissions to the default ones.

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

The requested database page cannot be accessed due to an I/O error. It could be because of disk or controller failure or because the path to check file is incorrect.

You should run chkdsk /f /r command, check valid permissions on Exchsrvr folder, ensure the correct path to check file, and troubleshoot file-level anti-virus software scanning. After this, you need to either restore the database from backup or repair the database using Exchange Recovery Tool- eseutil/p, isinteg -fix, and ExMerge.

Error -1023= 'JET_errInvalidPath' = Invalid file path

Possible causes are changed path to log files or check files before restoring and corrupted check files or temporary files created while a defragmentation or a repair.

Therefore, you need to place back the files to their original locations and remove the corrupted files. To correct database inconsistency, you need to either restore the database from backup or repair the database using eseutil/p, isinteg -fix, and ExMerge tools.

Exchange repair utilities can delete the corrupted pages. For safe repair, use of Exchange Recovery Software is recommended.

Stellar Phoenix Mailbox Exchange Recovery is a reliable utility that is used to repair corrupted Exchange database and restore its mailboxes as *.pst files at a safe location. This Exchange Server Recovery software supports MS Exchange Server 2013, 2010, 2007, 2003, 2000, and 5.5 and can also recover deleted mailboxes.Visit this tool http://exchange.stellarservertools.com/

Tips To Resolve “Operation terminated with error...” Error Message

Eseutil/p is an inbuilt repair utility of MS Exchange Server that repairs corrupted Exchange Server databases at both table and page level. While the repair utility proves successful in repairing most of the corrupted databases, there are certain situations wherein the command fails to repair a corrupt database. In such situations, it displays an error message. This happens when the database is severely damaged. Since the database cannot be repaired, it remains corrupt, and the data saved in it remains inaccessible. To access database in such situations, a user needs to restore database from a previous online backup. However, in the absence of an updated backup, a user needs to repair the database using a third-party Exchange Server Repair application.

For detailed explanation of the above problem, consider a practical case wherein your Exchange Server database gets corrupted. And, when you try to repair the database using Eseutil/p utility, you encounter:

“Operation terminated with error -1605 (JET_errKeyDuplicate, Illegal duplicate key) after xxx.xxx seconds.”

Data saved in the database becomes inaccessible after the above error message appears. Additionally, the same error message repeatedly occurs when you try to repair your database.

Cause:

The fundamental reason for the occurrence of the above error message is that the repair utility might rebuild B-trees incorrectly. This will change the complete metadata structure of the database, leaving it in a permanently non-repairable state.

Resolution:

To resolve the above error message and to access the records saved in the database, a user needs to obtain the latest service pack of MS Exchange Server 5.5 and perform repair. However, if the repair utility is unable to repair the database even after installing the service pack, then you need to opt for an advanced commercial Exchange Server Repair application.

An Exchange Repair software is a powerful utility specifically designed to repair MS Exchange database, that has become corrupted due to logical crash. The read only utility performs repair without making any change in the original database file.

Exchange Repair Software provides absolute repair of Exchange Server 5.5, 2000, 2003, and 2007 after any logical crash. The repair tool recovers almost all objects of database, such as, emails, notes, appointments, tasks, and attachments. Designed for Windows 7, Vista, XP, 2003, and 2000, the Exchange Server Repair software comes with an interactive user interface.

Troubleshooting Event Ids 9518, 9175, and 454 at MS Exchange Startup

The Event Ids in Microsoft Exchange Server form most important parts of system diagnosis. These cryptic error messages allow the user to diagnose the logging problems. While there are various reasons for the occurrence of these event id, the most important is the corruption in the 'Information Store'. For easy resolution of any event id, the user can restore the database from an updated backup. However in case of absence of an updated backup, the user requires a powerful Exchange Server Repair software to repair the database.

As a practical case, your server locks up for no reason and when you reboot, the MS Exchange 2003 does not start. On viewing the event log, you view a series of event ids:

“Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date: 6/7/2005
Time: 5:56:43 PM
User: N/A
Computer: CRC2K3
Description:
Error Log file is corrupt starting Storage Group
/DC=local/DC=cr/CN=Configuration/CN=Services/CN=Microsoft
Exchange/CN=CityRealtyMail/CN=Administrative Groups/CN=First Administrative
Group/CN=Servers/CN=CRC2K3/CN=InformationStore/CN=First Storage Group on the
Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.

Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Date: 6/7/2005
Time: 6:07:09 PM
User: N/A
Computer: CRC2K3
Description:
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are
network problems or the Microsoft Exchange Server computer is down for
maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000

Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 454
Date: 6/7/2005
Time: 5:56:43 PM
User: N/A
Computer: CRC2K3
Description:
Information Store (448) First Storage Group: Database recovery/restore
failed with unexpected error -501.”

Next, when you try to mount the 'Mailbox' or 'Public Folder', you encounter the below error message:

“The database files in this store are corrupted”

Cause:

The cause for the occurrence of the above error message is corruption of Exchange Server database.

Resolution:

To resolve the above error message and to repair the Exchange Server database, you have to use an effective Exchange Server Repair application. Such Exchange Repair utilities employ extensive scanning techniques to repair and restore corrupt Exchange Server database.

MS Exchange Repair is an answer to all logically corrupted Exchange Server databases. With recovery of deleted mailboxes, the Exchange Repair application repairs databases created in Exchange Server 5.5, 2000, 2003, and 2007. The repaired EDB file is saved in a .pst file format.

Information Store Corruption due to RAID Issues

One of the common reasons for Exchange Information Store to get corrupt is hardware issues. Thus when you identify server consolidation for Exchange Server computer, experts suggest you to adhere to Windows Server Catalog tips. The most important is a reliable storage subsystem and that's the reason you are often recommended to use Redundant Array of independent Disk (RAID) configuration. This not only increases performance by allowing multiple I/O operations but also adds to reliability. But unfortunately there can still be instances that may bring corruption to message store. If one or more of RAID components fail, the Exchange Information Store can catch corruption. In such situation, you need an Exchange Recovery solution to repair the database and recover the lost data.

Consider you use a RAID 2 system to run Exchange Server. All the Information store data including the log files are stored on the same drive. You observe that one of the RAID drives shows typical corruption issues. So you replace the drive, but you experience similar kind of problems with other drives as well.

Later, you notice that you cannot mount the Information Store. When you run eseutil /mh command to check the integrity of the database, it shows that Information store is corrupted. The database files and log files (typically, e00.log file) are damaged.

Cause

Since disk issues are repeatedly observed, it indicates issues with the RAID controller that has ultimately corrupted the Information Store database files.

Solution

You need the following solutions to deal with such problems:

1. Run eseutil /p command to repair the corrupted database. Keep in mind that this can delete the corrupted pages, so to prevent against critical data loss, it is recommended to use the command on a database backup.
2. Restore from a valid backup. But it is likely that database backup may also not exist in usable state. The reason is that the corruption problems have been continuous for considerable time and it is possible that you might have backed up the corrupted Information Store.
   
3. Use a third-party Exchange Recovery utility. The Exchange Server Recovery software can scan and then repair the corrupted Exchange database using powerful, yet safe, algorithms.

Exchange Server Recovery Software is a reliable tool that repairs corrupted Exchange database and extracts mailboxes as *.pst files while keeping the original database unaffected. The Exchange Recovery Tool supports MS Exchange Server 2007, 2003, 2000, and 5.5. The tool can also recover deleted mailboxes.

EDB Recovery to Fix Transport Database Corruption

Are you facing fatal errors while accessing your Microsoft Exchange Server 2007 database? Is your EDB (Exchange Server Database) file is inaccessible? The fatal error in Exchange server aborts the application and thus makes it unusable. This behavior of MS Exchange Server renders all your valuable data inaccessible and cause critical data loss situations. In order to get your precious data recovered in such situations, you need to repair and restore the damaged EDB file, using an EDB Recovery solutions.

As an example, MS Exchange Server 2007 Management Pack for Operations Manager supervises the MS Windows Application Event log on systems, which are running MS Exchange Server 2007 and returns the below event:

“Product Name: Exchange
Product Version: 8.0 (Exchange Server 2007)
Event ID: 17003
Event Source: MSExchangeTransport
Alert Type: Critical Error
Description: A Transport database operation has encountered a fatal error. The database may be corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required.”

After the above error, Microsoft Exchange Server does not let you access your database. At this point, you have to verify the cause of this problem and perform EDB File Recovery by resolving it.

Cause:

The error message below indicates that specified ESE (Extensible Storage Engine) database is damaged. It is preventing MS Exchange Server services from starting.

- ESE, also called JET Blue, is an ISAM (Indexed Sequential Access Method) data storage technology intended by Microsoft. The ESE is particularly used as a key component of the Microsoft Exchange Server and the Active Directory.

How to Fix ESE Corruption:

You can carry out following things to sort out this issue-

1. 
   
   Delete the defined database and corresponding transaction logs. You must not remove the database if you have significant data in the database.
2. 
   
   Repair the damaged database using Isinteg.exe tool or restore it from backup.

However, if none of the above methods helps you to work around the problem, EDB Recovery Tool is the only option to go for. They carry out in-depth scan of entire EDB file using high-end scanning techniques and restore all database objects such as emails, notes, contacts, tasks, and more.

The software enable you to recover corrupt EDB file in a quick and easy way as they are incorporated with simple and self-descriptive graphical user interface. The integrity of your database is always preserved by these tools.

EDB Recovery Software is the most preferred recover EDB solution to repair and restore EDB files in all cases of corruption. The EDB Recovery is designed for Microsoft Exchange Server 2007, 2003, 2000, and 5.5.