After you restore an Exchange Server database from one server to another, you might experience serious issues. When you attempt to mount the database in such situations, “c1041724” error occurs. In such situations, all of the critical data becomes inaccessible and serious data loss situations occur. At this point, you are required to go for Exchange Recovery to repair and restore the damaged database and access data from it.
After replacing the Exchange Server database, when you attempt to mount the newly configured server, you might find the following entries in Application Event Log:
Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Date: 7/14/2007
Time: 10:50:04 PM
User: N/A
Computer: EXCHANGE
Description:
The MAPI call ‘OpenMsgStore’ failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000
Such behavior of Microsoft Exchange Server renders all of your mission critical data inaccessible and you need to find out the cause of the issue to perform Exchange Repair by sorting it out.
Grounds of the issue
This issue generally occurs due to corruption to the Exchange Server database. Due to corruption, the Exchange Server database becomes inconsistent and thus it can not be mounted.
Resolution
Before mounting the database, check “Do not mount the database” and then attempt to start Information Store Service. Rename the old database folder and then run Eseutil on affected database. Now try to mount the database.
This method works in a number of cases, but sometimes when you try this solution, following error may occur in Event Log:
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 619
Date: 7/14/2007
Time: 10:50:23 PM
User: N/A
Computer: EXCHANGE
Description:
Information Store (3552) First Storage Group: Attempted to attach database ‘C: \Program Files\Exchsrvr\mdbdata\pub1.edb’ but it is a database restored from a backup set on which hard recovery was not started or did not complete successfully.
In such cases, the data can not be retrieved and you need to use Exchange Recovery software. These software uses effective scanning mechanisms to retrieve as much data as possible from the affected database. These applications are completely easy and safe to use.
Stellar Phoenix Mailbox Exchange Recovery is the most advanced and easy to use Exchange Recovery tool that handles most of the EDB corruption situations. It works well with Exchange Server 6.0, 5.5, 5.01 and 5.0. This software is compatible with Microsoft Windows 2003, XP and 2000.
