Microsoft Exchange Recovery Tool

Viruses have become very big threats to our precious and mission critical files, applications, system software and Exchange Server database. In case of Exchange Server database, when the virus infected mail spreads to user’s mailbox, it might damage whole mailbox or sometimes entire Exchange Server Database (EDB file). In these circumstances, all of the valuable data stored in the EDB file becomes inaccessible and results into data loss. At this point, to retrieve your precious and critical data, you need to go for Exchange Recovery solution using appropriate tools.

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.

OWA (Outlook Web Access), also known as EWC (Exchange Web Connect) is a remote webmail service of Microsoft Exchange Server5.0 and older versions. The interface of Outlook Web Access corresponds interface in MS Outlook. In OWA you can access all of your Outlook data from any remote system using web browser without configuring any profile on it. But in some situations, when you attempt to access emails using OWA, the process may not complete due to corruption to the Exchange Server database (EDB file). It results into critical data loss situations and require Exchange Server Recovery to be resolved.

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.

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. 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 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.

After you restore an Exchange Server database from one server to another, you might experience serious issues. When you attempt to mount the database in such situations, “c1041724” error occurs. In such situations, all of the critical data becomes inaccessible and serious data loss situations occur. At this point, you are required to go for Exchange Recovery to repair and restore the damaged database and access data from it.

After replacing the Exchange Server database, when you attempt to mount the newly configured server, you might find the following entries in Application Event Log:

Event Type: Error

Event Source: MSExchangeSA

Event Category: MAPI Session

Event ID: 9175

Date: 7/14/2007

Time: 10:50:04 PM

User: N/A

Computer: EXCHANGE

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

Such behavior of Microsoft Exchange Server renders all of your mission critical data inaccessible and you need to find out the cause of the issue to perform Exchange Repair by sorting it out.

Grounds of the issue

This issue generally occurs due to corruption to the Exchange Server database. Due to corruption, the Exchange Server database becomes inconsistent and thus it can not be mounted.

Resolution

Before mounting the database, check “Do not mount the database” and then attempt to start Information Store Service. Rename the old database folder and then run Eseutil on affected database. Now try to mount the database.

This method works in a number of cases, but sometimes when you try this solution, following error may occur in Event Log:

Event Type: Error

Event Source: ESE

Event Category: Logging/Recovery

Event ID: 619

Date: 7/14/2007

Time: 10:50:23 PM

User: N/A

Computer: EXCHANGE

Description:

Information Store (3552) First Storage Group: Attempted to attach database ‘C: \Program Files\Exchsrvr\mdbdata\pub1.edb’ but it is a database restored from a backup set on which hard recovery was not started or did not complete successfully.

In such cases, the data can not be retrieved and you need to use Exchange Recovery software. These software uses effective scanning mechanisms to retrieve as much data as possible from the affected database. These applications are completely easy and safe to use.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced and easy to use Exchange Recovery tool that handles most of the EDB corruption situations. It works well with Exchange Server 6.0, 5.5, 5.01 and 5.0. This software is compatible with Microsoft Windows 2003, XP and 2000.

In Microsoft Exchange Server, you can perform hard recovery to retrieve missing or inaccessible data. Such recovery is performed after restoration from online backup, in case of serious database corruption. Hard recovery is the process of replaying a log file, which is similar to the soft recovery. In some cases, the hard recovery can not be completed successfully and the database remains inaccessible and unusable. At this point, you need to go for Exchange Server Recovery to get your mission critical and precious data back.

In a practical scenario, when you attempt to carry out the hard recovery of Microsoft Exchange Server, you might come across -1019 error message. After this error message, you may find the following Event IDs in Application Event Log of Microsoft Exchange Server:

Event ID: 0
Source: ESE97
Type: Error
Category: Performance
Description: (252) Unexpected Win32 error: 0×3E6

Event ID: 122
Source: ESE97
Type: Error
Category: Logging/Recovery
Description: (252) Unable to read the log. Error -1022.

Event Id: 0
Source: ESE97
Type: Error
Category: Logging/Recovery
Description: (252) -1019

Such errors and events do not let your completely the recovery process and all of your critical emails, tasks, calendar entries, journal, notes and personal folders become inaccessible. In such cases, you need to find out the cause of this issue and perform Exchange Server Recovery by sorting it out.

Grounds of the issue

