EDB Corruption Due To Use Of Improper Esefile Switches Article

	1888 Articles Home \| Computer Articles \| Data Recovery Articles \| Windows Articles	Data Recovery RSS
EDB Corruption Due to Use of Improper Esefile Switches

In Microsoft Exchange Server, the Esefile is an inbuilt utility that is used to copy files and test checksum. Different switches are used to perform specific task using this tool. This utility can be used on Microsoft Exchange Server 2000 and 5.5.

Author: Bob Luis

Article Tools:

In some situations, this utility may cause checksum errors and database corruption if you use incorrect switches. In such cases, all of your critical data becomes inaccessible and serious data loss situations occur. At this point, to retrieve your valuable data, you are required to opt for Exchange Server 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 Server Repair 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 software repairs and restores EDB file of Exchange Server 2003, 2000 and 5.5. This is a non-destructive recovery tool.

About Author

Bob Luis has passion for writing Technical article. He is right now writing articles related to Product like Microsoft Exchange Server Recovery and Exchange Server Recovery.

For more information, visit: http://www.ms-exchange-server-recovery.com

Article Source: http://www.1888articles.com/author-bob-luis-22336.html

EDB Corruption Due to Use of Improper Esefile Switches