Posts Tagged ‘exchange database error’

Database Corruption While Replication of Public folders

March 8th, 2010


While talking about Microsoft Exchange Server, it’s like a mandate to mention the public folders. The public folders contain user data as well as information critical to the system. The system information is needed for the swift operation of Exchange Server in the environment. Replication of the public folders is done in order to have better performance and effective and easy management of application.

Two types of replication are there: hierarchy replication and content replication. In some cases, replication of the public folders between the Microsoft Exchange Servers becomes troublesome. Replication may cause some inconsistencies in the database and render it inaccessible. These inconsistencies may cause severe data loss and may lead to database corruption while replication of public folders. Thus, need may arise for Exchange Repair using tools.

Practically, when public folder replication request is sent by a system running Microsoft Exchange Server, email scanning might also occur. Messaging Database may also get corrupted at the same time and you may encounter the following error message displayed on your screen:

“Multiple edits have been made. The conflicting edits have been attached to the conflict message.”

At this time, the public folders of the server may get inconsistent and inaccessible. It may lead to critical data loss and database corruption. The job of Exchange Server Administrator is to find out the cause of the problem and go about solving it.

Root cause of the Problem:

There may be cases that a database transaction is written inappropriately and there is an error. This can lead to an imbalanced Exchanged Server transaction state. If virus scanning is enabled, then imbalanced transaction state may promote virus scanning to be done on outbound replication emails. Database may also get corrupted due to imbalanced state of database transaction.

Resolution of the Problem:

To resolve these problems, a hot fix is provided by Microsoft on its website and is downloadable from there. After the installation of the hot fix, database integrity should always be checked by Isinteg.exe utility. The hot fix can solve the problem and the problem will not occur in the future. As far as damaged database is concerned, hot fix can’t repair it. Exchange Recovery is required for repairing and restoring the corrupted database.

There is an affective and advanced third party application available to resolve the problem, called Exchange Database Repair tools. An extensive scanning of corrupted Exchange Server is carried out by this software. The software restores all of the server’s objects intact. The software is equipped with easy graphical user and interactive interface, thus there is no need for prior and sound technical skills and you can save yourself from database corruption while replication of public folders.