Exchange Server databases’ transactions are temporarily stored in transaction log files. At times, you need to remove these files manually, usually when the disk runs out of space or the circular logging is disabled. If you come to such situations, it is recommended to determine that the logs have been committed to database or otherwise will cause problems. The database usually shows Dirty Shutdown state in such cases. However, the other reason for this is that database is corrupt. If it is, you should look for Exchange Recovery solutions.
You can take the following situation when you try to mount an Exchange Server database. In an attempt of mounting the database, you might receive an error as below:
An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.
ID no: c1041724
Exchange System Manager
The mount operation fails after you receive this error message.
Error c1041724 can be encountered if you have run eseutil /p repair utility on the affected database. At this point if Eseutil log files remain intact and are not removed, the database can fail to start with the above error.
To isolate the issue, you need to proceed as follows:
1.You need to first check if eseutil /p command was run. To do so, you should run eseutil /mh command for pub1.edb and priv1.edb and check the repair count value. If it is other than ‘0’, this shows that the command was run.
2.From the previous step, you also need to check for the database consistency. If it exists in Clean Shutdown state, which shows that the log files have been committed, you can safely remove the log files from Exchange Server folder, Mdbdata folder to a backup folder and mount the database.
3.If the database shows ‘Dirty Shutdown’ state, it may be because either all the log files have not been committed yet or the database is corrupt. You can wait for sometime to determine if uncommitted transactions is the case. If not, the database is corrupt that you need to restore from backup or by performing soft recovery.
In cases when database remains corrupted with no access to a suitable backup, you can use third-party Exchange Server Recovery utilities. These special applications allow safe extraction of user mailboxes without any modification to the original content. Exchange Recovery utilities provide you interactive design plus impressive features to experience.
Stellar Phoenix Mailbox Exchange Recovery is a complete tool that repairs Exchange database repair systematically. It is a safe and powerful Exchange Server Recovery tool that supports Exchange Server 5.5, 2000 and 2003. The tool can restore mailboxes in individual .pst files, which can be directly accessed in Outlook. The software is enriched with a realistic approach to repair corrupted EDB file in each instance.