'Exchange Server Recovery | PST Recovery' Blog RSS Feed

EDB to PST Converter to access all the data in PST format

culveraxel — Sun, 27 Mar 2011 23:49:03 -0800

Exchange Database files (EDB) file on Exchange server act as repository of user information. For every user there is a corresponding mailbox on Exchange server which stores their respective data. An email client application like MS Outlook is needed to access that data. But, considering corruption probabilities; EDB file is too prone to corruption situations. There are two situation when you need to convert EDB to PST file i.e Either file is extensively corrupted or you want to convert working/partially corrupted EDB to PST file based on your requirements.

Although Microsoft provide utilities such as Exmerge.exe or Eseutil.exe, which are used in the majority of situations when you experience issues with your Exchange Information Store. Both the utilities are used to verify and then repairing your Exchange Information Store database files. But these utilities do not resolve the problems when file is seriously corrupted. In such case a third-party utility helps you to repair and recover your precious data. By following few simple steps you will have your workable PST file while keeping the original file intact.

There are various situations when your EDB file gets corrupted and you may loss all the data. Some of the situations include:

1.Virus Attack
2.EDB file approaching its size limit of 16 GB.
3.Corruption in Exchange transaction log files.
4.Hardware or Software Failure
5.Server Failure or Crash
6.File Header Corruption
7.Dirty Shutdown
8.During upgrading process
9.Logical corruption of Exchange Database
10.Accidental deletion of User Mailbox

When you face situations like mentioned above, you are left with inaccessible data. You won’t be able to access important file items like emails, contacts, drafts, meeting schedule etc. One possible way to access all the data is to convert EDB to PST file using some powerful software. The conversion process of the software should be very simple and should have interactive user interface so that even novice user can easily convert EDB to PST file.

Stellar Phoenix EDB to PST tool uses powerful scanning algorithm to scans the EDB file. This EDB to PST tool will successfully convert all your inaccessible .edb file items into .pst file format. The recovered data need to be import in MS Outlook. The EDB PST converter software is compatible with MS Exchange Server 2010, 2007, 2003, 2000 and 5.5

Steps to convert EDB to PST:

1.Download and install the EDB to PST converter software.
2.Browse and select the EDB file to be converted.
3.Browse and select the EDB file to be converted.
4.Select the type of Server for selected EDB file
5.Click 'Start' to scan the damaged EDB file.
6.Select all the mailboxes or particular mailbox to save at desired location
7.The "Mailbox Recovered Successfully" message box ensures successful EDB to PST conversion.

The free demo version of the EDB to PST Conversion tool allows you to extract the data from corrupted, damaged, inaccessible or working EDB files. However, like other third party tools, it also restricts you from saving the extracted user data. In order to save the complete user data, you need to get the full version of the software.

Improve performance of Entourage Database by Entourage repair products

culveraxel — Thu, 17 Mar 2011 04:46:22 -0800

It often happens, that if by any reason corruption occurs in Entourage, you simply refuse to use it as your e-mail client. Well, it is quite a bad humor. It is a true fact that when corruption ruins any software application, whether it may be your e-mail client, such as Entourage, Outlook Express or some other. Data that resides in it becomes totally unapproachable. By the loss of data, a do-or-die situation arises for you. But there is no need to give up hope. You can rush for a commercial Entourage database repair software for performing successful Entourage repair.

Let's consider a practical example. Suppose, you make an attempt to receive e-mail messages in Microsoft Entourage for Mac. Entourage fails to receive it, additionally it throws an error message that looks same as written below:

“Mail could not be received on account account_name. The domain name servers are not responding.”

Data of Entourage application becomes inaccessible. Entourage cannot be accessed.

Cause:

Above problem occurs when any of the following conditions become true:
1. Down or non-operational e-mail server on your Internet Service Provider (ISP).
2. Incorrect information of e-mail account.
3. Corrupt Entourage identity.

Solution:

For solving above behavior, and to perform Entourage repair. You have to do the following measures:

1. If the error is due to down or non-operational e-mail server and incorrect e-mail account information, then contact ISP. Your ISP will update you about the status of operational e-mail server and about correct e-mail account settings. If the ISP is not operational, then only ISP will inform you when e-mail server will be operational again. It will also tell you about correct e-mail account settings.
2. If the Entourage identity is corrupt, then you have to replaced with a new identity file or repaired it.

Moreover, you can also use an inbuilt database utility. But inbuilt utility is not beneficial in the case, if the database is badly damaged. For such cases, a third party Microsoft Entourage repair software can be used. Such software are simple and easy to handle. Once you use these software to rebuild entourage database, You will not again go for any other method, even you will not think. Such software are developed by a team of experts.

Stellar Phoenix Entourage Repair tool is a versatile software that can be relied for getting satisfactory results. Recovered data is stored in a new RGE file. It is capable to repair Entourage files from any kind of logical corruption. The tool is compatible with operating systems, such Mac OS X 10.6 Snow Leopard, 10.5 Leopard, and 10.4 Tiger. For additional information, you can go through a demo version of the software.

How to solve Entourage Error Corruption Opening Database [-39""] ?

culveraxel — Thu, 24 Feb 2011 23:55:00 -0800

Corruption is a major problem in Mac entourage database. Mac Entourage e-mail application cannot recognize the corrupt database. In such cases of corruption or any damage, you will not be able to retrieve the important data and it becomes unusable. To overcome such situation, Microsoft has provided an entourage rebuilding utility that you can use to perform Entourage repair. It might be possible that this database utility remains unable to repair corrupt entourage database file. Another option you have is to use third-party Entourage repair tool to solve the database issues.

Assume a practical situation in which you are using Microsoft Entourage and you are unable to access your data as the following error message is displayed:

