EDB Recovery Tool

Stellar Information Systems Ltd,<01-09-10>Gurgaon, a leading name in data recovery industry, today declares the launch of Stellar Phoenix Mailbox Exchange Recovery 4.0, a more robust software which repairs corrupt EDB files of Microsoft Exchange Server 2010 in addition to 5.5, 2000, 2003 and 2007 versions.

Developed specifically to address the needs of affected MS Exchange Server administrators, this powerful Exchange recovery application offers to repair corrupt or inaccessible mailboxes and recovers them as individual PSTs. The newly-revived software now incorporates the capability of recovering selective mailboxes.

MS Exchange Server administrators can bank upon this application to derive accurate results in all failure scenarios including corrupt database header, improper database backups, hardware issues, dirty shutdown and others. The free Demo version of the EDB recovery software now has the provision of providing preview of the recoverable mailboxes.

“Version 4.0 of Stellar Phoenix Mailbox Exchange Recovery software comprises unparalleled recovery capabilities with added support for MS Exchange Server 2010. The Mailbox Exchange Recovery upgrade provides tremendous power in the hands of Exchange database administrators with its ability to recover mailboxes in almost all EDB database corruption instances, “ said Sunil Chandna, CEO, Stellar Information Systems Ltd.

“We are sure that the upgrade launch of the EDB recovery software will meet the growing needs and challenges that the MS Exchange database administrators are facing day to day” he concluded.

Key Features Stellar Phoenix MailBox Exchange Recovery 4.0

• Supports Microsoft Exchange 2010, 2007, 2003, 2000 and 5.5
• Repairs and recovers corrupt EDB databases
• Allows selective recovery of mailboxes
• Recovery of Unicode-formatted EDB files also supported
• Recovers deleted mailboxes
• User-friendly and safe application
• Demo version provides preview of mailboxes
• Compatible with Windows 2000/XP/2003/Vista/Windows 7

About Pricing and Availability

Stellar Phoenix Mailbox Exchange Recovery 4.0 is available in three license options including Administrator, Technician and Academic. The Administrator license is available both in CD+Download versions and is priced at $599 plus service and handling charges extra.

About Stellar Information

Stellar Information Systems Limited (established since 1993) is the leading creators and providers of advanced data recovery software and data recovery services for more than 17 years. Holding direct presence in USA, Europe and Asia, Stellar is a name that is trusted for finest solutions to recover lost and inaccessible data.

For more information on the product refer to the official website www.stellarinfo.com and the product micro-site www.ms-exchange-server-recovery.com.

Contact Information :
For more information and product purchase options:
Call : 1-877-778-6083 (TOLL FREE)
Mailto: orders@stellarinfo.com.
Web Address- http://www.stellarinfo.com

Are you facing some sort of problem while trying to access MS Exchange database folder? Such problem can occur if there are some problems with the configuration in Exchange Server settings. You should try to address the settings. If the problem is not resolved, then there is a quite prominent possibility that the EDB (Exchange Database) database file is damaged, which can happen due to various reasons including virus infections, database header corruption, transaction log file corruption, etc. In such cases, appropriate methods should be used to recover corrupt EDB file. If these methods are insufficient, then the use of a third-party EDB recovery software to perform EDB recovery is a must.

Let us discuss a scenario in which you are unable to mount the mailbox database in MS Exchange Server 2010. In such case, the following error message is displayed:

“Failed to mount database ‘Mailbox Database’

Mailbox Database

Error:

Exchange is unable to mount the database that you specified. Specified database: d1cdba46-6f79-46f2-ba14-3ae2fa8aad43; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0×80004005,ec=-2147467259).”

In addition, the following report is logged in the Application event log:

“Event ID 9518

Event Type:     Error

Event Source:  MSExchangeIS

Event Category:         General

Event ID:        9518

Date:   date

Time:   time

User:   N/A

Computer:       ServerName

