How to rectify Error c1041724 in MS Exchange Server 2000

Are you facing problems in accessing mailbox folders in MS Exchange Server 2000? Usually, such things happen when some internal settings for the mailbox store are not correctly set. Also, it may also be possible that the mailbox folder itself has got corrupted. Such corruption can occur due to various reasons such as abrupt or improper system shutdown, database header corruption, corruption of transaction log files, etc. In such cases, you should try to resolve the issue using appropriate corrective measures. In you are not able sort the issue, then you should use a third-party Exchange Recovery software to repair MS Exchange Server mailbox store.

Consider a scenario wherein you are unable to mount an MS Exchange Server 2000 mailbox store using Microsoft Exchange System Manager. 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”

In addition, either or all of the following event IDs will be logged in the Application event log as well:

1. Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Description:
The MAPI call 'OpenMsgStore' failed with the following error: The attempt to log on to the Microsoft Exchange Server computer has failed. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0512-00000000

2. Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9546
Description:
Failed to create the Event Registration Mailbox for Database First Storage Group\Private Information Store (servername). Error – 0xbf69.

3. Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description:
Error 0x80004005 starting database "First Storage Group\Private Information Store (servername)" on the Microsoft Exchange Information Store.


Cause:

The root cause of this problem is that the System mailbox object exists in the System Objects container, which is created for this mailbox store. And when you try to mount it, Exchange Server creates another object for the same, which is causing the problem.

Resolution:

To resolve this issue, you should perform the following steps:

1.Start the Active Directory Users and Computers snap-in.
2.Click the Advanced Features option in the View menu.
3.Find the Microsoft Exchange System Objects container, and then look for the System mailbox object whose mailbox store you were trying to mount.
4.Delete the System mailbox. Now try to mount the mailbox store. It should run fine now.

However, there are few instances when the problem is not resolved using these steps. In such cases, you should use a third-party Microsoft Exchange Recovery software. Such read-only tools are highly interactive and user friendly in nature that ensure safe and secure Exchange Server recovery.

Stellar Phoenix Mailbox Exchange Recovery software is an Exchange recovery software that repairs corrupted Exchange mailboxes created in MS Exchange Server.

Information Store Corruption due to RAID Issues

One of the common reasons for Exchange Information Store to get corrupt is hardware issues. Thus when you identify server consolidation for Exchange Server computer, experts suggest you to adhere to Windows Server Catalog tips. The most important is a reliable storage subsystem and that's the reason you are often recommended to use Redundant Array of independent Disk (RAID) configuration. This not only increases performance by allowing multiple I/O operations but also adds to reliability. But unfortunately there can still be instances that may bring corruption to message store. If one or more of RAID components fail, the Exchange Information Store can catch corruption. In such situation, you need an Exchange Recovery solution to repair the database and recover the lost data.

Consider you use a RAID 2 system to run Exchange Server. All the Information store data including the log files are stored on the same drive. You observe that one of the RAID drives shows typical corruption issues. So you replace the drive, but you experience similar kind of problems with other drives as well.

Later, you notice that you cannot mount the Information Store. When you run eseutil /mh command to check the integrity of the database, it shows that Information store is corrupted. The database files and log files (typically, e00.log file) are damaged.

Cause

Since disk issues are repeatedly observed, it indicates issues with the RAID controller that has ultimately corrupted the Information Store database files.

Solution

You need the following solutions to deal with such problems:

1. Run eseutil /p command to repair the corrupted database. Keep in mind that this can delete the corrupted pages, so to prevent against critical data loss, it is recommended to use the command on a database backup.
2. Restore from a valid backup. But it is likely that database backup may also not exist in usable state. The reason is that the corruption problems have been continuous for considerable time and it is possible that you might have backed up the corrupted Information Store.
   
3. Use a third-party Exchange Recovery utility. The Exchange Server Recovery software can scan and then repair the corrupted Exchange database using powerful, yet safe, algorithms.

Exchange Server Recovery Software is a reliable tool that repairs corrupted Exchange database and extracts mailboxes as *.pst files while keeping the original database unaffected. The Exchange Recovery Tool supports MS Exchange Server 2007, 2003, 2000, and 5.5. The tool can also recover deleted mailboxes.