Microsoft Exchange Server offers multilingual environment support to its users. You can easily access of your emails, contacts, tasks and other items in any language, which is included in its database. Every language in Microsoft Exchange Server has a unique Locale ID (LCID). This is quite helpful feature to provide access of Exchange Server in native language. But in some situations, this might might prove harmful and cause database index corruption. The situation might occur due to a number of reasons and eventually cause critical database corruption and data loss situations. Such cases require Exchange Server Recovery to be sorted out.

In a practical scenario of index and Exchange Server database corruption, when you move the Exchange Server 2000 database to a server, which does not have same LCID and then you attempt to defragment the database, index corruption is reported. However, when load correct Local ID on new server and then attempt to defragment Exchange Server database, it doesn’t corruption the index corruption.

• The LCID is a 32-bit value, which is defined by Microsoft Windows operation system that has a sort ID, language ID and reserved bits to identify the particular language. For instance, the Locate ID for English is 1033.

In these situations of index corruption, you can not access data from the Exchange Server database as the database become inaccessible or corrupt. Thus, it becomes essential to find out the cause of this issue and go for Microsoft Exchange Recovery by resolving it.

Grounds of the issue

When you move the database between computers where LCID is different, there is possibility of silent index corruption. For instance:

1. If an LCID, which is reinstalled that was previously uninstalled (or vice versa), there is the possibility of index corruption.

2. When you backup and restore database, which is generated by the computer that has LCID installed to a system without LCID installed, you might come across index corruption.

3. If you copy a database to another computer, defragment it and then copy back to original system, silent index corruption occurs.

Resolution

In order to retrieve data from damaged Exchange Server database, go for Exchange Server Recovery using third party applications. These tools use high-end scanning techniques to methodically scan the affected database and retrieve data from it. The Exchange Server Repair applications are complete safe and easy to use.

Stellar Phoenix Mailbox Exchange Recovery is the best ever made and the most advanced Exchange Server Software to ensure absolute recovery. It works well with Microsoft Exchange Server 2003, 2000 and 5.5. This software is compatible with Microsoft Windows 2003, XP and 2000.

The recovery process in such cases may include deletion of the emails from all the mailboxes on Exchange Server. For this purpose, you could use ExMerge.exe (Exchange Mailbox Merge) application that is included Exchange Server CD.

The exchange Server database administrators generally use ExMerge.exe utility for backing up the mailbox data or to migrate the mailbox from one mailbox to another. The ExMerge tool is designed for copying mailbox data in the PST (Personal Storage File), which you can import to another mailbox. The ExMerge can also be used to extract particular messages from the mailbox store to the PST file and then remove PST files instead of importing the file in new mailbox store.

You can extract data from virus-infected Exchange Server mailbox using the ExMerge tool and carry out Exchange Repair by following the underwritten steps:

1. Setup ExMerge tool and start ExMerge wizard.

2. On Procedure Selection page, select Extract or Import and click Next.

3. On Two Step Procedure page, select Step 1 and Next.

4. On Source Server page, select Options and then User messages and folders on Data tab in Data Selection Criteria page.

5. In backs up the emails in the form of PST file and allow you to easily import them to mailboxes.

Although, this method works in a number of situations, but can not help you to retrieve data from damaged EDB file in all situations of corruption. In such cases, you need to use advanced and powerful third party Exchange Server Recovery applications to effective repair and restore corrupt EDB file and extract all of the data from it.

These applications use efficient scanning mechanisms to thoroughly scan whole database and retrieve as much data as possible from it. These tools come equipped with interactive and simple graphical user interface and thus let you carry out Exchange Server Recovery on your own.

Stellar Phoenix Mailbox Exchange Recovery is the most effective and successful Exchange Server Recovery tool to easily handle most of the EDB corruption scenarios with Microsoft Exchange Server 2003, 2000 and 5.5. This software is designed for Microsoft Windows 2003, XP and 2000.

In a practical scenario, when you attempt to access data from Exchange Server either using OWA or Microsoft Outlook, you might come across the below given error message:
“HTTP 500 – Internal Server error.”

At the same time, the following Event is logged into the Application Even Log of Microsoft Exchange Server:
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: General
Event ID: 2050
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description: Process Process_Name (PID=Process_ID). The shared memory heap could not be created.
After this behavior of Microsoft Exchange Server, the entire database become inaccessible and you come across critical dataloss situations. In such cases, you need to find out the cause of this issue and carry out Exchange Server Repair by sorting out this issue.

Root of the issue

You might come across this problem when the ExchangeApplicationPool property has wrong values or Exchange Server Virtual Directory is not running in correct identity.

Resolution

In order to sort out this issue, you need to ensure that the Exchange, the Exadmin, the Exchweb\Bin, the Exchweb, the Exchweb\Bin\Auth, the Public Virtual Directories, and the Microsoft Server ActiveSync are running in Microsoft Exchange Application Pool and not in the Default Application Pool. In case of corruption to the Exchange Server Database, you are required to carry out Exchange Server Recovery.

This is best possible with the help of third party applications. These tools are capable of scanning damaged EDB file and extracting all of its objects. They use advanced scanning algorithms to achieve absolute and quick Exchange Server Repair.

With self-descriptive and interactive user interface, these programs are quite easy to use and thus do not demand sound and prior technical skills.

Stellar Phoenix Mailbox Exchange Recovery is the most effective Microsoft Exchange Recovery solution to easily handle most of the EDB corruption scenarios. It works well with Microsoft Exchange Server 2003, 2000 and 5.5. This software is designed for Microsoft Windows 2003, XP and 2000. With read-only conduct, it always performs safe recovery.

The command line format of Esefile tool is as follows:

Esefile [/c source destination] [/x file] [/s file] [/d file page number]

/c Copy source files to destination
/x Test Edb.dll format checksum
/s Test Ese.dll format checksum
/d Dumps a page from file

When you test checksum using this tool, it verifies page-level integrity of the database. It tests at speed of about 1 GB per minute.

In case if you use /s switch on EDB format database and /x switch on ESE format database by mistake, checksum error is logged on every page. The utility may report that the database has incorrect checksum and possibly the database corruption may occur.

After testing checksum using incorrect switches with Esefile utility, when you attempt to start Information Store of Microsoft Exchange Server, it might not start and the following error messages is logged in Application Event Log:

Event ID 5000 Source MSExchangeIS
Unable to initialize the Microsoft Exchange Information Store service.
Error Non-database files or corrupted database.

At this point, you are required to resolve the database corruption as quickly as possible by carrying out Exchange Repair.

How to fix checksum errors in Exchange Server?

In order to sort out the above error and gain access of your database, you need to repair and restore the damaged database. This is best possible with the help of powerful and advanced Exchange Recovery software.

These programs are particularly designed to systematically scan entire Exchange Server database, repair and restore it. Advanced and effective scanning methods are used by these Exchange Recovery applications to achieve absolute recovery. With interactive and simple graphical user interface, these tools are completely easy to use.

Stellar Phoenix Mailbox Exchange Recovery is the most excellent solution to effectively handle EDB file corruption situations. It is designed for Microsoft Windows 2003, XP and 2000. This Exchange Server Recovery Software repairs and restores EDB file of Exchange Server 2003, 2000 and 5.5. This is a non-destructive recovery tool.