Description: Error 0×80004005 starting Storage Group /DC=com/DC=example/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=335A1087-5131-4D45-BE3E-3C6C7F76F5EC/CN=Administrative Groups/CN=Exchange Administrative Group (FYDIBOHF23SPDLT)/CN=Servers/CN=ServerName/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.

MDB failed to start.”

Cause:

There could be the following reasons for such erroneous situation:

• The ‘DomainName\Exchange Servers’ group is not assigned the ‘Manage auditing and security log’ user right.
• The EDB database file is damaged.

Resolution:

To overcome the problem, you can perform either of the following methods:

• Run Setup /PrepareAD: You should run the ‘Setup /PrepareAD‘ command using the Exchange Server CD. This command restores the original configuration settings of Exchange Server.
• Add the Exchange Servers group to the “Manage auditing and security log” policy: To do this, you should perform the following steps:

◦         Click Start | Administrative Tools | Domain Controller Security Policy.

◦         Click ‘User Rights Assignment’ in the Default Domain Controller Security Settings Microsoft Management Console (MMC) snap-in.

◦         Double-click ‘Manage auditing and security log’.

◦         Click ‘Add User or Group’ in the ‘Manage auditing and security log Properties’ dialog box.

◦         Enter ‘DomainName\Exchange Servers’ in the ‘User and groups names’ box.

◦         Click OK two times.

◦         Quit Default Domain Controller Security Settings MMC snap-in.

◦         Restart the Microsoft Exchange Information Store service.

If the problem is persisting, then a third-party EDB recovery software is to be used to recover corrupt EDB file. Such EDB recovery tools use fast and sophisticated scanning algorithms to recover EDB file without causing any damage to the original EDB file.

The EDB recovery tool that most of the recovery experts recommend is Stellar Phoenix Exchange Server recovery, which recovers corrupt EDB file created for MS Exchange Server 5.5, 2000, 2003, 2007, and 2010. Well equipped to extract individual PST files for every user mailbox, this EDB recovery software is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Is your Exchange Server Database (EDB) file corrupted due to virus attack or improper system shutdown and various other reasons alike? Are you unable to access the database and your valuable emails, notes, contacts, tasks, and other objects? To extract data in such cases, EDB Recovery becomes need of hour. Microsoft Exchange Server facilitates you two types of recovery- Hard Recovery and Soft Recovery.

You must complete the hard recovery after restoring the database from an online backup. It is primarily a log replay process. In hard recovery, the below operations are performed:

1. Patch information is applied to database during the log file replay.

2. Checkpoint is ignored. The Restore.env file is used in place of checkpoint to consider for which file the recovery needs to be started.

3. If EDB is restored to different file path than from which the file was backed up, the replay process of log file completes successfully, ignoring database paths that are listed in log files.

4. Replay the restored transaction log files from temporary folder designated by administrator prior to restore.

5. Hard recovery process doesn’t fail if other Exchange databases in storage groups are not available.

The database files, which are restored from online backup, are stored to normal paths set for database. The restore process starts by overwriting the existing Exchange Server database files. If you need existing database in future, you should back it up before restoring the database from backup.

You must consider that the restore process may fail due to any reason. Even if existing EDB file cannot be played at the moment, the files are possibly still repairable, and you can salvage the data.

The Corrupt EDB File recovery through hard recovery is possible in the majority of Exchange Server database corruption scenarios. However, you must have complete backup of the database to carry out this task. In case,the backup is either not available or not updated, you need to go for third-party Exchange recovery solutions.

In such situations, EDB Recovery Software come for your rescue. They are particularly designed to carry out in-depth scan of entire Exchange Server database and extract all mailboxes and their objects. The EDB Recovery Tool is totally easy to use with simple and self-explanatory graphical user interface. The applications preserve integrity of your database due to their read-only conduct.

EDB Recovery Software is the most advanced solution tor Recover EDB and handle all types of EDB corruption situations. It works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. The software restores emails, notes, contacts, tasks, calendar entries, appointments, attachments, and other objects.

