Blogs >> Technology >>
How to troubleshoot when you are unable to mount a damaged MS Exchange Server 2000 database
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, and 2007. 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.
To Know more visit: http://www.ms-exchange-server-recovery.com/
|
|