“ERROR: Failed to open database [Head] ERROR: Corruption opening database [16003:””]”

The above error indicates that your entourage database is severely damaged. When you try to solve the issue by rebuilding it using inbuilt Database Utility, the process may fails and generate the following error message:

“Error Corruption Opening Database [-39””]

It is highly recommended to immediately stop accessing Entourage data, once you come to know about the corruption situation. It helps you to avoid any further damage and ensure high success rate of Entourage database repair utilities.

Cause:

This problem may occur due to damaged Entourage Identity database file.

Solution:

Try out the below mentioned tricks to sort out this corruption issue with Microsoft Entourage:

i) Run database utility to rebuild your entourage database.
ii) Attempt to create a new user identity and re-enter account information manually.

If you fail to perform Entourage database repair using the Database Utility tool, you may opt for third-party Entourage database recovery software like Stellar Entourage Recovery.

Easy-to-use Stellar Phoenix Entourage Recovery tool is the first entourage repair utility ever made to successfully repair and recover damaged, corrupted or inaccessible database. The Entourage database recovery software is designed to retrieve and restore damaged data of MS Entourage version 2008, 2004. This Microsoft Entourage recovery tool salvages contacts, e-mails, tasks, notes, attachments, journal, and all other database objects. Stellar entourage recovery software particularly designed to thoroughly check complete database and extract all your precious data efficiently.

Exchange recovery is a solution for corrupt Microsoft Exchange Server

culveraxel — Wed, 23 Feb 2011 04:48:16 -0800

Microsoft Exchange saves a whole lot of data in it. But at times, Exchange Server refuses to write more data. This happens because the disk space on the drive is low. Such an instance also results in inaccessibility of the data. Even, you become unable to read data. Corrupt Exchange Server database also creates a situation of data loss and demands Exchange recovery. In order to overcome such situations, you should use preventive measures. Backup can also be used to get data back. However, if backup is not available, then it is advised to make use of a third party Exchange Recovery software.

Let's consider a scenario. Suppose, you fail to start Exchange Information Store and you receive the following application event log on Exchange 2003 server that goes like this:

“Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 482
User: N/A

Description:
Information Store (4360) First Storage Group: An attempt to write to the file "D:\Program Files\Exchsrvr\mdbdata\res2.log" at offset 4194304 (0x0000000000400000) for 1048576 (0x00100000) bytes failed after 0 seconds with system error 112 (0x00000070): "There is not enough space on the disk.". The write operation will fail with error -1808 (0xfffff8f0). If this error persists then the file may be damaged and may need to be restored from a previous backup”

If starting Exchange Information Store is important for you, then you should find out the cause for above mentioned behavior and solution for it.

Cause:

Such behavior is seen because of low drive space on the Exchange Information Store Drive.

Solution:

For resolving above behavior, and to recover exchange server, You have to follow the below steps:

1.Try to free up the space of the disk on the Exchange Information Store Drive and after making a space. Restart Exchange System.
2.If the reason behind the problem is the corruption of database, then it is better to go for a third party MS Exchange Recovery software.

Many Exchange recovery software are available in the market. You might also make a search on Internet. Google will display a number of tools for you. Select a software by knowing all the features that the tool is providing. Take your time while selecting a software. A help file comes along with the software that contains all the information and specification about the software. The results produced by such Microsoft exchange recovery tools are satisfactory. Follow exactly the same steps that is guided in manual file.

Stellar Exchange Recovery is a reliable software that is developed only to perform Exchange server recovery task. With the help of this edb to pst tool, mailboxes are restored in individual PST files, that can be directly used in MS-Outlook. It supports MS-Exchange Server 2000, 2003, 2007, 2010, and 5.5. You can download a demo version of the software to evaluate the features.

Resolving “Entourage cannot find this item” with Entourage database repair tool

culveraxel — Mon, 21 Feb 2011 01:51:13 -0800

Corruption of Entourage identity is a normal behavior faced in Entourage. But, when identity gets corrupt or damaged. It leads to many problems, such as you face data loss situations. You totally lose access of Entourage items. Well, there is no need to get upset if you are facing the same problem. Corrupt Entourage identity can be rebuild by some inbuilt steps. If you do not get the desired results, then you can use a third party Entourage database repair tools. Through these tools, you can easily address the situation of corrupt Entourage database.

In respect to above issue, consider a practical situation. Suppose, you have import all the e-mail items of Entourage to a new Entourage. After importing the items to a new computer, when you do a double click on an Entourage. You receive an error message that looks exactly same as given below:

"Entourage cannot find this item. it may have been deleted or renamed"

To gain access of e-mail items you need to find out the cause and solution for above stated error message.

Cause:

Disgraceful cause for the occurrence of above behavior is the use of corrupt or damaged Microsoft Entourage identity.

Solution:

For solving above error message, you need to rebuild Entourage identity. Follow the below steps for rebuilding the identity:

1. Exit all the applications.
2. Press the Options (alt) key till you start Entourage 2004 and until you do not see the database utility window.
3. In the window, select database and then click Rebuild database and then select Continue.
4. You can see the progress from the Rebuilding Main Identify window. When the operation gets completed, a message appears like this "Your database was successfully rebuilt."
5. Select Done. Select Quit and then open Entourage.

If the problem gets solved, then it is fine. Other wise, make use of an updated backup. If backup falls short to recover data, then without thinking so much. Make a search on an Internet for a third party Entourage repair tools. You will get ample of tools that are meant for performing Microsoft Entourage repair. It is your choice which software you want to use. These tools have read-only designs and are non-destructive nature. You will face no further damage after the use of these third party tools.

