Fixing 'Unable to Mount the Mailbox Store with error c104173c …' error in Exchange Server

Information store is the most vital component of Microsoft Exchange. When the Exchange Server is hit by corruption issues, information store also gets affected. It is made up of four database files viz Priv1.edb, Priv1.stm, Pub1.edb and Pub1.stm. When corruption occurs either Prive1.edb or Pub1.edb falls prey to it. In event of corruption, an Exchange administrator can observe various symptoms including the MS Exchange Information Store service won't start, or clients cannot send or retrieve e-mails or abrupt error messages. In order to isolate the issues, the administrator must use the updated backup copy of the database. However, if no backup is available, he should immediately switch to MS Exchange Repair solutions.

Consider a scenario, wherein, you, being the administrator, try to mount the mailbox store in Exchange System Manager, and receive the following error message:

“Unable to Mount the Mailbox Store with error c104173c The Information Store is Busy”

Cause

The above error indicates the possible corruption in one or both edb files (Priv1.edb or Pub1.edb) of information store.

Resolution

In order to troubleshoot the issue, you must perform the following Exchange Repair steps:

1. Run eseutil/mh command in order to determine if the database is consistent
2. If you get the following output 'Clean Shutdown' , move out all the log files from Exchsvrmbddata folder
3. But if you get 'Dirty Shutdown' as output, perform soft recovery by using eseutil/r
4. If database does not come to a consistent state, perform hard repair by using eseutil/p command.
5. If you use the above command, you may lose some Exchange Server data, including the messages that were contained in the log files that were not committed to the information store database. Therefore, it is a wise decision to use a third-party MS Exchange Repair application.

Such tools repair corrupt .edb files safely and employ improved scanning algorithms to recover inaccessible data in a hassle-free manner. Being-read only they do not modify the original content. Therefore, you can use them blindly and isolate the information store corruption issues efficiently.

Stellar Phoenix Mailbox Exchange Recovery is a powerful and reliable application which repairs corrupt .edb files and restores the mailboxes as individual PSTs. Compatible with Exchange Server 5.5, 2000, 2003, and 2007, this Exchange repair software recovers all e-mail messages, notes, journals, tasks, contacts and other components.

Restoring corrupt EDB file in MS Exchange Server 2007

MS Exchange Server is the server side of the client-server, collaborative application from Microsoft. It ably provides standard email features such as emails, contacts, notes, tasks, calendar items, etc. In addition, it provides you the option to access Exchange Server mobile devices and various web-based browsers. It may be notable that the server information is stored in an EDB (Exchange Information Store Database) file. At times the EDB file may get corrupt due to which you are unable to mount the Exchange Server database. These situations may occur due to various reasons such as abruptly exiting the Exchange Server, virus infections, corruption in the database header, hardware issues, etc. Such cases can be handled by using certain in-built methods. If you are not able to resolve the problem, then you should use an EDB Repair Software to repair the corrupted EDB file.

Consider a scenario wherein you have Microsoft Exchange Server 2007 running in your organization. When you try to mount the database that is running on the Server, you are unable to do so. An error message is displayed, that is:

“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”

Cause:

There could be the following causes for the aforementioned error message:

1. The eseutil /p command was executed on corrupted databases and the log files were not removed during the process.
2. The eseutil command was executed for an incorrect logfile base as shown in the following example:
eseutil /r three-character logfile base name

Resolution:

To resolve this problematic situation, you should perform the following methods for each of the mentioned cause:

1.Resolution for Cause 1: To do this, you should ensure two things:

A) Whether the eseutil /p command was run: This can be done by using the following command in the Command Prompt:
“c:\program files\exchsrvr\bin\eseutil /mh "c:\program files\exchsrvr\mdbdata\name of Exchange database.edb”
i. If the repair count is 1, then this command was run on this database.

B) If the database is in a clean and consistent state: To do this, you should perform the consistency check on the databases. If the database is consistent, then you should move the log files to a backup folder and then mount the databases.

2. Resolution for Cause 2: You should provide the correct parameter to run the eseutil command. For example,
“eseutil /r e00”

Once you perform the mentioned methods, try to mount the database. You will that the problem is now rectified. However, if it is not so then you should use a third-party Exchange Database Repair to extract the corrupted EDB files. Such .EDB repair tools are read-only in nature and are able to convert the EDB files to independent PST files using fast yet sophisticated scanning algorithms.

Stellar Phoenix Exchange Server Recovery is a software that performs Exchange Recovery of corrupted EDB files. It is able to perform repair edb by converting the Exchange mailboxes into equivalent PSTs for each user.

