Troubleshoot Exchange Replica Inconsistent Error 30146 in DPM

Applies to: System Center Data Protection Manager 2025 / 2022 / 2019 | Exchange Server 2019 / 2016 / 2013

Data Protection Manager (DPM) can report an Exchange mailbox database replica as inconsistent when a consistency check fails. One common cause is a version mismatch between eseutil.exe and ese.dll on the Exchange server and the DPM server, especially after an Exchange update.

Error ID 30146 is a general data consistency verification failure, so it should not automatically be treated as an Eseutil mismatch. Check the accompanying error details and event logs before applying the fix.

In This Article

• 1. Symptom
• 2. Why the Eseutil Version Matters
• 3. Compare the File Versions
• 4. Update the Files on the DPM Server
• 5. Run the Consistency Check Again
• 6. Other Causes of Error ID 30146
• 7. Key Takeaways

1. Symptom

DPM reports the Exchange data source as inconsistent and new recovery points cannot be created until the consistency problem is resolved. A typical message includes:

Data consistency verification check failed for LOGS of Exchange Mailbox Database on the Exchange server. Error ID: 30146.

The exact hexadecimal error value can vary. Treat the full error details and the Exchange and DPM event logs as part of the diagnosis.

2. Why the Eseutil Version Matters

DPM uses Exchange database utilities during consistency checking. Microsoft requires the versions of eseutil.exe and ese.dll on the DPM server to match the Exchange server being protected.

If Exchange is updated but the copies on the DPM server are not updated, consistency checks can fail. Microsoft also documents Error ID 30217 specifically for an Eseutil version mismatch.

3. Compare the File Versions

Compare eseutil.exe and ese.dll on the Exchange server with the copies in the DPM installation folder. The following example uses common installation paths; adjust the DPM path if your installation is different.

$ExchangeBin = "C:\Program Files\Microsoft\Exchange Server\V15\Bin"
$DpmBin      = "C:\Program Files\Microsoft System Center\DPM\DPM\bin"

Get-Item "$ExchangeBin\eseutil.exe","$ExchangeBin\ese.dll" |
    Select-Object Name,@{N="FileVersion";E={$_.VersionInfo.FileVersion}}

Get-Item "$DpmBin\eseutil.exe","$DpmBin\ese.dll" |
    Select-Object Name,@{N="FileVersion";E={$_.VersionInfo.FileVersion}}

$ExchangeBin = "C:\Program Files\Microsoft\Exchange Server\V15\Bin"
$DpmBin      = "C:\Program Files\Microsoft System Center\DPM\DPM\bin"

Get-Item "$ExchangeBin\eseutil.exe","$ExchangeBin\ese.dll" |
    Select-Object Name,@{N="FileVersion";E={$_.VersionInfo.FileVersion}}

Get-Item "$DpmBin\eseutil.exe","$DpmBin\ese.dll" |
    Select-Object Name,@{N="FileVersion";E={$_.VersionInfo.FileVersion}}

The file versions should match for the Exchange version that DPM is protecting.

4. Update the Files on the DPM Server

If the versions do not match, copy the current eseutil.exe and ese.dll from the Exchange Server Bin folder to the DPM Bin folder.

• Exchange: C:\Program Files\Microsoft\Exchange Server\V15\Bin
• DPM: <DPM installation folder>\Bin

Update both files together. If Exchange is updated again later, recheck the DPM copies so that the versions remain aligned.

5. Run the Consistency Check Again

After the files are aligned, return to DPM Administrator Console and run a synchronization with consistency check for the affected Exchange data source. If the version mismatch was the cause, the replica should return to a consistent state and protection jobs can resume.

6. Other Causes of Error ID 30146

Error ID 30146 is not specific to Eseutil version mismatch. Microsoft documents other causes, including missing or damaged Exchange log files. Antivirus software on the DPM server can also cause this condition if it scans or removes protected log files.

If the file versions already match, check the DPM and Exchange event logs at the time of the failure, verify the Exchange log chain, and review antivirus exclusions before replacing files unnecessarily.

7. Key Takeaways

• Error ID 30146 means the DPM consistency check failed, but it does not identify a single root cause.
• Keep eseutil.exe and ese.dll on the DPM server aligned with the protected Exchange server.
• After an Exchange update, recheck the copies on the DPM server.
• If the versions already match, investigate Exchange logs, DPM logs, and antivirus activity before changing anything.

References

• Microsoft Learn – Back up Exchange with DPM
• Microsoft Learn – Troubleshoot Exchange protection and recovery issues in DPM
• Microsoft Learn – DPM error codes

Ceyhun Kirmizitas

Cloud and infrastructure professional with nearly two decades of experience in enterprise IT environments, spanning public cloud, private cloud, and hybrid architectures.