While trying to mount a mailbox store or a public folder store in MS Exchange 2000 Server or in MS Exchange Server 2003, you may experience trouble. During the process, you may receive following error message:
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
Additionally, an event that resembles the following event is logged in the Application log:
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Description: Error 0xfffffc01 starting Storage Group /DC=COM/DC=EXAMPLE/CN=CONFIGURATION/CN=SERVICES/CN=MICROSOFT EXCHANGE/CN=FIRST ORGANIZATION/CN=ADMINISTRATIVE GROUPS/CN=FIRST ADMINISTRATIVE GROUP/CN=SERVERS/CN=ServerName/CN=INFORMATIONSTORE/CN=FIRST STORAGE GROUP on the Microsoft Exchange Information Store. Storage Group – Initialization of Jet failed.
You may come across the behavior when an incorrect drive letter is set for the Exchange database files or for the log files. Error code 0xfffffc01 in description indicates that a drive letter has changed for the Exchange database files or for the log files.
Another possible option that might be triggering this problem could be antivirus software, that may be blocking write access to the drives that contain the Exchange database or the transaction log files. In order to find out if your Antivirus software is causing this problem, disable the antivirus software temporarily in the Services console. Now, you try to mount the affected databases. If you succeed, means you need to replace or fix antivirus software.
If you determine that the error has occurred because of an incorrect drive letter is set for the Exchange database files or for the log files, you need to verify the database path and the log file path by using Exchange System Manager. Follow below given steps:
- Start Exchange System Manager, click Start -> Programs -> Microsoft Exchange-> System Manager.
- If administrative groups are displayed in Exchange System Manager, expand Administrative Groups, and then expand the administrative group in which you experience the problem
- Expand Servers, and then expand the server on which you experience the problem.
- Right-click the storage group that contains the store that you cannot mount, and then click Properties.
- On the General tab, examine the path that appears in the Transaction log location box. Then, examine the path that appears in the System path location box.
If these paths are incorrect, click Browse to locate the folder that contains the transaction log files or the database files. By default, the transaction log files and the database files are located in the following folder:
- Click OK.
- Follow steps 3 through 5 for each storage group that may be present to verify the database path and the transaction log file path.
- After you verify the database path and the transaction log file path for each storage group, verify the database paths for each store in each storage group. Mount the mailbox store or the public folder store.
If you want easy and hassles free option you can opt for the Exchange Server Recovery. With exceptionally powerful features, this performs accurate and successful Exchange recovery. This tool to repair Exchange 2007 mailbox, efficiently resolves Exchange dirty shutdown situations and meets Exchange clean shutdown state. In short, the Exchange Server Recovery is an ultimate tool to repair Exchange Server. Get more detail,Click here:- http://www.edb2pst.net/
Why We Need to Migrate EDB to Office 365?
Convert EDB Files to PST Files to Deal Corruption Due to Exchange Server Jet Error 1216
7 Much-Talked About Features in Exchange Server 2016
Eseutil and Isinteg alternative EDB to PST Converter
Conduct a Simple EDB2PST Conversion and Deal With all EDB File Errors Effectively