Fix Event ID 40013 in Exchange Server

Published On - June 11, 2026

Have you seen the following message:
“The tombstone table has reached an excessive number of entries and/or total size. A maintenance task has been dispatched to perform urgent cleanup.” Don’t know what it is & how to tackle it?

It is typically a warning message [or Event ID 40013 in Application log] that can become a serious operational concern if not addressed in time. Like,

Risk of database corruption.
Database performance degradation.
Random Exchange database dismounts.
Mailbox operations may become slower.
Increased resource consumption [additional CPU, memory, etc]

Tombstone Table & its Use Case in Exchange Server: Exchange creates a tombstone table to store records of deleted mailbox items & objects. The table remains available for synchronization, replication, & retention purposes.

But with time, the Exchange maintenance process removes the outdated tombstones. The problem arises when cleanup operations can’t keep pace with mailbox activity.

Know the Common Causes of the Event ID 40013

Look out for the factors that can contribute to excessive tombstone growth.

Large-scale mailbox cleanup operations.
Have an oversized Exchange Database.
Corruption within the Exchange database.
Retention policy configurations are misconfigured.
Poor server performance [Insufficient RAM, slow storage, etc.]

Quick Answers:

Backup operations & transaction logs truncation should be verified.

Exchange typically logs follow-up cleanup events after processing tombstone records. So, monitor it accordingly.

Check Exchange Server performance like CPU utilization, available memory, disk latency, etc., by performance monitor, task manager & resource monitor.

Fix Event ID 40013 in Exchange Server [Easy Ways]

Check out the following section to remove Event ID 40013 in Exchange Server manually. Follow the provided steps to avoid the risk of failure.

Way 1. Verify Exchange Services Health

Service health & event logs verification is a critical step to ensure Exchange databases are stable.

Run the command “Test-ServiceHealth” as an administrator while using the Exchange Management Shell. Make sure the RequiredServicesRunning column returns a “True” value.
Check application logs, system logs, & Exchange specific warnings and errors. It helps to catch underlying database or storage issues.

Way 2. Optimize Database Size & Distribution

In most cases, large mailbox databases cause multiple vulnerabilities, including maintenance complexity. But it can be managed by making some adjustments;

Distribute mailboxes across multiple databases.
Isolate users who send & receive a high volume of emails.
Set sensible, proactive storage limits to review mailbox quotas.
Logical constraints & proper whitespace reclamation can reduce the impact of Event ID 40013.

Way 3. Check Deleted Item Retention Settings

The long retention periods can directly affect your databases, recycle bins, & tombstone tables growth, which can significantly increase costs. So it is necessary to evaluate deleted item retention, mailbox retention policies, & recoverable items configuration. In short, create & configure retention policies as per your business requirements.

Way 4. Repair Exchange Database Corruption

If the Event ID 40013 still persists, there may be chances of database corruption. To handle such situations, go with this structured breakdown:

Analyze the database health first with the command “eseutil /mh”. The outcome can be either a Clean Shutdown [All is Well] or a Dirty Shutdown [It shows inconsistency that requires recovery].
The administrator should attempt soft recovery first if the database is inconsistent with the command “eseutil /r”.

Important to know: To handle severe Exchange database corruption without hassle, try our Recoveryfix Exchange Server recovery software. It provides quick & specific results while avoiding the risk of data loss.

Free Download

How to Prevent Event ID 40013 Issue?

Reduce the chances of the Event ID 40013 issue with simple efforts.

Ensure sufficient RAM, CPU, and storage.
Avoid excessive database growth.
Track Exchange Server performance continuously.
Prevent minor warnings from becoming major outages.
Align retention settings with organizational requirements.
Maintain database health & proper log management with backup.

End Thoughts: Fix Event ID 40013 in Exchange Server

Event ID 40013 is a warning that Exchange is struggling to manage the growth of its tombstone table. The suggested quick hacks & manual ways may reduce the impact of Event ID 40013 & restore its functionality. However, go with the advanced software if you want an easy resolution to a corrupt Exchange database. Download the tool to take a free trial now.

FAQs

Q- Does Event ID 40013 always imply a critical error?

A- It is typically logged as a warning. But its repeated occurrences may indicate hidden databases or performance issues.

Q- If I restart the Exchange, will it prevent the Event ID 40013 issue?

A- A restart may temporarily reduce symptoms, but it will not resolve the underlying cause of tombstone accumulation.

Q- How often should Exchange maintenance clean tombstone records?

A- Exchange performs online maintenance automatically that depends on database size, server performance & workload.

Q- Should I run ESEUTIL immediately after seeing Event ID 40013?

A- No. It should only be executed once you are confirmed that the cause is database corruption & you have taken a backup already.