HOW TO SOLVE WHEN EXCHANGE DATABASE FAILS TO MOUNT WITH (HR=0X80004005, EC=-528) ERROR

Published by admin on June 11, 2016

Transfer log files testimony all variation to Exchange Server record and are decisive for appropriate implementation of Exchange. If you get rid of a log file that hasn’t been inscribed to connected catalog, it can carry numerous problems, most ordinary being that file may not pass to accumulate. You may resolve this difficulty by eradicating all log files, but primarily you require checking database steadiness. If it survives in conflicting state, the resolution is to reinstate using backup or pertain an EDB Repair method.

For illustration, take a situation in Exchange Server. You attempt to grow a mailbox amass, but maneuver fall short using error message beneath:

“Exchange is powerless to build up database that you specify. Particular database: ServernameFirst Storage GroupMailbox Database; Error code: mapiExceptionCallFailed: Incapable to build up database. (hr=0x80004005, ec=-528)”

The issue arises every time when you struggle to mount store. Accordingly, all clients associated to server are disengaged.

Manual Solution:

To work out this difficulty, you require moving transaction files to dissimilar directory. Follow steps stated beneath:

1. Discontinue Information and all records in storage group
2. Authenticate integrity of database by executing esesutil /mh command, associated by name of database (as Mailbox Store1 database, name is Mailbox Store1.edb). Scrutinize ‘State’ value beneath header details
3. If database is Clean Shutdown (Consistent) state, you securely eliminate all transaction record file and store them to another folder. Ensure you do not eradicate present transaction log file
4. If database within Dirty Shutdown situation, retrieve from last online backup. If backup is unacceptable, execute eseutil /r command for soft restoration.

Common Exchange Server Database Errors and Causes

A large EDB or exchange database is always vulnerable to corruption issues and once it gets damaged user might experience lots of common Exchange Server errors, some of them are given below:

• Exchange Server Error 550
• Unable to initialize the MS Exchange Information Store service
• JET_errRecordNotFound, Jet_errRecordDeleted
• Exchange Server Error Code 528
• # JET_errBadDbSignature -531
• # JET_errDatabaseStreamingFileMismatch -540
• # JET_errConsitentTimeMismatch -551
• # JET_errDatabaseDirtyShutdown -550
• # JET_errInvalidDatabaseId -1010
• # JET_errInvalidDatabase -1028
• # JET_errFileInvalidType -1812
• # JET_errFileInvalidType -1812
• # JET_errDatabaseCorruptedNoRepair -1224
• “Edb.log error.”
• “Edb.log is missing.”
• “Edb.log not found.”
• “Edb.log failed to load.”
• “Failed to register edb.log.”
• “Runtime Error: edb.log.”
• “Error loading edb.log.”

Common Causes of EDB Corruption:

• When EDB file storage area gets overfull because of diverse mailboxes of numerous user accounts tend to share a single file
• Unexpected power failure may also affect the server and damages the EDB file
• Sometimes deletion of user’s mailbox mistakenly can also lead to the corruption
• Any fault appear while the execution of JET engine oriented transactions
• Due to inconsistent data can also generate errors
• Improper configured Server attendant services
• Deletion of LOG files can cause storage discrepancy
• An oversized transaction logs might be affect the work of EDB file and slowdown its performance.
• Computer Virus or Malware attack
• Hard drive failure
• Checksum errors

How to detect and prevent physical Exchange database corruption?

Once exchange database gets physically corrupted or infected with HOW TO SOLVE WHEN EXCHANGE DATABASE FAILS TO MOUNT WITH (HR=0X80004005, EC=-528) ERROR situation then you may see the variety of error messages prompted to the screen. One of the common error messages is Exchange error 1022 (JET_errDiskIO) that prompt after the physical corruption in the Information store. These types of error messages are clear signs that your database got damaged and required to be repaired.

One of the popular way to spot physical corruption in the information store is Online backups, in online backup procedure, each pages of the database is verified so any corruption will be spotted easily.

If you discover any types of corruption in the information store then you should try to execute and run exchange recovery tool over the Exchange database.

• If you want to detect errors in database at the page/ file level then you should try the Esefile.exe utility.
• Eseutil.exe utility is able to detect and repair the page/file level corruption.

Eseutil.exe utility is also able to detect the corruption at database level. In the manner to detect the application level corruption, you may run Isinteg.exe utility. It is observed that page/file level corruption can further lead to database or application level corruption issues. So, it is strongly suggested to use Isinteg utility after executing Eseutil.

How to prevent physical corruption to the database:

