Nobody wants any inconvenience while working with MS-Exchange Server information store. But still, you face problems. Have you ever give a stress to your mind why such behavior occurs. It is good to spend time to find out the cause. Because without knowing the responsible reason for the problem. You cannot solve the problem. Exchange Server stops working because of some hard ware issues, driver issues, Exchange Server corruption. Many times, reasons are described in the event ID itself. The best way to sort out the corruption related problem is a third party Exchange Server Recovery software.
For instance below error message might get received when MS-Exchange Server information store fails to start, or it stops working if it is already in use. Event ID mentioned below gets received like this:
''Event ID: 145
Source: ESE97
Category: General
Description: MSExchangeIS ((%pid%) ) The database engine could not access the file called %database path%\edb.log.''
Event ID that is mentioned above do not get received every time. It occurs intermittently.
Cause:
Event ID occurs when a event lists locked open the file. This happens when locked files open by antivirus software and backup. For verification whether the file is locked open or not follow the below steps:
Log on to the Exchange Server computer by the administrator account.
Make a Test folder.
Enter the following at the command prompt:
copy database path\edb.log c:\test
Other reason might be the corruption of Exchange Server information store.
Solution:
For solving the above problem, do a installation of AV software, backup, or other software so that any of the data files cannot get directly accessed on the Exchange Server. Do not include all \exchsrvr directories from being scanned by file based virus scanning software. This is advisable because Exchange aware AV scanning software do not access the files directly and do not cause this issue.
For taking the backup of Exchange server files, firstly stop the Exchange Services. Exchange aware backup product can be used to back up the Exchange databases in a online mode. No file contention problem will be faced.
However, if still problem persists, then it means that the Microsoft Exchange information store is corrupt or damaged. Eseutil/p can be used to repair the Exchange Server database. But it many situations, it might not work. So, for such cases you can use a third party Exchange Recovery software. Such software proves very helpful to perform Exchange Server Recovery.
Stellar Phoenix Exchange Server Recovery is a fast and easy tool that successfully performs Exchange recovery. It recovers the email addresses from Active Directory storage. The tool supports MS Exchange Server 5.5, 2000, 2003, 2007 and 2010. It shows compatibility with Windows 7, Vista, Server 2003, XP, and 2000.
For instance below error message might get received when MS-Exchange Server information store fails to start, or it stops working if it is already in use. Event ID mentioned below gets received like this:
''Event ID: 145
Source: ESE97
Category: General
Description: MSExchangeIS ((%pid%) ) The database engine could not access the file called %database path%\edb.log.''
Event ID that is mentioned above do not get received every time. It occurs intermittently.
Cause:
Event ID occurs when a event lists locked open the file. This happens when locked files open by antivirus software and backup. For verification whether the file is locked open or not follow the below steps:
Log on to the Exchange Server computer by the administrator account.
Make a Test folder.
Enter the following at the command prompt:
copy database path\edb.log c:\test
Other reason might be the corruption of Exchange Server information store.
Solution:
For solving the above problem, do a installation of AV software, backup, or other software so that any of the data files cannot get directly accessed on the Exchange Server. Do not include all \exchsrvr directories from being scanned by file based virus scanning software. This is advisable because Exchange aware AV scanning software do not access the files directly and do not cause this issue.
For taking the backup of Exchange server files, firstly stop the Exchange Services. Exchange aware backup product can be used to back up the Exchange databases in a online mode. No file contention problem will be faced.
However, if still problem persists, then it means that the Microsoft Exchange information store is corrupt or damaged. Eseutil/p can be used to repair the Exchange Server database. But it many situations, it might not work. So, for such cases you can use a third party Exchange Recovery software. Such software proves very helpful to perform Exchange Server Recovery.
Stellar Phoenix Exchange Server Recovery is a fast and easy tool that successfully performs Exchange recovery. It recovers the email addresses from Active Directory storage. The tool supports MS Exchange Server 5.5, 2000, 2003, 2007 and 2010. It shows compatibility with Windows 7, Vista, Server 2003, XP, and 2000.
0 comments:
Post a Comment