Are you facing fatal errors while accessing your Microsoft Exchange Server 2007 database? Is your EDB (Exchange Server Database) file is inaccessible? The fatal error in Exchange server aborts the application and thus makes it unusable. This behavior of MS Exchange Server renders all your valuable data inaccessible and cause critical data loss situations. In order to get your precious data recovered in such situations, you need to repair and restore the damaged EDB file, using an EDB Recovery solutions.

As an example, MS Exchange Server 2007 Management Pack for Operations Manager supervises the MS Windows Application Event log on systems, which are running MS Exchange Server 2007 and returns the below event:

“Product Name: Exchange
Product Version: 8.0 (Exchange Server 2007)
Event ID: 17003
Event Source: MSExchangeTransport
Alert Type: Critical Error
Description: A Transport database operation has encountered a fatal error. The database may be corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required.”

After the above error, Microsoft Exchange Server does not let you access your database. At this point, you have to verify the cause of this problem and perform EDB File Recovery by resolving it.

Cause:

The error message below indicates that specified ESE (Extensible Storage Engine) database is damaged. It is preventing MS Exchange Server services from starting.

- ESE, also called JET Blue, is an ISAM (Indexed Sequential Access Method) data storage technology intended by Microsoft. The ESE is particularly used as a key component of the Microsoft Exchange Server and the Active Directory.

How to Fix ESE Corruption:

You can carry out following things to sort out this issue-

1. Delete the defined database and corresponding transaction logs. You must not remove the database if you have significant data in the database.

2. Repair the damaged database using Isinteg.exe tool or restore it from backup.

However, if none of the above methods helps you to work around the problem, EDB Recovery Tool is the only option to go for. They carry out in-depth scan of entire EDB file using high-end scanning techniques and restore all database objects such as emails, notes, contacts, tasks, and more.

The software enable you to recover corrupt EDB file in a quick and easy way as they are incorporated with simple and self-descriptive graphical user interface. The integrity of your database is always preserved by these tools.

EDB Recovery Software is the most preferred recover EDB solution to repair and restore EDB files in all cases of corruption. The EDB Recovery is designed for Microsoft Exchange Server 2007, 2003, 2000, and 5.5.

Know More: How to Recover EDB File?

Exchange Server supports transaction logging and numbers them sequentially. It starts naming them from E nn 00001.log and goes on till E nnffff0.log, where nn represents the storage group number. When all the log files are exhausted, Exchange Server gives ‘JET_errLogSequenceEnd’ error and causes different issues, as discussed below. You need to remove these log files while making sure that the databases are healthy. If not, you should restore them from backup or repair using eseutil utility or a EDB Recovery software

For instance, you might come across these symptoms in a computer running Exchange Server 2000 or 2003:

1. The connected users experience failures when trying to logon to their mailboxes. The databases become inaccessible even when they are mounted. It specifically occurs in Exchange Server 2000 that is not using August 2004 Exchange 2000 Server post-Service Pack 3 update rollup or in original version of Exchange Server 2003. The application log shows event ID 1022.
2. The databases in computer running Exchange Server 2003 SP1 or SP2 or August 2004 Exchange 2000 Server post-Service Pack 3 update rollup get dismounted without displaying any warning. When you try to mount them, it shows an internal processing error and logs event 1159 and 9518 in application log.

Cause

Exchange Server has used all the available transaction log files of storage group.

Solution

To solve the given problem, you need to reset the log sequence by removing all the log files to a different location. But before you do so, you should ensure for databases’ consistency. You should follow these steps:

1. Select the ‘ Don’t mount this store at start-up’ option to make sure that they don’t mount at startup
2. Dismount the database that cannot be dismounted by killing the store
3. Mount the other storage groups by restarting the store
4. Try to repair the problematic storage group databases by running eseutil /r
5. Check for databases’ consistency by running eseutil /mh
6. If they are consistent, move checkpoint and log files to a different location and mount the databases
7. If the databases remain inconsistent, you should delete the damaged databases provided you have a full backup to restore. If not, you can use a powerful Exchange Recovery utility to repair and restore them.