Low Disk Space or Database Corruption Prevents you to Write Data to EDB File

Are you unable to write data to Microsoft Exchange Server database? Is your EDB (Exchange Server database file) inaccessible? This behavior may occur due to either low disk space on Exchange Server computer or corrupt EDB file. If the database is corrupt, you need to restore it from the most recent backup to prevent data loss situations. However, in case backup is not valid or updated, you need to opt for Exchange Recovery solutions to retrieve data from the database.

In a practical scenario, the Information Store Service of Exchange Server may fail to start and you encounter the below errors in Application Event Log of Exchange Server, while read/writing data from/to EDB file:

“Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 482
User: N/A
Description:
Information Store (4360) First Storage Group: An attempt to write to the file "D:\Program Files\Exchsrvr\mdbdata\res2.log" at offset 4194304 (0x0000000000400000) for 1048576 (0x00100000) bytes failed after 0 seconds with system error 112 (0x00000070): "There is not enough space on the disk.". The write operation will fail with error -1808 (0xfffff8f0). If this error persists then the file may be damaged and may need to be restored from a previous backup.”

You can not access the database after above error. To gain access of your valuable data in the EDB file, you need to identify the root of this issue and perform Microsoft Exchange recovery by resolving it.

Root of the problem:

You may face this behavior of Exchange Server due to any of the below reasons:

1.You do not have sufficient free space on the Exchange Server hard drive. The Error 0x00000070 entails ERROR_DISK_FULL and Error 0xfffff8f0 entails JET_errDiskFull.
2.EDB file is corrupt and Exchange Server can not recognize it.

Resolution:

You can try out any of the below methods to sort out this problem:

1.If problem is caused by low disk space, remove some files to free up disk space.
2.If database corruption is causing the issue, repair and restore the database using powerful and advanced commercial Exchange recovery software.

The Exchange recovery tool carry out in-depth scan of entire Exchange Server database and extract all inaccessible data from it. You need not to be technically sound to use these tools and repair the database as they have interactive graphical user interface.

Stellar Phoenix Exchange Mailbox Recovery is the most powerful, yet easy to use Exchange Database Recovery application to ensure easy recovery in all EDB corruption scenarios. The Exchange 2007 recovery software works well with Microsoft Exchange Server .

Exchange Server Database Fragmentation Fails with Misleading Errors

Microsoft Exchange Server database consists of two common databases, known as Priv.edb and Priv.stm. These database contains all your significant emails, notes, contacts, tasks, journal, attachments and more. If the Exchange Server database come across any sort of database inconsistency and integrity problem, Eseutil.exe utility can help you to fix the problem. It can also be used to repair the damaged database and defragment it. However, in some cases, this utility can not perform the expected tasks successfully and database remains in inaccessible state. In such cases, you are required to carry out Exchange Recovery to work around the problem.

When you attempt to manually defragment the STM (streaming) file of Exchange Server database, you might encounter the below error message:

“Operation terminated with error -2231 (JET_errSLVStreamingFileInUse, The specified streaming file is currently in use) after 0.891 seconds.”

After the above error, when you check the integrity of STM file, you might encounter the below possibly misleading error:

“Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 0.901 seconds.”

You are highly recommended not to use Exchange Server database repair utility against problem STM file as it might damage the internal structure of STM database file. At the same time, you may receive further error message stating:

“Operation terminated with error -1601 (JET_errRecordNotFound, The key was not found) after 2.354 seconds.”

What Causes Fragmentation Errors in Exchange Server ?

The above problem may occur if any of the below conditions are true:

1. This behavior occurs because the version of Eseutil utility doesn't ensure that you're running the tool against correct Exchange Server database. Structure of STM file is different from structure of EDB file. Some Eseutil functions might damaged STM file.

2. The Exchange Server database is corrupt and Exchange Server can not read it.

Solution

Go through the below steps to fix this problem and perform Microsoft Exchange recovery:

1. Obtain latest service pack of Exchange Server.

2. Use third-party Exchange Recovery software to repair and restore the damaged Exchange Server database.

The Exchange Server Recovery applications are capable of handling all types of Exchange Server corruption scenarios, using advanced scanning techniques. The software preserve absolute integrity of your database as of their read-only and non-destructive conduct.

Stellar Phoenix Exchange Mailbox Recovery tool is a powerful, yet easy to use application that effectively handles all EDB corruption problems. This Exchange Recovery Tool works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all inaccessible objects of Exchange Server database, including emails, contacts, notes, tasks, journal, and more.