Stellar Phoenix Entourage Recovery is a trustworthy tool that does the job of Microsoft Entourage repair easily and effectively. Mail items, such as contacts, attachments, appointments, journal, tasks, events, and more get easily repaired. The tool is designed for Entourage 2008 and 2004. It is compatible with Mac OS X 10.6 Snow Leopard, 10.5 Leopard, and 10.4 Tiger.

Way to recover deleted e-mails with attachment

culveraxel — Thu, 17 Feb 2011 03:04:04 -0800

Many times it happens that the message body of received e-mail do not contain important data, but its attachment contains significant data that cannot be afforded to lose. An attachment can be your MS-Word document, Excel spreadsheet, PowerPoint presentation, zip archive, any other type of file. That attachment can be saved in a computer hard drive or any location. For a safer side, if you have saved your attachment, you can restore it from that location. At times, e-mails gets accidentally deleted. Isn't it. But do not give up hope. As, third party deleted email recovery software is ready for your help.

In this section of article, a scenario has been discussed how an Outlook user lose his/her valuable data by removing an e-mail attachment. An Outlook user receives an offer letter from one of the reputed company in Outlook Inbox. After receiving the offer letter from a company, he is every happy. In excitement, he call one of his friends and show that e-mail containing attachment of letter to him. But while accessing the Inbox, that e-mail gets deleted accidentally by them. And, a result of this mistake is that attachment containing offer letter gets also lost. He has not even save that attachment into a computer hard drive. That e-mail does not even found in 'Deleted Items' folder. Now, an Outlook user is in a grave problem.

A situation of e-mail deletion is quite a big problem. Well, do not get fret. One truth is that when an e-mail gets deleted, data of it still resides in a PST file unless an until you do not overwrite data on it. But if you fail to recover deleted emails, then you can rely on a third party deleted e-mail recovery software. Such software recovers deleted and lost e-mails, along with attachments.

In market, numerous software are available these days. It is a good alternative when to recover e-mails is a primary concern. Without recovering the e-mail, a huge loss can be faced. For using these software, you have to pay a small amount of money. But these software produces quite good results. And, one good thing about these software is that you do not have seek any other's help. Such software are much capable to perform deleted email recovery on its own.

Stellar Phoenix Deleted Email Recovery is a competitive tool that is designed to recover deleted emails and other e-mail-objects also. The tool can recover and restore deleted e-mails of Outlook as well as Outlook Express application. File remains in original location and in original format. It works well with Windows 7, Vista, Server 2003, XP, and 2000.

Use Exchange Recovery tool for problematic Exchange Server database service

culveraxel — Wed, 16 Feb 2011 04:02:55 -0800

Sometimes Exchange Server database service simply refuses write access to the Exchange Server database files or checkpoint files. When database service exhibits the same behavior, it makes all the data of Exchange Server database inaccessible and unusable. You lose your access of important data. Behind such peculiar behavior, you can find numerous issues. Well, such data loss situation can be handled by an updated backup. If backup falls short too weak, then try to use a third party Exchange recovery software.

Let us take an instance to depict the above stated problem. Suppose Exchange Server database service denies write access to the EDB or CHK file, and you will come across the below event ID's:
“Event Type: Error
Event Source: ESE97
Event Category: General
Event ID: 145
Date: 2/3/2000
Time: 1:57:34 PM
User: N/A
Computer: EXSERVER1
Description: (1996) The database engine could not access the file called E:\exchsrvr\mdbdata\tmp.edb.”
“ Event Type: Error
Event Source: ESE97
Event Category: Logging/Recovery
Event ID: 158
Date: 2/1/2000
Time: 4:40:20 PM
User: N/A
Computer: EXSERVER1
Description: MSExchangeIS (1628) Unable to write a shadowed header for file D:\exchsrvr\MDBDATA\edb.chk.
(Microsoft Exchange Server 5.5 error format. In Microsoft Exchange Server 4.0, the Event ID for this error is 61; in Microsoft Exchange Server 5.0, the Event ID is 63.)”
These event ID's do not occur each and every time. Such kind of behavior occurs when there are some issues in Exchange Server. Valuable data of the Exchange Server database cannot be accessed.

Cause:
Some of the causes that are responsible for the occurrence of above error message are as follows:
a)File has been stolen by some other process, such as a virus checker. Access has been denied by backup process.
b)Occurrence of disk and controller failure.
c)Removal of the permissions from the folder where file has been kept.
d)Marked file as a read-only.
e)Deletion of file that is contained in the folder.
f)Corruption of Exchange Server database is one of the reason.

Resolution:
Above problem can be overcome easily by following methods:
i.If disk or controller failure occurs, then try to check the errors related to system log for I/O or drive errors.
ii.Use a suitable backup to restore permissions.

However, corruption of Exchange Server database file can be handled with a third party Exchange Server Recovery tools. Such third party tools easily perform Microsoft Exchange recovery effectively and efficiently. Valuable data of the Exchange Server database, such as contacts, attachments, journal, tasks, calendar entries can be easily recovered.

Stellar Exchange Server Recovery is a reliable tool used to perform MS Exchange recovery. It recovers data from the corrupt Exchange Server database. Additionally, it repairs Unicode formatted EDB files. It works well with operating systems, such as Windows 7, Vista, Server 2003, XP, and 2000. You can download a demo version of the software to recover exchange server data and check its overall functionalities.

About the Author:

The author of this article has a strong background in computer technology; She has been a technical writer and blogger for over 5 years. She is writing articles related to topics like Exchange Server Recovery and EDB PST Converter to repair and convert .edb to .pst file.

Rectify: “ Mail could not be received on account account_name...