EDB Recovery Software are well-designed and exclusive applications that allow you to extract all user mailboxes from a corrupted Exchange database and restore them safely.

Stellar Phoenix Mailbox Exchange Recovery is an advanced and non-destructive utility that uses powerful scanning algorithms to repair a damaged Exchange Server database. It is compatible with Exchange Server 5.5, 2000 and 2003. It is a safe Recover EDB tools with impressive set of features. The tool extracts user mailboxes in individual .pst file format files.

In Microsoft Outlook, the Delegate access allows you to share Outlook resources, like appointment schedules, for enhanced coordination across various workgroups and throughout the organization. But in some situations, when you try to access the Delegate tab, it can not be accessed and you might come across some error messages. This problem could be due to some issues with Exchange Server mailbox. To handle this situation, you need to repair the Exchange Server database (EDB file) and extract mailboxes from it. For this purpose, you need to go for EDB Recovery solutions.

In a practical scenario, when you attempt to access Delegate tab in Microsoft Outlook email client, you might come across the below given error message:

“The Delegate page is not available. Unable to access Outlook folder.”

At this point, you can not access shared data from Exchange Server and come across data loss situations. At this point, you need to find out the cause of this problem and go for appropriate EDB Repair solution to gain access of your mission critical data.

Cause of this problem

You might encounter this error messages due to corruption to the Exchange Server mailbox. In mix mode organization of Exchange Server, this issue might take place because of an erroneous homeMTA attribute. When the problem is caused by the incorrect homeMTA attribute, you can not add new users from EGAL (Exchange Global Address List) to your personal distribution list.

Furthermore, if you’ve wrong value in Secretary Field, you encounter same error message. For instance, the following profile contains a wrong value for Secretary Attribute:

CN=Username\0ADEL:8e945738-9e88-4dc8-991b-e8ce46799ca5, CN=Deleted Objects, DC=Comatose, DC=com

In above example, Secretary Attribute points a deleted object of domain.

Resolution

If the problem is due to homeMTA attribute, verify it and correct it. However, if mailbox corruption is causing this issue, go for EDB Recovery solutions to repair and restore data from corrupted EDB file.

Recovery is best possible with the help of powerful and effective third party applications, known as EDB Repair software. These tools use adequate algorithms to methodically scan damaged Exchange Server database and retrieve all of its inaccessible objects such as emails, notes, contact, tasks and so forth. With self-descriptive and interactive user interface, these tools are completely easy to use.

Stellar Phoenix Mailbox Exchange Recovery is the most excellent solution to handle majority of EDB corruption circumstances. It works well with Exchange Server 2003, 2000 and 5.5. This software is compatible with Windows 2003, XP and 2000. Due to read-only and non-destructive design, this software is completely safe to use.

FBA (Form Based Authentication) is used as a term of art in context of Web or Internet based network computers and in collaborative messaging environment with Exchange Server. It refers to notion of a user being presented with editable form to fill and submit to log into the Exchange Server account. It is basically employed to enhance the security of sensitive and confidential emails and other personal data. In some situations, FBA may get broken and you can not log into your Exchange Server account. This situation could occur due to Exchange Server database corruption or some issues with the EDB file objects. At this point, you are required to go for EDB Recovery solutions to repair and restore damaged EDB file.

In a practical scenario, when you start Microsoft Exchange Server, everything else works file (such as OWA (Outlook Web Access) with HTTPS redirection, SSL public folder, OMA (Outlook Mobile Access) and RPC (Remote Procedure Call) over HTTPS) but FBA is broken. After changing the IP addresses of any website, things may start active strangely. You can not access anything from the Exchange Server and may face critical situations of data inaccessibility and data loss.

If you restore the default settings to sort out this issue, you might come across the following error message:

“Server object error ‘ASP 0177: 800401f3′
Server.CreateObject Failed
/exchweb/bin/auth/owalogon.asp, line 4
800401f3”

Grounds of the issue

This situation may occur due to the number of reasons, which include the followings:

• Exchange Server database corruption

• Version incompatibility issues after upgrading to later version of Exchange Server