These Event IDs and error messages indicate that the database is severely damaged and it can not be restored using hard recovery. After this behavior of Microsoft Exchange Server, the Exchange Server Repair process gets terminated and last transaction log file, which is replayed, is altered and damaged.

How to handle the Exchange Server database corruption?

In order to resolve this issue, you need to first repair and restore the damaged Exchange Server Database (EDB) file. This is best possible with the help of powerful and advanced third party Exchange Server Repair software.

These software are particularly designed to effectively scan the damaged EDB file and retrieve all of its objects. These software come equipped with self-descriptive and interactive graphical user interface that let you carry out easy and quick recovery. With read only and non destructive design, these software are completely safe to use and always perform original recovery.

Stellar Phoenix Mailbox Exchange Recovery is the most excellent solution to handle most of the EDB corruption situations. It works well with Microsoft Exchange Server 2003, 2000 and 5.5. This software is compatible with Microsoft Windows 2003, XP and 2000.

When you start Microsoft Exchange Server database, you might come across Error -1216. This error shows that the Microsoft Exchange Server has concluded that that files in EDB (Exchange Server Database) file’s running set are lost or the files have been reinstated with different versions. In such situations, the EDB file may get damaged and you need to go for Exchange Server Recovery to sort out the issue. Error -1216 may be shown in the following format:

“Error -1216 (JET_errAttachedDatabaseMismatch)”

This error can also be symbolized in the hexadecimal format as ‘0xfffffb40’. When you encounter this error, Microsoft Exchange Server aborts the soft recovery process on EDB file, prior to make some changes in the database that might prevent you to re-integrate the missing database files with data set.

When this error occurs, you should try restoring the missing database files. When such files are not available, use Eseutil tool to override the error and continue with Exchange Server Repair. When this error occurs, you might find the following entries in the application event log of Exchange Server:

“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 0
Date: 4/24/2001
Time: 6:20:18 PM
User: N/A
Computer: EXCHANGE1
Description: Information Store (4312) Database recovery failed with error -1216 because it encountered references to a database, ‘D:\exchsrvr\mdbdata\PRIV2.edb’, which is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed).

The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, please contact PSS for further instructions regarding the steps required in order to allow recovery to proceed without this database.”

This behavior of Exchange Server generally occurs when the assessment of header information in database and log files indicates that the replacement or deletion of some vital files has been done. If you run soft recovery, entire database might get damaged.

No matter what the cause of this issue is, the ultimate result would be the loss of your mission critical data. In such situations, Exchange Server Recovery is required to repair and restore damaged database. This is best possible using powerful and advanced third party tools, known as Exchange Server Repair software.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced and effective tool to retrieve data from damaged Exchange Server. This software can repair and restore EDB files of Exchange Server 2003, 2000 and 5.5. It is compatible with Microsoft Windows 2003, XP and 2000.

Microsoft Exchange Server is an important part of a collaborative and messaging environment. Due to the importance of Exchange Server database and stored data, you should regularly back it up. But in some situations, when you attempt to backup EDB (Exchange Server Database) file, the process gets terminated halfway due to corruption to EDB file. In such cases, you need to first perform Exchange Server Recovery to sort out the issue to gain access of your mission critical data.

Sometimes when you attempt to create backup of Microsoft Exchange Server database, which is damaged and inaccessible, you might come across the below given error message:

“Database or database element is corrupt”

Furthermore, with this error message, you might also get a statement, which states that this file can not be verified. Due to corruption, the Exchange Server can not recognize the database and thus can not access it. At this point, you need to identify the cause of data loss and carry out Exchange Server Repair by sorting it out.

Root of the issue

As stated in the above error message, this situation occurs due to corruption to the EDB file. The corruption could be the possible result to virus infection, accidental system shutdown, application errors, operating system malfunction and other similar reasons.

Resolution

In order to fix this issue, you should go for Eseutil/p utility. This is an inbuilt tool in Microsoft Exchange Server that is used to repair damaged EDB file. This tool scans the damaged database and can repair in a number of cases.

Although, this utility is helpful in resolving this error message, but it also has a downside. It deletes all of the database elements that are not recognized by this tool. This behavior of Eseutil tool cause critical data loss situations and make your data permanently inaccessible. To safely retrieve your critical data, go for advanced and powerful Exchange Server Recovery software.

