With the newer versions of Exchange Server, the application may have become better in different perspective, but the problems like not mounting of Exchange database is still the same. Here, is a list of some probable causes which might be creating the problem and the severest one among them is which says that database is corrupted and needs Exchange Server repair:
Hardware Issues: With the event ID 474, you may discover that due to some hardware problems at hard disk level, the database has got corrupted and thus is failing to mount. This case needs handling through EDB recovery: either through backup after replacing the hard drive, moving the mailbox to other server or having an Exchange Server recovery help from service part of data recovery industry.
Not having the sufficient rights:
If you get Event ID 2102, 9519, 1029, 1005, 90741121, 125 or 9004, the problem is stuck with the modification of the SeSecurityPrivilege right. To fix the issue, manually assign the correct permission or you can also run Exchange setup in Domain Prep mode.
Transaction logs modified or deleted: The installed antivirus program should not have power over transaction log folder for scanning, for the reason that server crash may happen if any virus is detected in these logs due to the modification or deletion of affected logs. You may get Event ID 455 in this respect.
Database size limitation; Exchange server 2000 and 2003 standard edition sets limit of 16 GB to the database size, which might be the cause. Exchange server
considers PRIV.EDB and PRIV.STM as the total database size. As a cure, you can set the maximum database size to 17 GB by editing the registry and removing the undesired data. After this, remove this limit as this could raise the database corruption further.
Active Directory permission modified: If the information store has no privileges to be read, the database will fail to mount. The other reason could be that server object is not there in the Active Directory. So run Exchange Setup in Domain Prep mode or have correct ADS editing.
Among all, database corruption is the real issue to handle; either occurred due to hardware problems or some logical issues. EDB repair is the way which can medicate, but needs the real help.
As stated earlier also, hard disk damage like cases has way through Exchange server recovery service, while, in logical corruption, you have an alternative of using Eseutil utility for EDB recovery. But, I advise you not to use this as of its destructive nature to the corrupted pages; instead you can have easy-to-use third party applications, called Exchange Server repair software for the same.
Stellar information Systems Limited offers you both EDB repair solutions, which are high in bringing effective results.
Stellar Phoenix Mailbox Exchange Recovery software is the application to extract all the mailboxes from the corrupted database. This Exchange Server repair product is of read-only design, having superb scanning power.
Exchange Server recovery service era is enriched with Class 100 Clean Rooms, high-tech tools and techniques and the focused approach to EDB recovery. Under this, you will find damaged hard drive components corrected or replaced and EDB recovered.
