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.

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 .

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.

Resolving Error 501 in Exchange Server

Exchange Server Information Store databases support transaction logging i.e. before committing any data to the database, it is first written to transaction logs. If your database is ever forced to perform recovery, these transaction logs replay and restore the database to a working state. When an Exchange Server Information Store database corrupts, it marks an event indicating the root cause of the issue.

You can deduce the problem and thus, take corrective measures to solve it. In cases, when no backup is available to replace the damaged database and ESEUTIL utility also fails to repair, you need to use an effective Microsoft Exchange Recovery utility that could repair and restore the damaged database. For an instance, you might receive the below event ID in Application log of Event Viewer: Date: date Source: ESE Time: time Category: Logging/Recovery Type: Error Event ID: 454 User: N/A Computer: Servername Description: Information Store (2184) Database recovery/restore failed with unexpected error -501 Cause Event 454 generally indicates database corruption that occurs while restore or recovery operation. Error -501 corresponds to hexadecimal value 0xFFFFFE0B. It represents JET_errLogFileCorrupt error and shows that the recovery operation has failed because of log file corruption.

Solution You need to solve the given issue by following these steps: Check if all database files are consistent. If they are, you can move all corrupted log files that are contained in Exchsrvr\Mdbdata folder and then try to mount the Information Store If applying the above step doesn't solve the issue as databases are not consistent, you need to restore the corrupted databases from backup. In case, no suitable backup is present, you can execute eseutil /p command to repair the damaged databases If the error stil persists, use a powerful and safe third-party Exchange Recovery Tool to scan and repair the damaged database. Microsoft Exchange Recovery software are non-destructive tools designed with advanced technology to repair the corrupted database.

These tools provide you self-explanatory interface and provide advanced set of features. In addition, you can use these products in any case of logical database corruption. Stellar Phoenix Mailbox Exchange Recovery is a fully-competent Exchange Server Recovery tool to systematically repair damaged Exchange databases created with Exchange Server 5.5, 2000 and 2003. It provides safe Exchange Recovery Tool that extracts all user mailboxes by converting them into Outlook usable .pst files. The tool is capable of recovering all email messages, notes, journals, tasks and other objects.

Logical Corruption and Bad Page Error in Exchange Server Database

Logical corruption in Microsoft Exchange Server database (EDB) is very problematic and quite difficult to identify and repair than physical damage. The administrators and users are generally unaware of logical corruption to EDB file. Microsoft Exchange Server does not include any inbuilt tool to diagnose and warn you about the logical database corruption. There are no specific symptoms to recognize such kind of corruption. In case of logical corruption, entire database becomes inaccessible and you come across critical data loss situations.

 In order to overcome logical database corruption, you are required to go for Exchange Recovery solutions. In a practical scenario, when you attempt to access data from Microsoft Exchange Server, you might find the following entries in Application Event Log: Event ID: 42 Source: EDB Type: Warning Category: General Description: MSExchangeIS ((###)) The database engine found a bad page. The above event shows that the inner structure of the database has got damaged, because the internal references (pointers) are misaligned or corrupted. The Exchange Server might become unusually unresponsive, sluggish or slow. Cause The logical corruption of Exchange Server Database might take place if you replay the wrong transaction log files, after restoring the database.

The logical corruption is indicated by the “bad page link” or JET_errBadPageLink errors. In such cases, you need to go for Exchange Repair to get your valuable data back. Resolution In order to sort out this issue, go through the underwritten steps: 1.Restore Exchange Server database (EDB) from recent backup. It is important that only log file, which are restored from backup get replayed, not any existing log file that might available on Exchange Server hard drive. 2.Use exmerge.exe (Microsoft Exchange Mailbox Merge) tool to export data, then important into new priv.edb file. 3.Use “Move Mailbox” feature in Exchange Administrator program for moving users from damaged Exchange Server to another one. Recreate priv.edb file on original server and then move users back to original server. When all else fails, repair and restore corrupted EDB file with the help of third party Exchange Recovery tools.

 These applications used advanced scanning mechanisms to methodically scan the entire EDB file and extract all of the user mailboxes from it. These programs are very easy to use and allow you to have Do It Yourself Exchange Repair. Stellar Phoenix Mailbox Exchange Recovery is the most advanced and effective solution to retrieve data from EDB files of Exchange Server 2003, 2000 and 5.5. This software is designed to work with Microsoft Windows 2003, XP and 2000. With read-only and non-destructive conduct, this software is completely safe to use. for download free Exchange server Software