culveraxel — Fri, 28 Jan 2011 00:30:45 -0800

Microsoft Entourage is an e-mail application for Mac. You can send and receive mails easily with this account as with others e-mail clients. But at times, it happens that Entourage starts behaving abruptly. This happens because of many reasons. Numerous reasons are responsible for it. Corrupt Entourage identity is one of the reasons for such behavior. All the data of the Entourage application becomes unapproachable for you. To overcome such a problem, you need to repair Entourage database. This can be best possible with a third-party Microsoft Entourage repair software.

Let's consider an error message that appears on the screen when you make an attempt to receive e-mail messages in MS-Entourage for Mac. But you fail to receive them. In addition to failure, you receive an error message like this as given below:

“Mail could not be received on account account_name. The domain name servers are not responding.”

In this situation, data of the MS-Entourage cannot be accessed. In other words, situation of data loss occurs.

Cause:

Above error message occurs if the following conditions are true:

1. Down or non-operational e-mail server on Internet Service Provider.
2. Wrong information of e-mail account.
3. Corrupt or damaged Entourage identity.

Resolution:

To sort out the above problem you have to follow the below mentioned steps:

* If the error is due to down or non-operational e-mail server, then contact Internet Service Provider (ISP). ISP checks whether the e-mail server is operational and the settings of your e-mail account. It also tells you when the e-mail server will be operational again and informs you about the settings of your e-mail account.

If the information is incorrect, then make sure that the information of e-mail account is corrected.

If corrupt or damaged Entourage Identity is the reason for the above error, then make an attempt either to repair Entourage identity or use an updated backup.[/italic]

If none of the above steps help you to sort out the problem, then try to repair Entourage using a third-party Entourage database repair software. A lot of software are available in the market that do the job to repair Entourage quite well. These tools are read-only and non-destructive in nature. For using these tools there is no need to have a prior recovery experience.

Stellar Phoenix Entourage Recovery is a self-explanatory tool used to repair and rebuild Entourage database. It repairs the corrupt file, even if the file is logically corrupt. This tool is read-only in nature. It performs safe Entourage recovery. The tool is compatible with Mac OS X 10.6 Snow Leopard, 10.4 Tiger, and 10.5 Leopard.

How to mend Exchange server error “Error -1022='JET_errDiskIO' = Disk I/O error”?

culveraxel — Mon, 24 Jan 2011 03:41:00 -0800

Database of MS-Exchange server leads to several errors. These errors makes it quite difficult to work smoothly. Sometimes it happens that database file of Exchange server refuses to open. On each attempt to open database of Exchange server, you remain unsuccessful. Corruption of Exchange database is one of the reasons for such a behavior. Because of this, data cannot be approached. You fail to access the content of database. To avoid such data loss situations use a backup. However if backup falls short in recovering data, then perform Exchange recovery with the help of third-party Exchange Server Recovery tool.

Related to above topic let's study an error message. As discussed above, Exchange server gives an error message on the screen when you attempt to open database of Exchange server. Database cannot be opened and when you see the details of the error you notice the following event log in the description:

Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 489
Computer:Computer Name
Description: Process name [process id] file name: An attempt to open the file [path\file name] for read-only access failed with [Error Code and Explanation]. The open file operation will fail with error [-1022].

Root of the issue:

The “Error -1022='JET_errDiskIO' = Disk I/O error” is caused when a disk I/O error stops Exchange from accessing requested database page or a check file. This could be because of disk or controller that prevents you from accessing the disk (though this may be temporary). Also check the log for drive or input/output errors around the time of Event 490. The problem occurs when the path for check file is wrong, may be due to drive failure.

Solution:

To handle above error execute “chkdsk /f /r” command. If executing this command does not solve the problem, then verify the permissions on Exchsrvr folder. Ensure that SYSTEM has full control of Exchsrvr and all the sub-folders (on every partition) that contain Exchange data.

If you cannot mount databases, then you will need to troubleshoot Windows NT file-level anti-virus software that might be running on the Exchange server. Also check the log for drive or input/output errors around the time of Event 490. Verify and correct the path for the check file. You can also correct the root cause, and use an updated backup to retrieve data of the database.

If all else fails, then performing Isinteg -fix, and ExMerge command to a new Information Store also helps you to sort out the problem.

However if no satisfactorily results are found after using above commands, then opt for a third party Exchange Recovery tool. A lot of tools are available in the market that have the main objective to recover exchange server.

Stellar Phoenix Mailbox Exchange Recovery is a sophisticated and recovery for exchange server utility that successfully performs Exchange Server recovery in all the cases of corruption. This Exchange Recovery Software recovers all the data of .edb files contained in messages, notes, tasks, attachments, and in other objects.

How to convert EDB to PST When EDB file Get Corrupted?

culveraxel — Mon, 13 Dec 2010 01:50:50 -0800

MS Exchange Server is the most powerful and reliable tool to provide the effective communication environment. It uses a database file to store the information of the users. Exchange Server has different mailboxes for every individual user that are accessed by users with their email client like MS Outlook. Like other database it also faces the heat of corruption and gets corrupted due to many known and unknown reasons like Exchange server crashes, virus attack and some human errors etc.

When corruption occurs, EDB file becomes totally unusable and you may encounter serious data loss situation. You also get some irritating error messages, when you try to access the data from this corrupt edb file. In these situations, users can not access their mailboxes through MS Outlook. To get access all the user data in the outlook, you need to repair edb file by performing edb to pst conversion using some perfect EDB PST Converter tools.

Causes of Exchange Database Corruption:

Although there are many reasons of edb corruption, Let's take a look of the most prominent causes of corruption:

