In the MS Exchange Server systems, the public folders are well structured databases, which enable you to collect, organize, and share the information with your colleagues in your organization. These public folders are mounted when you start Exchange server and can be replicated between different versions of Exchange servers. However, when you are unable to mount the public store then very often corruption in the EDB file is the major reason behind this. You should try to find out the reason for EDB corruption and try to repair EDB file. If none of the methods work, then the only way-out is to use a third-party EDB repair software to do the needful.

Assume a practical scenario in which you are using MS Exchange 2000 Server Edition. You are unable to mount the Exchange public folder store as the following error message is displayed:

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both...

Exchange Database File(EDB) known as Priv.edb is a rich-text Exchange Server that stores message headers, message text and standard attachments. It is used to store and manage all of the Exchange Server items including MAPI messages, HTTP or SMTP messages.

This is the most important file of Microsoft Exchange Server. Sometimes, this file may get damaged due to dirty shutdown, database inconsistency, virus attack and many other reasons. Nevertheless the cause of Priv.edb corruption, the ultimate results are very drastic and may put you out of the business.

Though Priv.edb corruption is problematic for Exchange Server users, but it is not as much catastrophic as you think. You can execute EDB repair using third party applications, like Stellar Phoenix Mailbox Exchange Recovery, in all cases of corruption...

Exchange Server transaction logs are stored on Exchange computer hard drive and are crucial for the working of database (*.edb) file. When you start any Exchange Server, ESE (Extensible Storage Engine) checks the database for consistency. This information is revealed by a specific flag in the database header that shows database status as dirty or clean. The dirty database status indicates that there are some uncommitted transactions that need to be replayed. Exchange tries to replay them at the time of mount, but may fail if cannot read them. The reason can be corruption of log files. Such situations can force you to use an EDB Repair Software.

To comprehend these potential problems, consider you use Exchange Server 2007. You experience an unexpected crash (Dirty database shutdown). The next time when you try to mount the database, it gives the below error message:

-1852 0xFFFFF8C4 JET_errLogCorrupted

Logs could not be interpreted 4294965444...

The key construct of an Exchange database file, EDB, is B-trees. Similar to all other B-trees, these structures have hierarchical pages and indexes to allow fast and efficient search. An Exchange Server database show abrupt symptoms, when these indexes get corrupt or are missing. This can occur due to numerous reasons and will make you resort to EDB Repair steps.

While Exchange database indexes are corrupted or missing, the MS Exchange database troubleshooter tool can encounter several entries with event ID 9519 having error code 0xfffffa84 logging in the application log. Due to this, Exchange Server users might experience problems while accessing or mounting the database.

This problem is observed in MS Exchange Server 2000, 2003 or 2007.

Cause

Error 0xfffffa84 of event ID 9519 is logged, if database index corruption is when you:

1.Run database repair command- eseutil /p...

Most of the Exchange database problems (including corruption) occur because the administrator continues to use the very old hardware without any refresh. Thus, it is suggested to keep a timely check through application log and related information. Once the EDB database corruption is confirmed, the administrator can either restore from a good backup or select an EDB Repair option.

To comprehend such situations, let us consider a problem when you cannot mount the Exchange database. You observe that all Exchange services run without any error, but when you try to mount the database, it reports an error as below:

Event Type: Error Event Source: ESE Event Category: Logging/Recovery Event ID: 412 Date: 7/3/2008 Time: 1:40:37 PM User: N/A Computer: SMTPBRMDBALEX2 Description: Information Store (4948) e53f288d-df1b-47ba-9c3b-901e530848a5: Unable to read the header of logfile E:\exchsrvr\mdbdata\E003C9F3.log. Error -530....

Microsoft Exchange Server is a transaction-based and fault-tolerant system and thus, has much better protection against data loss as compare to other messaging applications. Despite of the fact, Exchange Server databases still get corrupt. The common reasons of corruption are abnormal system or power failure, database oversize issues (16 GB), antivirus scanning, virus attack, and application bugs. Such instances can affect any of the Information Store databases, which are Priv.edb and Pub.edb. As an administrator, your primary concern is to restore the data, which is applicable using the last backup or by repairing the database. There are several EDB Repair software available that may work against if the Exchange repair utilities fail and/or backup is not available.

As one of the instances, suppose you experience an unexpected power outage with your Exchange Server computer. After this, when you start the database, you get some events (such as event 467, 9297 etc.) logging in the Application log. When you run eseutil commands to check the database integrity, it gives an error as below:...

An Exchange Server database can get corrupt for several reasons, which include unexpected power failure, corrupted log files, network errors, virus infection and others. Consequently, the database may stop and fail to mount. You can try repairing the database using eseuitl utility. If this fails too, it compels you to apply the latest backup available or repair the database by an EDB Repair product.

For instance, you might come across the below error when dealing with Microsoft Exchange Server:

“Database page read failed verification because of no page data.”

It further suggests to move the existing databases to a new hardware. The error is logged with event 476 in application event log.

Cause

The above error means that the database read operation has failed It generally occurs with error 1019. The causes are: 1.The specific database page that has been referenced within the database file is expected to be in use, but Exchange finds it empty or uninitialized...