These software are particularly designed to safely, smoothly and thoroughly scan entire database and retrieve all of the inaccessible database objects. These software use efficient and powerful scanning algorithms to achieve perfect Exchange Server Repair. With interactive and simple graphical user interface, such applications are easy to use and do not require sound and prior technical skills.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced and effective software that can handle all EDB corruption scenarios. It can repair and restore damaged EDB file of Exchange Server 2003, 2000 and 5.5. This software is compatible with Windows 2003, XP and 2000.

Microsoft Exchange Server is the most important application to create a collaborative messaging environment. It stores all of the critical user information in Exchange Server Public Information Store. The Exchange Server database contains a separate mailbox for every user and an exact copy of the mailbox is stored on the user hard drive in the form of OST file. In some cases, the Exchange Server database may get damaged due to virus attack or other similar reasons and you need to opt for Exchange Recovery to sort out this scenario.

Sometimes, when you attempt to mount the Exchange Server database (EDB file), you might come across any of the following events in the Application Event Log of Exchange Server:

Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 505
Description: Information Store (2028) An attempt to open the compressed file “drive:\Exchsrvr\MDBDATA\priv1.edb” for read / write access failed because it could not be converted to a normal file. The open file operation will fail with error -4005 (0xfffff05b). To prevent this error in the future you can manually decompress the file and change the compression state of the containing folder to uncompressed. Writing to this file when it is compressed is not supported.

Or

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description: Error 0xfffff05b starting database “First Storage Group\Mailbox Store (EXCHANGE)” on the Microsoft Exchange Information Store. Failed to attach to Jet DB.

This issue generally occurs when you upgrade to Exchange Server 2000 Service Pack 3 or later and the Information Store database is compressed using NTFS (New Technology File System) file system compression. Under some situations, NTFS compression may damage the Exchange Server database like when the EDB file exceeds 4 GB size. In such cases, Exchange Repair is required to work around the issue.

Exchange Server 2000 Service Pack 3 and later do not allow NTFS compressed information store to mount. The files are managed by Extensible Storage Engine (ESE) that needs sector independence for log-based recovery that is not allowed in compression.

This entire behavior of Exchange Server corrupts the EDB file and you are required to repair and restore is using Exchange Recovery software to access your critical data. These software can recover all of the Exchange Server database objects.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced Exchange Repair software that works in most of EDB corruption cases. It works well with Exchange Server 2003, 2000 and 5.5. This software is compatible with Microsoft Windows 2003, XP and 2000.

MS Exchange Server is a server application which retains users’ data in the form of mailboxes, which all are stored in Mailbox Folder. Mailbox Folder is comprised of two main files: Priv1.edb and Priv1.stm. Priv1.edb is the database file which contains all the e-mail messages, message headers and attachments, whereas, Priv1.stm is a streaming file and contains all the multi-media data. Corruption of EDB creates needs of EDB Repair.

Using Move Mailbox Wizard, MS Exchange Server allows moving mailboxes within any versions of MS Exchange, MS Exchange Server 5.5, 2000 and 2003, under a condition that they should be within same Exchange organization. But, when the user tries to move mailboxes from Exchange Server 5.5 to Exchange Server 2000, the process may fail with the following error message:

Error: Moving messages
CN=TestUser,CN=Users,
DC=Machine,DC=Company,DC=Com:
The MAPI call failed.
MAPI or an unspecified service provider.
ID no: 80004005-0000-00000000

Viewing Application log of Exchange Server 2000 shows that the application is failing to move some of the mailboxes. The problem is associated with few of the mailboxes which contain corrupt messages, stripped or disassociated attachment. In case of corrupt messages in mailboxes, EDB gets corrupt and needs exchange server recovery. When we click the messages of mailboxes, which contain the disassociated or stripped attachments, some error messages are encountered which states that attachment can’t be opened or access is denied.

• In order to resolve this issue, we need to permanently delete the message using SHIFT+DELETE or simply deleting the message and emptying the Deleted Items folder.
• If corruption is high, we need to repair EDB as a whole using Eseutil utility or EDB Repair software. Eseutil deletes the corrupt pages from corrupt database; however, this is safe to use EDB Recovery software which apply safe, yet powerful scanning algorithms to extract lost information from corrupt database.

Stellar Phoenix Mailbox Exchange Recovery is a powerful EDB Repair application which is compatible with Exchange Server 5.5, 2000 and 2003. This EDB Recovery software has interactive interface and restores recovered mailboxes in PST format, usable with MS Outlook. The application can recover all the database objects.