1. JET engine errors
2. Due to Virus attacks
3. Exchange Server Error Code 528
4. Hardware Failure Errors
5. Server failure or Crash
6. File Header Corruption
7. Log Files Deleted
8. Dirty Shutdown due to power spate
9. Due to Upgradation
10. Logical corruption of Exchange Database
11. Due to Some Human Errors
12. Deletion of user Mailboxes

Corruption of edb file may makes you panic because it stores important emails, contacts, notes, task, journal, drafts, attachments, calender items etc. of hundred of users and after corruption you will not be able to access these items.

Solution:

Whatever the trigger, the consequences of exchange database corruption can be a devastating, and recovery from it is not instantaneous. In order to combat these corruption situation, Microsoft provides some free utilities, named as Eseutil.exe, Exmerge.exe and Export-Mailbox. These tools convert edb to pst and extract the user mailboxes in .pst file format. However in case of severely corruption, these tools may fails. The best way to cope this situation is using some advanced third party EDB to PST Converter software. One of such tools is Stellar Exchange Server Recovery.

The newly and updated Stellar Phoenix Exchange Recovery tool is devised with extensive scanning algorithm that scans the complete exchange database. This EDB to PST tool will successfully convert all your inaccessible edb file data into .PST(Personal Storage) file format which can be imported in MS Outlook directly and you can access the same using Mirosoft Outlook. The Comprehensive EDB Recovery software is compatible with MS Exchange Server 2010, 2007, 2003, 2000 and 5.5.

The free evaluation version of the EDB to PST Converter allows you to extract the data from inaccessible .EDB files. However, it restricts you from saving the extracted Exchange mailboxes data from EDB to PST. In order to save the complete user data, you need the full version of the software.

MS Outlook and Outlook Express mails can be recovered Using Deleted e-mail Recovery tools

culveraxel — Tue, 30 Nov 2010 21:35:35 -0800

It is quite a common thing for e-mail applications users, such as MS Outlook and Outlook Express application users, to suffer deletion of important mails. Many times, mails get accidentally or unintentionally deleted from the mail account. And the user has no idea that his crucial mails have been deleted. To recover e-mails, 'Deleted Items' folder can be used. But what if you do not find any of the accidentally deleted emails in your 'Deleted Items' folder. In MS Outlook mails get automatically deleted, if the option 'Empty the Deleted Items folder upon exiting' is enabled. Don't worry! There is no need to panic. In case, you have maintained backups, then use that to recover mails. Otherwise, use a deleted e-mail recovery tool to recover deleted emails and other items of your Outlook mail application.

Suppose, an Outlook user finds one day that some of his important mails have been deleted from his/her email account. Thinking, he/she has accidentally deleted important mails, he/she tries to access those mails from the 'Deleted Items' folder. When he/she tries to access those mails, then he/she learns that they are not even present in the 'Deleted Items' folder. Such inconvenience is caused because 'Empty the Deleted Items folder upon exiting' option is checked instead of unchecked.

How to recover:
To get over such a pathetic situation you have to recover deleted e-mails. For recovering, if you have an updated backup, then use the backup to retrieve important mail from that backup. If you have deficient backup along with you, do not give up hope. Use a third party Deleted E-mail recovery tool.

Deleted Email Recovery software are only meant to recover deleted mails and other components, such as contacts, attachments, appointments, tasks, meeting requests, notes, distribution lists, journals, and events. These tools are easy to understand and simple to use. In addition to this, these are read-only and non-destructive in nature. They recover deleted mails, irrespective of the reason owing to which the mails get deleted.

Stellar Phoenix Deleted Email Recovery is a proficient tool that can restore deleted mails of Outlook as well as Outlook Express application. It creates and saves data in .eml, .pst, and .msg file formats. Original formatting of RTF and HTML messages remains intact. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this tool supports versions of MS Outlook 2000, 2007, 2003, and 2002 and Outlook Express 5.x and 6.0.

Important Email Deleted With Junk Mail Folder Mails? Recover It

culveraxel — Thu, 25 Nov 2010 04:24:45 -0800

Did you deleted all the messages in your 'Junk Mail' Folder, and now feel that an important awaited message might have found its way into that folder, before you deleted that folder? Or have you removed all the 'Deleted Items', and feel that some important messages might have been accidentally deleted before you emptied the 'Deleted Items' folder? Well, such accidents do happen! So don't panic. The email must have been transferred to that part of the computer where it may be overwritten. But, if you have instantly realized it, then chances are that your data or email is still safe somewhere on that system. So, all you need to do is, take out that last taken backup to perform deleted email recovery. But if you do not have a backup, then you may use a reliable software to recover deleted emails.

Deletion of emails in the concerned email-application is just as normal as deletion of any other file saved on the computer. And just as files that are deleted from the system are safe on the hard drive, so are the emails. The only difference is in the storage and recovery mechanism as the files and messages are different forms of data. Depending on this fact, different software are available to restore deleted emails and other items. Needless to say, the emails are one of the most crucial means of communication. In fact, they are the most important pieces of information. That is why, a number of well-defined archiving systems are also available. Such systems provide essential disaster recovery in above stated situations.

But in case, you didn't know about archiving, then you will need to opt for a third-party deleted email recovery application. These are special applications that are designed after detailed understanding of the email application, its storage mechanism, and the way data is deleted or discarded by these applications. Good applications recover password protected PST plus encrypted PST file.

Stellar Phoenix Deleted E-mail Recovery is a reliable tool that performs complex scanning algorithms to recover any and every piece of data that has been deleted accidentally or intentionally, and needs to be recovered. Some of these items include emails, attachments, calendar-entries, tasks, contacts, lists, and appointments. With support for MS-Outlook 2007, 2003, 2002, 2000 and Outlook Express 5.x and 6.x, this Deleted email recovery software is compatible with Windows 7, Vista, XP, 2003, 2000 and NT4 (SP6).

