Microsoft Exchange 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

Exchange Server public information store database contains all the user mailboxes, apart from the information which is required in Exchange Server environment and thus is considered the most important. However, Information Store also comprises one another database called Public information store database (Public.edb), which manages data in public folders. If a logical crash occurs to the Exchange Server, the database corruption may occur and it will require Exchange Server Repair.

In some of the cases, user may fail to mount the information store database and encounter an event in the application log of Event Viewer:

“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 problem is specifically encountered when user upgrades to Exchange Server SP3 or later. It takes place when the information store database has been compressed using NTFS file system compression (Compressed NTFS- generally used to save disk space).
Note: NTFS compression can corrupt Exchange database under critical situations like when the information store reaches to about 4 GB in size, in which Exchange Server Recovery is required.
Exchange Server SP3 and later versions, including Exchange Server 2003 don’t allow NTFS compressed information store to mount. These files are managed by ESE (Extensible Storage Engine) which require sector independence for log-based recovery process, which is not allowed in compressed files. Thus database corruption may result, specifically in database files, larger than 128 MB, which require Exchange Server Repair. Files, smaller than 128 MB, are automatically decompressed in Exchange Server SP3 and later.
In order to resolve the above issue, we need to decompress the folders of Information store databases and logs after dismounting the database. Then, we need to carry out offline defragmentation using ‘eseutil /d’ command and mount the database again. If the database comes out to be corrupt, we need to apply Exchange Server Repair or else perform the online backup of the database.
Exchange Server Recovery can be performed using eseutil utility, but the corrupt pages will be deleted. So, using commercial exchange server repair software can provide complete solutions by utilizing efficient yet safe scanning algorithms to repair the corrupt database.
Stellar Phoenix Mailbox exchange recovery is the finest Exchange Sever Recovery software. It is compatible with Exchange Server 2003, 2000 and 5.5. This Exchange Server Repair software is a user friendly application and has an interactive interface. It recovers mailboxes in PST format, usable with MS Outlook.

Creating backup of Exchange Server database is a very common practice for database administrators. It helps them in restoring the database if any kind of data loss, corruption or other errors occur. But sometimes, after restoring your database from backup, you may find it difficult to access data from it.
One such scenario occurs when you try to start directory server in Exchange Server after restoring from backup. When you try to do this, you may encounter the following error message:
“Error 1067. The process terminated unexpectedly.”
Along with this error message, the following event entries might appear in the Application Even Log:
Event ID: 124
Source: ESE97
Description: MSExchangeDS ((1432 ) ) Unable to read the log header.
Error -530.
Event ID: 1196
Source: MSExchangeDS
Description: Couldn’t recover the restored Microsoft Exchange Server
database (EDB). Cannot continue. Error c8000212.
After this error message, you can not access anything from your Exchange Server database and may fall in need of Exchange Server recovery.
Reason of this issue
This problem generally occurs when Edb.log file, which is created while performing restoration from backup, interfaces with recovery process. It occurs on recovery server.
Due to this problem, the recovery process could not be completed successfully and you might face this behavior of Exchange Server. It cause complete inaccessibility of Exchange Server database.
Work around
To fix this problem, manually delete the existing data from the Dsadata folder before starting restore operation from the backup. It will delete Edb.log file.
Though, it could fix the issue, but it is not a safe method. Deleting Edb.log file might introduce severe errors in the Exchange Server database and may corrupt it.
EDB corruption is the worst scenario for a database user and it might put him/her in need of exchange server repair. Exchange Server repair can easily be carried out using Exchange Server recovery software.
Stellar Phoenix Mailbox Exchange Recovery software is the best ever made Exchange Server repair software to work around all the corruption issues. Using this Exchange Server recovery software, you can perform easy, quick and absolute Exchange Server repair. Phoenix Exchange Server Repair is applicable to all the Exchange Server file versions.

MTA or Message Transfer Agent is the e-mail dealing system in Exchange environment. This sends, receives and delivers mails between servers. Also, this proves valuable for addressing and routing information. But, in few of the cases, the service may fail to start with the following error message:

“Could not start the Microsoft Exchange Message Transfer Agent service on \\ServerName. Error 2140: An internal Windows NT error occurred.”

Network administrator is experiencing problems with MTA and so, as recommended, if you run MTACHECK to know if the MTA is corrupted or got crashed, another error message may flash out, stating:

“Database contains serious errors and cannot be automatically repaired.”

The application event log is also helpful in getting the descriptive information about the Exchange Server problem. So here you get Event IDs like 2127, 2152, 2155, 2219 and 2187, which directly or indirectly points towards Exchange database corruption as of the Exchange server recovery failure, object accessing errors, failure in reading database and so on.

Exchange database is corrupt and hence is inaccessible. However, you can try out the registry editing way and then specify the correct path to the MTA database files. So locate the following registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeMTA\Parameters\MTA Database Path

Type the correct path to MTA database files in Value data box by double clicking the entry. Verify the correct location for the MTA Run directory by locating and

double clicking the following registry.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeMTA\Parameters\MTA Run Directory

If you still don’t find Exchange database accessible, this is a sure corruption case which needs correct scanning and hence Exchange server repair to cure. EDB repair is the process, applicable through third party software which have the read-only conduct, interactive interface and great EDB recovery abilities to help the users.

Be sure to have Exchange server recovery through the trusted and reputed source as an insufficient one will bring damages to the database.

Stellar Phoenix Mailbox Exchange Recovery is the most powerful utility to scan and repair the corrupted Exchange database with the efficient scanning EDB repair algorithms. Easy to use and safe to repair, this Exchange server repair application is found to be compatible with Exchange server 5.5, 2000 and 2003.

This EDB repair tool is meant for all the database objects including e-mails, notes, journal, tasks, appointments and others.