• Missing or damaged Exchange Server objects

In all these cases, the data can not be accessed normally and you need to perform EDB Repair by sorting out this problem.

Resolution

In order to gain access of your critical data in such cases, you are required to repair and restore damaged Exchange Server database. This is best possible with the help of powerful and advanced third party software, known as EDB Recovery applications.

These tools use effective scanning mechanisms to restore all of the EDB file objects including emails, notes, contacts, calendar entries, tasks, journal, personal folders and so forth. With interactive and simple graphical user interface, these tools allow you to perform easy, quick and absolute EDB Repair.

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

Microsoft Exchange Server runs a defragmentation process to rearrange the mailbox store and public folders and stored data more competently, eradicating unused storage space.

You could use Eseutil utility for defragmenting the Exchange Server database. It examines the basic structure of the database and rearranges them. It is required for better performance of the database.

Sometimes when you defragment the database, the process fails half-way though. After the process gets halted, you get a temporary file of Priv1.edb. When you rename this file, it gets disappeared.

In such situations, the Mailbox store gets corrupted and you can not mount it. In this case, when you use the Eseutil /MS (to dump the space usage), the operation gets terminated with the following error message:

“Error -2211 (JET_errSLVHeaderCorrupted, SLV file header contains invalid
information)”

After getting this corruption error message, when you use Eseutil /P to repair the database, you will get the further error message stating:

“Checking database integrity. Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 1.912 seconds.”

This behavior results into the inaccessible Exchange Server database. You can not retrieve even a single bit of data from the database and you may fall in the grave situations of data loss.

Cause

As stated in the above error message, this problem takes place due to damaged Exchange Server database. The database corruption could be the possible result of unexpected system shutdown, virus attack, oversized EDB file and so forth.
It does not matter what the reason of data loss is. The only thing which matter is how to retrieve your precious data? The answer of this question is Exchange Server recovery.

Exchange Server recovery is the process of repairing the damaged database with the help of EDB recovery software and restore it. EDB recovery software are easy to use tools, which help you in all cases of EDB corruption and can recover all of the EDB objects.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced Exchange Server repair software. It supports EDB recovery from Exchange Server 5.5, 2000, and 2003. It systematically scans the entire database and ultimately gives you fruitful results of Exchange Server recovery.

Exchange Server databases have two basic files, EDB and STM. As its supports transaction logging, uncommitted set of transactions are stored in log files. Users’ mail boxes are stored in EDB files. So when Exchange Server database corrupts, EDB Recovery is basically focused for extracting user mailboxes from EDB files. However, one of the symptoms that Exchange database is corrupt is that it will fail to mount. In addition, it will mark an event in application log like:

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

Also, an error message is encountered about internal processing errors. Other than Exchange database corruption, above log may also create while these issues:

• Application log may record this event due to un-removed log files after running eseutil/p repair command on damaged Exchange database
• It may also occur if log file has been deleted by antivirus program. Also if log file is quarantined by such programs, database may fail to mount
• Incorrect usage of eseutil /r three-character logfile base name command may also create the same issue. It particularly happens if logfile base name is incorrectly specified

Solution

• If un-removed log files are the issue after using esuetil/p command, we need to first check database consistency. If it is correct, we can move these log files to some other folder. However if database is reported as damaged, we can try committing all log files to the database. If problem persists, users are required to apply Exchange Server Repair solutions.
• Antivirus program is not recommended to scan Exchange Server directories. So it should be excluded from file level scanning. This can even corrupt the database.
• We need to correctly use eseutil /r command and logfile base name.

Exchange Server Recovery

Third party Exchange Server Repair solutions are applicable if user has no valid backup. EDB Recovery Software can scan damaged Exchange database and extract all user mailboxes.

Stellar Phoenix Mailbox Exchange Recovery is the powerful and complete application to repair damaged Exchange database. The software supports Exchange Server 5.5, 2000 and 2003. It extracts users’ mailboxes and restores them in PST file format. It is a read-only application. It can be used with Windows 2003, XP and 2000.