Tips to Solve 'The database will be unable to restore' Error in Exchange Server

culveraxel — Sat, 30 Oct 2010 00:03:45 -0800

Microsoft Exchange Server may sometimes report errors when an Exchange-aware backup is running. Not always, but database corruption is the most common reason for a backup failure. You can analyze the exact cause of the problem by the event ID and related error description logging in the application log of Exchange Server. If this comes out to be database corruption, you then need to implement Exchange Server Recovery methods.

For example, consider the below event ID and backup failure error, which might occur post failure of a backup attempt.

Event ID: 217

Source: ESE

Type: Error

Category: Logging/Recovery

Description:

Error err_num During backup of a database location. The database will be unable to restore.

The symbolic name of the above error is 'BACKUP_ERROR_FOR_ONE_DATABASE'.

Cause

To know the root cause of the given problem, you should check the err_num in description section of the above event. Common reasons for backup failure are described underneath:

1. Microsoft Exchange Server creates a .pat file to record database page changes that the backup process runs while it is running. The above error can occur if it cannot access the .pat file for some reasons.

2. If the err_num is -1018, hardware issues are most likely to cause the problem.

3. If the err_num is -613, this indicates presence of checksum errors in .stm or SLV file. This problem can occur because of hardware issues or third-party SMTP disclaimer software packages.

Solution

You should troubleshoot the given problem by following these methods:

1. To unlock the .pat file, you need to stop the software that might be accessing the file, such as another backup software or an antivirus application. Alternatively, you can also wait till the application finishes and release the file. Try to run the backup program again.

2. In case of -1018 error, you need restore the database from last online backup or move the mailboxes to another store (in case you use Enterprise version) or run eseutil /p and isinteg -fix commands or run a third-party tool like Stellar Exchange Recovery software to recover exchange database.

3. In case of -613 error, you should repair the .edb and related .stm file.

If you execute eseutil utility, data loss is likely. Thus, using Exchange Mailbox Recovery is the safest option.

Stellar Exchange Server Recovery is a reliable utility that repairs corrupted Exchange database and allows restoring only the required mailboxes as *.pst files. This Exchange Database Recovery software supports MS Exchange Server 2007, 2003, 2000, and 5.5.It can also recover deleted mailboxes.

Rectify “This Identity Cannot Be Opened With This Version of Entourage.

culveraxel — Wed, 13 Oct 2010 03:26:21 -0800

Are you facing problems related to your MS Entourage Database? Any problem related to Entourage means all the mail-objects such as messages, contacts, calendar-entries, tasks, events, and similar features cannot be accessed. Entourage uses database to store data. But many times it happens database gets corrupt. When database gets corrupt Entourage application becomes useless. You become unable to access mail-objects and even you cannot send or receive mails from Entourage to some other persons. Anyhow, to get over such situation updated backup is quite helpful. If updated backup is not available, then make use of a third party Entourage Repair tool.

To illustrate above issue, let's take an example that appears on the screen when you try to open Entourage database but fail in your attempts:

"This Identity Cannot Be Opened With This Version of Entourage.”

The above error indicates that your database is severely damaged and it is unusable. To salvage data from such damaged database, you must find out the ground of the issue and then perform Entourage recovery by fixing it.

Ground of the Issue:

The main cause for the occurrence of the above error message is the corruption of Entourage database. Corruption occurs due to number of reasons. Some reasons are discussed such as application malfunction, fatal virus attacks, unexpected system shutdown, database header gets corrupt, identity gets corrupt.

Resolution:

To resolve this error you need to repair entourage database. Use simple steps to repair entourage database.

- First of all check the Entourage database using Database Utility to check out the corruption.

- If the database is corrupt, then rebuild MS-Entourage with an inbuilt database utility tool.

- Restore the database from updated backup. But if the backup is not available, then it will be a problem.

However, if the above resolution steps fail to repair Entourage, then make use of a third party Entourage repair software. These software are capable to rebuild entourage database corrupted due to any of the reason. Now a days, numerous software are available in the market that repairs entourage database and allows mail objects, such as messages, contacts, calendar-entries, tasks, events and similar objects quite effectively. A high end scanning algorithms are used for safe and easy recovery of Mac Entourage. Built with simple graphical user interface, the tool does not require prior technical skills.

Stellar Phoenix Entourage Repair v1.1 is a tool that repairs Entourage database and helps you to manage mail related components quite easily. When a tool repairs entourage database that repaired database is restored on a user-defined location. This Entourage database repair tool is compatible with Mac OS X 10.6 Snow Leopard, 10.4 Tiger, and 10.5 Leopard. You can download a demo version of the software

Repairing EDB database file in MS Exchange 2000 Server when you are unable to mount public store

culveraxel — Tue, 14 Sep 2010 05:27:42 -0800

In the MS Exchange Server systems, the public folders are well structured databases, which enable you to collect, organize, and share the information with your colleagues in your organization. These public folders are mounted when you start Exchange server and can be replicated between different versions of Exchange servers. However, when you are unable to mount the public store then very often corruption in the EDB file is the major reason behind this. You should try to find out the reason for EDB corruption and try to repair EDB file. If none of the methods work, then the only way-out is to use a third-party EDB repair software to do the needful.

Assume a practical scenario in which you are using MS Exchange 2000 Server Edition. You are unable to mount the Exchange public folder store as the following error message is displayed:

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.

ID no: c1041724

Exchange System Manager”

When you check the Application event log, you find the following event ID:

“Source: MSExchangeIS Public

Event ID: 1133