• Make sure that the hardware components used must of good quality
• It is also necessary to make sure that the configuration and other settings of the hardware mechanism must be correctly configured and checked after a fix time of interval.
• It is recommended to avoid using antivirus program or any other file level tool on the Exchange server system.

About the EDB Repair Tool

To repair damaged or error showing EDB file you should try a professional EDB repair tool, this recovery application able to deal with all types of issues that corrupt a healthy EDB file. With the help of this tool you can restore emails, attachments, contacts, calendars, tasks, etc. from corrupt EDB files. It is packed with lots of features that make you able to deal with HOW TO SOLVE WHEN EXCHANGE DATABASE FAILS TO MOUNT WITH (HR=0X80004005, EC=-528) ERROR situation, through this you can repair, restores damaged EDB files and Saves as MS Outlook PST File. It also allows you to exports recovered mailboxes to Live Exchange Server and searching particular Mails in the repaired EDB file. You can easily save the recovered EDB as MSG, EML, HTML, RTF and PDF Files. It supports MS Exchange Server 2016 / 2013 / 2010 / 2007 / 2003 / 2000 and 5.5.

This recovery application allows anyone to repair their EDB database and get back their data because it is designed with easy to understand user interface, interface contained by this tool is packed with lots of graphical signs that make it very easy to use application. So, you don’t need to call any EDB professional in the manner to repair or recover your corrupt database. This recovery tool also doesn’t need any backup to repair your database; YES, it is true you don’t need a backup of your database to get your data back. So, try this application once and restore data from your EDB file.

Key Features of EDB Recovery Application

Repair a Damaged Exchange Server

The basic task of this recovery tool is to repair any severely corrupt Exchange database file (EDB) and recover the inaccessible mailboxes completely into a working PST file. After recovering you can easily import the PST files to your MS Outlook application and again access to all your mail components.

Restore Accidentally Deleted Mailboxes

This recovery tool is programmed with very strong algorithms that provide it very effective scanning technology, it becomes very useful in recovering and restoring the user mailboxes, which have been deleted accidentally.

It Automatically Generates Log Report of Entire Recovery Process

This recovery tool creates and allows user to save the complete log report of the whole recovery process. This Log Report contains the entire history of the recovery operation such as the path of the scanned EDB file, recovery Date & Time, recovered folders and more.

Very Compatible

This application supports various versions of MS Exchange that include the latest MS Exchange Server and Windows Operating System.

• Server Compatibility– MS Exchange Server 2016 / 2013 / 2010 / 2007 / 2003 / 2000 / 5.5
• Operating Systemcompatibility – Windows 8 / 7 / Vista / Windows Server 12 and 8

Additional features: You can search for the Particular Mails from Scanned EDB file and also recover data from Selective Mailbox Exchange, Saves the repaired Mailbox in PST Format, see the preview of recoverable User Mailboxes, Save and Load Scan Information and more.

Steps to fix EXCHANGE DATABASE FAILS TO MOUNT WITH (HR=0X80004005, EC=-528) ERROR

Step 1: Click on ‘open EDB File’ and choose the EDB file or to search the files you may click on ‘Find EDB File’.

Step 2: Select the MS Exchange Server type and click ‘Start’ button.

Step 3: Select the scanning types, ‘Quick Scan’ or ‘Extensive Scan’ and click ‘OK’.

Step 4: Recoverable file and folders are presented in the left panel; you may see the preview of the item by clicking.

Step 5: Now select the mailbox folders to recover and then click on the ‘Save mailboxes’ icon. Fill the destination drive or folder in a dialog box and click ‘OK’.

Step 6: And the selected Data will be recovered.

Manual trick to repair the corrupted edb files

If you are unable to access your edb database due to any error then it is sure you’re your edb database gets damaged. There are lots of tools available that can turn a dirty or damaged EDB file into a working database but it is recommended that try to restore data with the help of manual method before buying EDB recovery tool. Below manual trick to fix HOW TO SOLVE WHEN EXCHANGE DATABASE FAILS TO MOUNT WITH (HR=0X80004005, EC=-528) ERROR is given, apply them carefully and easily restore the lost data and other objects.

Configuring Gmail account to the Thunderbird is a good idea to repair the data

• Open the Thunderbird and go toTools–account settings– > click on Account Actions–Add Mail Account. Now, another mail account can be added to Thunderbird.
• Now enter new name, email address and password. Click on as IMAP radio button and click Done to save.
• At the left hand side, click on the Gmail account ID.
• In the Thunderbird, Gmail account has been configured and here, you can view all the email messages.

The above given trick is very helpful but sometime it get fails when the level of corruption is very higher or EDB database gets damaged deeply.

393 Total Views 2 Views Today