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.

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 .

Resolving Event ID 489 in Exchange Server

Microsoft Exchange Server database file can often develop errors, which it finds unable to remove by normal repair methods. Inability to open a database file is one such error. An Exchange Recovery Tool comes handy when your Exchange database becomes corrupted and you have no backup to restore.

The further discussion depicts a commonly occurring problem when trying to open an Exchange database file. In such situations, you can encounter unexpected error and file open operation might fail. On viewing the application event log, you may observe the below event log:

Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 489
Computer:Computer Name
Description: Process name [process id] file name: An attempt to open the file [path\file name] for read-only access failed with [Error Code and Explanation]. The open file operation will fail with error [Error Code].

Cause and Resolution

The actual cause of event 489 can be determined by the error code ('error_code') displaying at the end of its 'Description' section. Below are the possibly occurring error codes along with their causes and solutions:

Error -1032= ' JET_errFileAccessDenied'= File cannot be accessed

The file is in use by some other process or utility like, a virus checker or a backup program. Another cause can be insufficient permissions on folder containing database files to let the store to function correctly.

Thus, you need to configure the program using the database file to not scan the Exchange Server directories and/or to change the folder permissions to the default ones.

Error -1022='JET_errDiskIO' = Disk I/O error

The requested database page cannot be accessed due to an I/O error. It could be because of disk or controller failure or because the path to check file is incorrect.

You should run chkdsk /f /r command, check valid permissions on Exchsrvr folder, ensure the correct path to check file, and troubleshoot file-level anti-virus software scanning. After this, you need to either restore the database from backup or repair the database using Exchange Recovery Tool- eseutil/p, isinteg -fix, and ExMerge.

Error -1023= 'JET_errInvalidPath' = Invalid file path

Possible causes are changed path to log files or check files before restoring and corrupted check files or temporary files created while a defragmentation or a repair.

Therefore, you need to place back the files to their original locations and remove the corrupted files. To correct database inconsistency, you need to either restore the database from backup or repair the database using eseutil/p, isinteg -fix, and ExMerge tools.

Exchange repair utilities can delete the corrupted pages. For safe repair, use of Exchange Recovery Software is recommended.

Stellar Phoenix Mailbox Exchange Recovery is a reliable utility that is used to repair corrupted Exchange database and restore its mailboxes as *.pst files at a safe location. This Exchange Server Recovery software supports MS Exchange Server 2013, 2010, 2007, 2003, 2000, and 5.5 and can also recover deleted mailboxes.Visit this tool http://exchange.stellarservertools.com/