Type: Information

Computer: Exchange

Allocating message database resources for database "First Storage Group\Public Information Store (Exchange)".

Cause:

There could be different causes for this generic error. Some of them are:

The first Exchange Server was deleted, which caused this problem. Because of this, the respective public folder store is transferred to the 'LostAndFound' container.

It may also be possible that the old public store and/or the whole server is moved to the 'LostAndFoundConfig' container.

Resolution:

The problem can be solved using the following methods:

You should use the 'Active Directory Users and Computers' feature to delete the ExchangeOld folder store from the 'LostAndFound' container.

You should use the 'ADSI Edit' feature to remove the ExchangeOld folder store from the 'LostAndFound' container.

Note: When you perform either of the aforementioned methods, ensure that the Default Public Store is referring to the existing public folder store.

However, if the problem is persisting even after performing these methods then it means the EDB file is damaged, which can be repaired using a third-party EDB repair software. Such read-only EDB recovery tools are extremely safe to use that do not overwrite the existing EDB database file during the recovery.

One of the most efficient EDB repair tools is Stellar Phoenix Exchange Server Recovery, which repairs EDB database file meant for MS Exchange Server 5.5, 2000, 2003, and 2007. With the capability of extracting individual PST files for every user mailbox from EBD file, this EDB repair software is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

How to troubleshoot when you are unable to mount a damaged MS Exchange Server 2000 database

culveraxel — Mon, 30 Aug 2010 23:40:11 -0800

MS Exchange Server from Microsoft is the server side of the client-server product, which enables a system administrator to monitor and manage user mailboxes in the organization. It enables emailing, calendaring, supports both web- and mobile-based access. All such information is stored in an EDB (Exchange Database) database file, which can get corrupt and make all the vital information seem very susceptible. In such cases, you should try and find out the reason of EDB corruption and try to fix the problem. If you are unable to resolve the issue, then there is a serious need to look for Microsoft Exchange recovery software that will enable you to perform Exchange Server Recovery.

Let us take an example in which you are unable to mount MS Exchange Server 2000 database. The following error message is displayed in this regard:

“The name of one of the database files in this store is invalid.
ID no.: c1041737
Exchange System Manager”

In the event log, you may find the following event ID:

“Event Type: Error
Event Source: ESE98
Event Category: Database Corruption
Event ID: 470
Date: May 29, 2001
Time: 4:55:47 P.M.
User: N/A
Computer: Servername
Description:
Information Store (3112) Database E:\Program Files\Exchsrvr\Mdbdata\Priv1.edb is partially attached. Attachment stage: 4. Error: -1022.
For more information, click http://search.support.microsoft.com/search/?adv=1.”

Cause:

The most possible cause of this problem is that the EDB database file has corrupted. Because of which, Exchange 2000 is unable to write data on the hard disk. The presence of Event ID 470 is quite apparently displayed in the event log. Another reason for this error is that incorrect permissions are there for the 'Exchsrvr' folder structure.

Resolution:

To resolve this problem and perform Exchange recovery, you should perform the following methods:

1.Run the 'chkdsk' tool to scan the hard disks on the host Exchange server using the following parameters:
chkdsk /f /r
2.Analyze the permissions on the 'Exchsrvr' folder structure. You should also ensure that the SYSTEM has full rights of the 'Exchsrvr' folder and its subfolders.
3.If the problem is still not resolved, then you should try to fix any antivirus-related issue. For this, you should configure the antivirus settings so that it does not scan the 'Exchsrvr' folder and its log file directories.
4.If the previous method does not work, then you should uninstall the antivirus and try to restart the Server. It should work fine now.

If the problem is persisting, then there is a need to use a third-party Exchange recovery software to repair the EDB database file. These Exchange Server recovery tools employ fast yet sophisticated scanning algorithms to repair EDB file without overwriting or modifying the existing it.

The best Exchange Recovery Tool available in the market today is Stellar Phoenix Exchange Server Recovery, which recovers EDB database files created for MS Exchange Server 5.5, 2000, 2003, 2007 and 2010. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this Microsoft Exchange recovery software recovers inaccessible EDB database into separate PST files for every user. In addition, this Exchange recovery utility maintains the formatting of the RTF and HTML messages.

Causes and Fixes for Logical Corruption in Exchange Server Database

culveraxel — Wed, 14 Jul 2010 23:58:08 -0800

Like other databases, Microsoft Exchange Server database (EDB file) may also corrupt at some point of time and does not let you perform typical Exchange Server operations. The corruption can be of two types - Logical and Physical. Logical corruption is pretty common and occurs due to internal fault in the database. When it happens, Microsoft Exchange Server database becomes totally unusable and you encounter serious data loss. MS Exchange Server does not include any utility to detect and fix logical corruption. Thus, you are required to opt for Exchange Recovery to get your valuable data back.

You may encounter logical corruption of EDB file due to any of the following reasons:

1.If you incorrectly run the soft recovery using eseutil /r tool after restoring database from an online backup, it replays only log files and ignores the patch files. It may result in logical corruption. Extensible Storage Engine 98 does not let you run the soft recovery on an EDB file that needs hard recovery. In case you try this, the following Jet error appears in Application Event Log of Exchange Server:

“JET_errSoftRecoveryOnBackupDatabase (-544)”

2.If you initialize an inconsistent EDB file, the process checks whether that log range specified in database header is there in directory of log, and signatures of both log and database are correct. In case it does not find the specified values, it logs the below event:

“JET_errRequiredLogFilesMissing (-543)”

3.The database may also face logical corruption if you run eseutil /p utility. Jet-level Exchange Server database repairs result in some inefficient disk space uses and data loss, because it fixes the EDB file by deleting the corrupt data.

