Exchange EDB Guides

Exchange Database Won't Mount Find the ec code in the mount error, match it to its cause and apply the fixes in order

Leena Taylor Paul By Updated October 21, 2026 8 min read

Exchange database won't mount errors end with an ec= number that names their cause.

Match that number to the table below. Free space and locks come first, then soft recovery. Hard repair waits until a spare copy of the .edb has given up its mail.

Log errors-528, -543, -550
Disk and lock errors-1022, -1032, -1808
Page and match errors-1018, -1216

Users get no mail when an Exchange database won't mount. Error text is a wall of words, with a short number after ec= buried inside it.

Find that number first and you skip an hour of guessing. Eight codes below match eight causes, from missing logs to a full disk.

Where do You Find the Error Code in a Mount Failure?

Exchange database won't mount messages end with an ec= value, the ESE error code. Use Exchange Management Shell so you see the full message.

Mount-Database DB01

Failed to mount database "DB01". Error: An Active Manager operation failed.
... Unable to mount database. (hr=0x80004005, ec=-528)

Here ec=-528 is the code. Open ESE events in the Application log next. Microsoft says they carry specific reasons and error details, per The log disk is full.

Check services too. Start Microsoft Exchange Replication plus Microsoft Exchange Information Store before you retry Mount-Database. Microsoft says the cmdlet mounts a database only when both services are started.

“Read the number after ec= before you read any forum thread. It tells you if the fight is about disk space, logs or damage.”

Nick Rogers, Founder of Univik

What do Common Exchange Mount Error Codes Mean?

Exchange database won't mount cases come down to eight ESE codes, from missing logs to a full disk. Microsoft lists names and values in Extensible Storage Engine Error Codes.

Code ESE name What it means First fix
-528 JET_errMissingLogFile Mount finds no current log file Find or restore the log, then eseutil /r
-543 JET_errRequiredLogFilesMissing Required logs absent, recovery cannot start Find the logs or restore a backup
-550 JET_errDatabaseDirtyShutdown Database was not shut down cleanly Soft recovery using eseutil /r
-1216 JET_errAttachedDatabaseMismatch Attachment info disagrees with the database file Match database to its own logs
-1018 JET_errReadVerifyFailure Database page fails its checksum Check storage, then restore or save mail
-1022 JET_errDiskIO Disk I/O error Fix the disk or storage path
-1032 JET_errFileAccessDenied Another process has the file open Stop scans and backups on that folder
-1808 JET_errDiskFull No space left on disk Free space, then mount again

Jet error -528, -543 and -550 belong together because all three involve logs or a dirty shutdown. Log replay has its own guide in Exchange Database Dirty Shutdown.

For the file not found error, see Exchange Jet Error -1811. Page checksum failures sit in Exchange Jet Error -1018.

What is the Fix Order for a Database That Won't Mount?

Exchange database won't mount fixes start with free space and locks, then soft recovery, then a hard repair. Steps cost more as the list goes on.

1
Free space and locks
Free disk space on log and database drives. Pause backups and put .chk, .log and .edb on your antivirus skip list, in line with Anti-Virus Software in the Operating System on Exchange Servers.
2
Check the header
Use eseutil /mh on a dismounted file to view its header. In Eseutil /M File Dump Mode, Microsoft documents /mh as a dump mode that neither repairs nor changes files. Note State and Log Required range.
3
Soft recovery
Use eseutil /r from the folder that contains your logs to replay them into the database. Microsoft says soft recovery assumes no database or log files were moved, deleted or destroyed, per Eseutil /R Recovery Mode.
4
Restore
Restore your newest good backup. Replay newer logs after it.
5
Save the mail
Open your copy offline and export needed mailboxes with Univik Software.
6
Hard repair a copy
Point eseutil /p at a copy only. Microsoft says repair invalidates previous backups, so take a full backup straight after, per How to Run Eseutil /P (Repair).

Steps 5 and 6 swap places only when nobody needs mail on damaged pages. Before You Run Eseutil /p lists what a hard repair deletes.

Why does Exchange Say Logs do Not Match a Database?

Error -1216 flags a database file that is absent or differs from its attachment info. Exchange then says its logs do not match the database.

When one database is no longer available, for example after a destroyed disk, -1216 can strike all databases in its storage group at once, Microsoft says in Reference for Common Eseutil Errors.

Compare Log Required range in eseutil /mh with log file names you have. Treat a gap in that range as missing logs.

Why will a Database in Clean Shutdown Not Mount?

