Dealing with silent Index corruption in Exchange Server

When you move the Exchange Server database to a system that do not have the same Locale ID (LCID) and then try to defragment the same, it might report an index corruption. Also, when you load the accurate Locale on the server and then try to defragment the database, it won’t report the index corruption.

A LCID is a 32-bit value termed by Microsoft Windows comprising of a sort ID, language ID and reserved bits which is similar to the particular language. After this situation, the data in Exchange Server becomes inaccessible. If you move database between computers having different LCID installation status, then possibility of occurrence of silent database index corruption is high. For example:

• When LCID that was previously uninstalled is reinstalled, then there is a possibility of silent index corruptions
• When Exchange Server database is copied to a different computer, de-fragmented and then copied to the original computer, it might result in index corruption.

The thing that disturbs you the most is database corruption that leads to inaccessibility of EDB file thereby causing massive data loss. There is this latest service pack for Exchange Server made available by Microsoft, it can fix this problem so it won’t occur in future but it cannot deal with the corruption. The corrupt database indexes will still remain corrupt, even after up-gradation.

In this situation, the only solution you are left with is to perform Exchange database recovery to repair damaged indexes. Exchange database recovery can be made possible through the Exchange Server Recovery software. Exchange Server Recovery software is a powerful third party Exchange recovery tool that can take care of almost all kinds of EDB corruption errors. The Exchange Server recovery software supports all versions of Exchange Server, such as Microsoft Exchange Server 5.0, 5.5, 2000, 2003, 2007 and 2010.

Comments are closed.