Solving Jet Error - "JET_errRecordNotFound,the key was not found" in Exchange Server

When EDB file get corrupted, you can't mount the Exchange database and also unable to access your emails & other items from Exchange server. These situations may occur due to various reasons like suddenly exiting the Exchange Server,corruption in the database header, virus infections and hardware related issues etc.

Such problems can be handled by using in-built eseutil.exe utility. However when edb file is badly corrupted, you may receive Error "JET_errRecordNotFound". In this case the inbuilt utility may fails to perform the expected tasks which makes the database inaccessible and leads to data loss.

In order to solve this problem you need to install the latest service pack of the MS Exchange server. If it does not resolves the issue then it is necessary to use the third-party Exchange Recovery software such as Stellar Phoenix Mailbox Exchange Recovery tool to repair and restore the damaged exchange database (EDB) files.

Download the most trusted free EDB repair Software for MS Exchange Server 5.5, 2000, 2003, 2007 and 2010 from http://exchange.stellarservertools.com/

Resolving Event ID 9175 and 486

Sometimes when you try to mount a database on a server that is running Microsoft Exchange Server, and instead receive the 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, the following event is logged in the Application log:

Event Type: Error
Event Source: MSExchangeSA
Event Category: (14)
Event ID: 9175
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

or

Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 486
Description: Information Store (3932) First Storage Group: An attempt to move the file “E:\Program Files\Exchsrvr\mdbdata\E00.log” to “E:\Program Files\Exchsrvr\mdbdata\E000080A.log” failed with system error 2 (0×00000002): “The system cannot find the file specified.” The move file operation will fail with error -1811 (0xfffff8ed).

Cause


1. Error 1811 relates to JET_errFileNotFound. This issue may pop up in an Exchange log (E00.log) file that has a mismatching signature and LGeneration. If E00.log file has a mismatching signature, the information store won’t mount even if the databases are consistent.
2. If an anti-virus program quarantines, deletes or interferes the current Exchange log file.

How to Resolve?

To resolve this issue, ensure the anti-virus is not configured to scan the Exchange Server directories. Check the log files of the anti-virus program to verify whether the Exchange log file was quarantined or deleted.

1. If quarantined, recover the Exchange log file by executing the following steps:

a) Recover the Log to folder which contains production files
b) Start MS Exchange Information Store Service. In case other Exchange log files are not missing, the database will mount. In case more log files are found to be missing, check the missing log files in the quarantine folder. If you cannot find the files, follow the next step.

2. If deleted, recover the Exchange log file by following these steps:

a) Move all the inconsistent databases to backup folder
b) In case, new E00.log file is made, move it to the backup folder. Also, move E00.chk and copy the existing files.
c)Rename last E00*.log file as E00.log
d) Restore database from backup.

If you do not have a backup, you must consider using third-party Exchange Server recovery software to bring EDB database files to consistent state.

Stellar Phoenix Mailbox Exchange Recovery extracts inaccessible data from corrupt .edb files and is compatible with Exchange Server 5.5, 2000, 2003, 2007, 2010 and 2013.

Unable to mount MS Exchange Server 2007 database...it could be corrupt

Are you unable to mount EDB (Exchange Database) database file on the MS Exchange Server 2007 system that is being used in your organization? If yes, then there is a very prominent possibility that the EDB file is corrupt thereby disabling you from mounting it. In such cases, you should try to find out the exact cause of corruption and try to eradicate that issue. In case, nothing is succeeding then you should use a professional Exchange repair software to recover the trapped data.
Consider a similar situation in which you are unable to mount the database on MS Exchange Server 2007. The following error message is displayed:

“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, when you check the error log the following event is logged:

“Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 486
Description: Information Store (3932) First Storage Group: An attempt to move the file "E:\Program Files\Exchsrvr\mdbdata\E00.log" to "E:\Program Files\Exchsrvr\mdbdata\E000080A.log" failed with system error 2 (0x00000002): "The system cannot find the file specified." The move file operation will fail with error -1811 (0xfffff8ed).”

