How to Resolving Event ID 9175 and 486

When even you try to mount a database on a server that is running EBD, 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 MS Exchange Server computer is not available. Either there are network problems or the Exchange Server computer is down for maintenance. The MAPI provider failed.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 file(E00.log) 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 Resolving?

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.

We provide you an Exchange Recovery extracts inaccessible data from corrupt .edb files and is compatible with Exchange Server 5.5, 2000, 2003, and 2007. This Exchange recovery tool recovers all e-mail messages, notes, journals, tasks, contacts and other components.

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

Are you unable to mount EDB 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 Exchange Server. 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 --> CMD --> enter --> Display Command Prompt window

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 --> CMD --> Open box --> click OK.

2.To check the private information store, enter the following command in the Command Prompt:

                   c:\program files\exchsrvr\bin>eseutil /mh 

                   "drive:\program files\exchsrvr\mdbdata\priv1.edb"

3.To check the public information store, enter the following command in the Command Prompt:

                   c:\program files\exchsrvr\bin>eseutil /mh 

                   "drive:\program files\exchsrvr\mdbdata\pub1.edb"

4.Analyze the consistency check results. If the database is consistent, then all the transaction log files are moved to the information store. 

5.Transfer all the log files from the directories to a backup folder.

6.Try to mount the edb db. It should run fine now.

If unable to mount the database, the only way of resolving this problem is to use a  edb repair software. 

The best Exchange repair software among all the available tools is 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 MS Outlook PST files.