Databases in Clean Shutdown fail to mount because a block sits outside the file. In Reference for Common Eseutil Errors, Microsoft calls these databases independent of log files.

Cause Sign Fix
File replaced from a backup or another disk Mount refuses a file that does not match its Active Directory entry Set AllowFileRestore to $true
Path or name differs from database entry No file sits at the EdbFilePath Exchange expects Put file at that exact path and name

Show expected paths, allow a replaced file and mount. Set-MailboxDatabase documents AllowFileRestore for Exchange 2010 and later.

Get-MailboxDatabase DB01 | Format-List EdbFilePath,LogFolderPath
Set-MailboxDatabase DB01 -AllowFileRestore $true
Mount-Database DB01

Move logs once eseutil /mh reports Clean Shutdown. Microsoft tells you not to delete log files while a database sits in dirty shutdown, per The log disk is full.

How do You Reach Your Mail While a Database is Down?

When an Exchange database won't mount, duplicate the .edb plus its logs onto another disk, then open that duplicate offline.

Exchange EDB Converter from Univik handles a dismounted .edb on Windows without Exchange Server or Outlook. Univik Software applies logs found beside your .edb to a scratch copy, the same replay step eseutil /r performs.

Univik Software stages dirty or locked files in a scratch folder first, so keep 256 MB free there beyond the database size.

Start screen with options to open an EDB file with or without logs
In the app. Choose Open an EDB file. Add a log folder to replay logs found there.
Point Eseutil repair, then mount Univik Software
Live Exchange server required Yes No
Opens a dismounted .edb After recovery or repair Yes
Source file Changed by repair Copy used, source unchanged
Message preview before export No Yes, message by message
Cost Free From $99 for 2 PCs
Trial Free 10 messages per folder

With mail saved, a failed repair costs server time and no email. How to Convert EDB to PST covers export steps.

Key Takeaways
  • When an Exchange database won't mount, the ec= number names the cause.
  • Codes -528, -543 and -550 point to missing logs or a dirty shutdown.
  • Codes -1022, -1032 and -1808 point to disk, lock and space problems.
  • Error -1018 means a damaged page. Error -1216 means a database and logs that do not match.
  • Copy the .edb with its logs before recovery. Save mail before a hard repair.
Open the Database That Won't Mount

Browse the mailbox tree of a failing .edb in Univik Software before you repair anything. Trial edition saves 10 messages per folder. Licences start at $99 for 2 PCs.

Free Download See all features

Questions About Exchange Mount Errors

What does hr=0x80004005 mean in the mount error?

0x80004005 is the unspecified failure code Windows returns. Look at the ec= value beside it, because that value names the ESE error.

Can a full log drive stop a database from mounting?

Yes. Microsoft documents that the storage group goes offline and its databases dismount once an Exchange 2007 log disk fills, per The log disk is full. Make room on your log drive, then mount the database again.

Can eseutil /r fix a database stuck in dirty shutdown?

Yes, for a dirty shutdown when all the logs are present. Microsoft says soft recovery replays committed transactions and reverses incomplete ones, per Eseutil /R Recovery Mode.

Can antivirus stop an Exchange database from mounting?

Yes. Microsoft says antivirus file scans can lock or quarantine a log or database file while Exchange uses it. Tell your scanner to skip the extensions .edb, .log and .chk plus database folders, as Microsoft advises in Anti-Virus Software in the Operating System on Exchange Servers.

Is my mail lost when a database will not mount?

No. Mail lives in the database file and in its logs. Recovery brings it back. Univik Software opens that file offline with no mount.

Can I mount the database on another server?

Yes, as a recovery database, but only for Exchange 2016 and later files. Microsoft does not support earlier mailbox databases there. Recovery databases in Exchange Server adds that a Mailbox server mounts one recovery database at a time. See Exchange Recovery Database for the limits.

Does Mount-Database -Force fix a failed mount?

No. Microsoft says Force hides warning and confirmation messages and overrides errors or warnings found during the mount, per Mount-Database. Missing logs still need a backup restore or a repair, as Reference for Common Eseutil Errors explains for error -543.

Can you open an .edb offline after a failed mount?

Yes. Whether your .edb is dirty or dismounted after a failed mount, Univik Software opens it offline on Windows. Exchange Server and Outlook play no part.

Leena Taylor Paul

Leena Taylor Paul covers Exchange mount errors for the Univik team, which has shipped Windows mail tools since 2013. Last checked October 2026. Contact our support team if a database still will not mount.

More Exchange EDB Guides

All Univik guides for Exchange mailbox databases, grouped by what you need to do next.