Cause:

You may have run the eseutil /p command on the damaged databases. This problem has occurred because the transaction log files were not removed during the process.

Resolution:

First of all, you should check whether eseutil was run on this system at all or not by performing the following steps:
1.Click Start | Run.
2.Enter 'CMD' in the 'Run' box and press 'Enter' key. The Command Prompt window will be displayed.
3.Enter the following command:
4.c:\program files\exchsrvr\bin\eseutil /mh "c:\program files\exchsrvr\mdbdata\name of Exchange database.edb"
5.Check the repair count field. If it is 0, then the eseutil /p command was not run. For a non-zero count, eseutil /p command was run on the database.

Now, you can transfer the transaction log files to another folder if the database is in a clean shutdown state. To check this condition, you should perform the following steps:

1.Click Start | Run and enter 'cmd' in the 'Open' box and click OK.
2.To check the private information store, enter the following command in the Command Prompt:
3.c:\program files\exchsrvr\bin>eseutil /mh "drive:\program files\exchsrvr\mdbdata\priv1.edb"
4.To check the public information store, enter the following command in the Command Prompt:
5.c:\program files\exchsrvr\bin>eseutil /mh "drive:\program files\exchsrvr\mdbdata\pub1.edb"
6.Analyze the consistency check results. If the database is consistent, then all the transaction log files are moved to the information store.
7.Transfer all the log files from the directories to a backup folder.
8.Now try to mount the database. It should run fine now.


In the event of still unable to mount the database, the only way of resolving this problem is to use a third-party MS Exchange repair software. These tools are highly interactive in nature that do not damage the EDB files while scanning them.

The best Exchange repair software among all the available tools is Stellar Phoenix Exchange Server Recovery that repairs corrupted EDB files integrated in MS Exchange Server 5.5, 2000, 2003, and 2007. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this Exchange Server repair tool is able to extract individual user mailbox in the form of separated PST files.

For more visit at: http://www.ms-exchange-server-repair.com/

What to do when you are unable to connect to MS Exchange Server 2003

Are you experiencing problems in connecting to Exchange Server after restoring a mailbox store? If yes, then chances are that mailbox has corrupted due to various reasons such as hardware problems, database header corruption, etc. In such cases, you should adopt appropriate methods to counter the situation. However, if you are not able to fix the problem then you should use a third-party Exchange Server recovery to perform Exchange recovery.
For instance, you are using MS Exchange 2003. In this, you have restored a mailbox store to the recovery server. However, you are unable to connect to it using the ExMerge tool. You see the following error message in the ExMerge event log:

“Error opening message store (EMS). Verify that the Microsoft Exchange Information Store service is running and that you have the correct permissions to log on. - 0x8004011d ( (CmapiSession::GetMailboxesOnServer))”

In addition, the Application log reports the following error signature:

“Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Date: Date
Time: Time
User: N/A
Computer: Server_Name
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”

Cause:

There could be the following reasons for such error:
1. The mailbox store containing the System Attendant mailbox is not mounted.
2. ExMerge is using the System Attendant mailbox to connect to other mailboxes.
3. The Recovery Storage Group (RSG) server is not having a System Attendant mailbox.

Resolution:

To resolve this issue, you should perform either of the following resolutions:

1. Mount the mailbox store containing the System Attendant mailbox: You should mount the mailbox store that contains the System Attendant mailbox on the recovery server. Run ExMerge when complete to extract the data from the user mailboxes.
2. Create a Recovery Storage Group (RSG) and restore a production database: You should create an RSG to recover data from the mailbox store. Restore the extracted mailboxes in a production database using the ExMerge tool.

The problem would be fixed using any of the aforementioned methods. However, if this is not so then you should use a third-party Microsoft Exchange recovery software to recover Exchange database. Such read-only tools are user friendly in nature that do not overwrite the existing database while scanning it.

Stellar Phoenix Mailbox Exchange Recovery is an efficient Exchange recovery software that performs Exchange database recovery for corrupted databases.