Tuesday, March 6, 2012

Resolving Exchange Sever Error -338 (JET_errBadParentPageLink, Database corrupted)

Microsoft Exchange Server, no doubt, is one of the best email server applications. It is a transaction based messaging tool and provides better security system against important data loss. Despite of powerful data security, Exchange database files still become damaged and corrupted due to various reasons. The most common causes of corruption are Dirty shutdown, hardware failure, database file oversize issues, virus attack, human errors and due to application bugs. Such paradigms directly affect the Information Store databases ( Priv.edb and Pub.edb). Well, such kind of problematic situations can be tackled easily through the use of an updated backup or some advance third party Exchange recovery software if the built-in utilities fail. Let us do a general talk on a problematic situation which is faced by Exchange server administrator at an attempt to check the database integrity by executing the inbuilt eseutil commands. Error messages appear to be like this:

“Operation terminated with error -338 (JET_errBadParentPageLink, Database corrupted)…”

Presence of the above error message directly results into an inaccessibility of Exchange server data. As soon as this error message appears, data of Exchange database file become inaccessible. So, it becomes necessary to find out the cause and solution for this problem.

Basically, this error occurs when there is corruption in Exchange information store database which can occur due to unexpected power failure or any other reasons.
In order to get rid of the above problem, you may use following methods:
  • Restore database from the last online valid backup copy.
  • Transfer all possible mailboxes to a new mailbox store.
However, if the above solutions do not work and problem still persists, then the only option left to overcome this problem is using the Exchange server repair tool. You can use built-in repair tools like esesuitl /r (soft recovery) and eseutil /p (hard repair) to repair and bring the database into consistent state.
i) Eseutil /r command line tool never cleans any instance of corruption. It is only applied to bring the Information store database into consistent state.
ii) Eseutil /p utility is used for cleaning the complete corruption from Exchange information store database and followed by isinteg. . This hard repair tool can cause serious data loss situation sometimes as it removes the damaged pages. So, my advice is to backup of the database before running it.

In case, any of the above mentioned solutions are unable to alleviate the problem or you want to get data upto 100 %, only way is a third-party Exchange database recovery utility. Now a days, ample of third party tools are easily available online. Their main purpose is to recover data from corrupt/damaged Exchange database file or from failed Exchange server. Moreover, these utilities come with simple and self-explaining user interface and do not require prior technical skills. Stellar Phoenix Exchange Server Recovery is one such tool.

Stellar Phoenix Mailbox Exchange Recovery is one of the highly efficient utility that analyze each and every part of Exchange database file to repair and recover corrupt data upto 100 %. This reliable and high-end Exchange server recovery program provides preview of data before actual recovery and supports MS Exchange Server 5.5, 2000, 2003, 2007, and 2010. The Exchange mailbox recovery tool has easy recovery steps and can be run on Windows 7, Vista, XP, 2003, and 2000.

No comments:

Post a Comment