Sunday, July 6, 2014

Resolving Mounting Issue of a Damaged MS Exchange 2000

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 works with MS Outlook, which is the client side of the client-server product. MS Exchange Server enables emailing, calendaring, supports both web- and mobile-based access. All such information of user mailboxes is stored in an EDB (Exchange Database) database file. 

However, such database file 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. There are some simple measures that help in recovering the corrupt file. In addition, you can try few inbuilt repair mechanisms provided by Microsoft. If you still not 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.

Such issue can arise in any MS Exchange version. However, 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

Information Store (3112) Database E:\Program Files\Exchsrvr\Mdbdata\Priv1.edb is partially attached. Attachment stage: 4. Error: -1022.
For more information, click”

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. However, there could be other reasons depending upon the version of the MS Exchange Server.

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

  • Run the 'chkdsk' tool to scan the hard disks on the host Exchange server using the following parameters: chkdsk /f /r
  • 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.
  • 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.
  • If the previous method does not work, then you should uninstall the antivirus and try to restart the Server. It should work fine now.

The above steps can be easily performed to repair the Exchange database file. Moreover, the tools are in-built in MS Exchange.

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

Such Microsoft Exchange recovery software’s recovers inaccessible EDB database into separate PST files for every user. In addition, they are created to be supported across various versions of Windows including the latest Windows 8. Moreover, the software maintains the original formatting of the files including the RTF and HTML messages.

No comments:

Post a Comment