Sunday, July 31, 2016

Fixed: Exchange Error c1041724 when you try to mount a Database

While mounting an Exchange database restored from the last Exchange backup, sometimes the mounting process fails, and Exchange server prompt the following error messages-

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.”

"C1041724 error occurs when you try to mount a database."

So if you’ve recently encountered one of these errors and looking for the solution, the article describes the possible causes and similar solutions to fix unable to mount Exchange database error

Let’s investigate the root causes when the last time you failed to mount an Exchange database-

1. The very first thing needs to be checked that you’ve restored the database from the Exchange backup accurately Or, if you had forgotten to check The Last Backup Set (Log file replay will start after this restore completes)’ option during the restore process. 

2. Another possible cause is the insufficient disk space. This error can occur if there is not enough free disk space on the drive which contains the restored databases that you’re mounting to Exchange server.

3. Check that if the database was shut in the clean state and correctly restored from the backup.

4. Probably your Exchange database is corrupt, or if you’ve executed Eseutil/p to repair the database but the log files remain intact and not removed. In such case, database fails to be mounted and through the error.

5. And lastly, verify that you haven’t restored more than one storage at a time.

So these are the most common causes why did you fail to mount the database to the server. Fortunately, there are a lot of solutions that fix the database from the error. By following the few steps database can be again mounted to the server with no further errors. Let’s check the best possible solutions-

The first solution, free some additional disk space if the error occurred due to insufficient disk space. All you need to just perform offline database defragment to release the database white space. Database defragmentation is quite easy with the Eseutil utility (Eseutil.exe). And if there is a lot of transaction log files on the same drive too, you can also avail some free space by removing them. Check the Microsoft KB to remove unnecessary transaction log files.

Secondly, while restoring the database make sure Last Restore Set is checked and restore only one storage group at a time.

Lastly but not least, it is recommended to run hard recovery before mounting the Exchange database. There are two standard ways to run hard recovery – either use manual hard recovery using Eseutil command or using an advanced tool for Exchange Server database recovery.

If you’re using manual hard recovery, run the command and mount the database using the Exchange System Manager-

eseutil /cc [path to directory containing Restore.env]

However, it requires strong PowerShell skills if you’re performing it manually. And in case if it fails to run hard recovery, the data from the affected database will be lost in the absence of backup.

So it is recommended to prevent the database from further damages and perform recovery efficiently and mount it again without any failure. Download Stellar Phoenix Mailbox Exchange Recovery software by visiting official web page, and recover the affected database from severely corruption and export it again to a live Exchange Server.

The software lets you perform the database recovery and exporting the mailboxes back to the server in few click without interrupting Exchange server’s other services or any data loss. All you need just to download and install the software, rest sit back, the software will do the remaining job by itself for you! 


No comments:

Post a Comment