Resolution

To fix this problem and ensure effective Microsoft Exchange recovery, follow the underwritten steps:

1. Defragment the database using eseutil /d command and then run database integrity check using Isinteg -fix command.
2. Restore corrupt EDB file from the most recent backup. You should not run the soft recovery after restoring from backup as it may cause further damage.
3. Use third party Exchange recovery software to repair and restore the problem database.

The Exchange recovery tool is particularly designed to perform in-depth scan of entire EDB file and extract all inaccessible data from it. They offer simple and secure recovery due to their rich graphical user interface and non-destructive nature.

Stellar Phoenix Exchange Mailbox Recovery is the most efficient and comprehensive tool to offer exchange database recovery in all EDB corruption scenarios. It restores emails, contacts, tasks, notes, journal, attachments, appointments, and other EDB file objects. The exchange user profile recovery software works well with MS Exchange Server 2007, 2003, 2000, and 5.5.

How to Handle Meeting Request Deletion in Microsoft Outlook?

culveraxel — Tue, 13 Jul 2010 00:20:21 -0800

Are you using one Microsoft Outlook account on two different computers? Have you configured your Outlook in such a way that all you emails are received on two different addresses? You may face critical problems of calendar entry deletion in such configuration. When you remove a meeting request from one computer, it is deleted from other Outlook account as well. In such critical situations, you need to use Deleted Email Recovery solutions to recover lost meetings and other calendar entries.

As a practical example of this behavior, you may lose meeting requests from one system, if you remove from another one. The problem occurs generally if both the computers are connected to same MS Exchange Server mailbox. For instance, this scenario might include a laptop, which is using the Cached Exchange Mode, and one desktop computer, which is using Online mode. You can also consider the below scenario:

1. You receive one meeting request.
2. You make sure that the request exists in Inbox of both the system.
3. You start Outlook on your laptop.
4. You click the 'Work Offline' option on File menu.
5. You open a meeting request on your desktop computer, which is using the Online mode. Then, you click the Accept option.
6. You remove the meeting request from Inbox folder while you are offline on your laptop computer. Then, you update the modifications to Microsoft Exchange Server mailbox by clicking Send and Receive option.
7. You delete the meeting from Calendar.

In this case, the meeting request that is accepted on desktop computer is processed immediately. However, the meeting request, which is removed on laptop is synchronized later on. After completion of synchronization process, meeting request is also deleted from desktop computer.

In such critical situations, you must have a complete backup of your Microsoft Outlook PST file to restore data from it. However, in case the backup is not available or it is not updated, you may fall in critical situations that require deleted mail recovery to be fixed.

You can easily Recover Deleted Email using advanced and efficient third-party applications. The deleted email recovery software use advanced scanning techniques to thoroughly scan entire PST file and extract all deleted items from it. They are incorporated with self-explanatory and interactive graphical user interface to ensure easy recovery.

Stellar Phoenix Deleted Email Recovery is the most comprehensive tool to recover deleted items from Microsoft Outlook PST file. The software successfully recovers emails, contacts, meeting request, calendar entries, and attachment. It works well with Microsoft Outlook 2007, 2003, 2002 (XP), and 2000.

How to rectify Error c1041724 in MS Exchange Server 2000

culveraxel — Mon, 12 Jul 2010 01:33:08 -0800

Are you facing problems in accessing mailbox folders in MS Exchange Server 2000? Usually, such things happen when some internal settings for the mailbox store are not correctly set. Also, it may also be possible that the mailbox folder itself has got corrupted. Such corruption can occur due to various reasons such as abrupt or improper system shutdown, database header corruption, corruption of transaction log files, etc. In such cases, you should try to resolve the issue using appropriate corrective measures. In you are not able sort the issue, then you should use a third-party Exchange recovery software to repair MS Exchange Server mailbox store.

Consider a scenario wherein you are unable to mount an MS Exchange Server 2000 mailbox store using Microsoft Exchange System Manager. An error message is displayed, that is:

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both. ID no: c1041724 Exchange System Manager”

In addition, either or all of the following event IDs will be logged in the Application event log as well:

1. Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Description:
The MAPI call 'OpenMsgStore' failed with the following error: The attempt to log on to the Microsoft Exchange Server computer has failed. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0512-00000000

2. Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9546
Description:
Failed to create the Event Registration Mailbox for Database First Storage Group\Private Information Store (servername). Error – 0xbf69.

3. Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description:
Error 0x80004005 starting database "First Storage Group\Private Information Store (servername)" on the Microsoft Exchange Information Store.

Cause:

The root cause of this problem is that the System mailbox object exists in the System Objects container, which is created for this mailbox store. And when you try to mount it, Exchange Server creates another object for the same, which is causing the problem.

Resolution:

To resolve this issue, you should perform the following steps:

1.Start the Active Directory Users and Computers snap-in.
2.Click the Advanced Features option in the View menu.
3.Find the Microsoft Exchange System Objects container, and then look for the System mailbox object whose mailbox store you were trying to mount.
4.Delete the System mailbox. Now try to mount the mailbox store. It should run fine now.

However, there are few instances when the problem is not resolved using these steps. In such cases, you should use a third-party Microsoft Exchange Recovery software. Such read-only tools are highly interactive and user friendly in nature that ensure safe and secure Exchange Server recovery.

Stellar Phoenix Mailbox Exchange Recovery software is an Exchange recovery software that repairs corrupted Exchange mailboxes created in MS Exchange Server 5.5, 2000, 2003, and 2007. It restores the mailboxes into separate PST files for each user. This Exchange Server Recovery utility is compatible with Windows 7, Vista, Server 2003, XP, and 2000.