Error 1206 In Exchange Server

Exchange Server database corruption is not an unusual incident for the database administrators. Those who haven’t experienced it yet may strongly face it in the future. Virus attack, network malfunctions or unexpected system shutdowns are the reasons that corrupt your database and make it unusable.

Now, eseutil/p and eseutil/g are the utilities which can respectively repair and check the integrity of Exchange database (EDB). But sometimes, running these commands may not prove to be productive as some error messages like following may pop up, while trying to run the specified utilities:

“-1206, JET_errDatabaseCorrupted”

The command crashes out and database goes to the inconsistent state. Some of the users also report that the similar error message is encountered, when the upgrading of Exchange Server is tried. In such situations, the upgrade process may fail again with an additional error message, showing unexpected conditions in the database.

When you get error 1206 in Exchange Server, this is not always mandatory that the database is corrupted, as has been stated in the mentioned error message. So, see the recommended points:

.Try to mount the database and check that whether it is possible. If yes, make a backup of all the mailboxes to a new mailbox store.

.File level scanning and antivirus scanning should not include EDB and log files. So make sure that these files are not being scanned.

See into the System and Application logs. Here, you will get some hints of the actual problem. If it says corruption in Exchange database, go for EDB repair.

In case, the mentioned error message has resulted after an upgrade failure, this is quite possible that the database has upgraded, may be partially, but the upgraded Exchange Server files have not been copied to a folder known as the Exchsrvr folder.

If you find EDB inaccessible and also System and Application logs signifies the corruption, use EDB recovery solutions to solve the problem. The EDB repair software is available in the market, which can actually scan the corrupted database and correct it for use. It comes with advanced recovery ability and the read-only mode keeps the critical data safe and intact.

Stellar Phoenix Mailbox Exchange Recovery is the ultimate utility to fix such issues. This EDB repair application uses the most powerful scanning algorithms and repairs the corruption. It supports Microsoft Exchange Server 5.5, 2000 and 2003. The application performs EDB recovery for all the database objects.

By: Mahi Sony

Article Directory: http://www.articledashboard.com

Mahi Sony work as a freelancer and researcher of data recovery & partition recovery Software.