Windows Event ID 1925 – MSExchange Store: Database Mount Failure or Corruption

Start by examining the complete error details and database status to understand the scope of the issue.

1. Open Event Viewer → Applications and Services Logs → Microsoft → Exchange → MailboxDatabaseFailureItems

2. Locate Event ID 1925 and note the specific error code and database name in the event description.

3. Launch Exchange Management Shell as administrator and check database status:

Get-MailboxDatabase | Select Name, Mounted, DatabaseSize, LastFullBackup

4. Check the specific failed database status:

Get-MailboxDatabase "DatabaseName" | Format-List *

5. Review recent Application log events for related errors:

Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName='MSExchange*'; Level=2} -MaxEvents 50 | Where-Object {$_.TimeCreated -gt (Get-Date).AddHours(-24)}

6. Document the error code, affected database, and any accompanying ESE or MSExchange Database events for further analysis.

Ensure adequate storage space and verify the integrity of the underlying storage subsystem.

1. Check available disk space on all Exchange database and log drives:

Get-WmiObject -Class Win32_LogicalDisk | Select DeviceID, @{Name="Size(GB)";Expression={[math]::Round($_.Size/1GB,2)}}, @{Name="FreeSpace(GB)";Expression={[math]::Round($_.FreeSpace/1GB,2)}}, @{Name="%Free";Expression={[math]::Round(($_.FreeSpace/$_.Size)*100,2)}}

2. Verify database and log file paths are accessible:

Get-MailboxDatabase | ForEach-Object { Test-Path $_.EdbFilePath; Test-Path $_.LogFolderPath }

3. Check for disk errors using CHKDSK on database drives:

chkdsk E: /f /r

4. Examine Windows System log for storage-related errors:

Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='disk','Ntfs','volsnap'; Level=2,3} -MaxEvents 20

5. If using SAN storage, verify connectivity and check SAN management tools for path failures or performance issues.

6. Ensure Exchange service account has full control permissions on database and log directories.

Try Exchange's built-in recovery mechanisms before resorting to more aggressive repair methods.

1. Stop the Microsoft Exchange Information Store service:

Stop-Service MSExchangeIS -Force

2. Navigate to the database log directory and check for uncommitted transaction logs:

Get-ChildItem "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\DatabaseName\" -Filter "*.log" | Sort-Object LastWriteTime

3. Run ESEUTIL to check database state:

eseutil /mh "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\DatabaseName\DatabaseName.edb"

4. If the database is in "Dirty Shutdown" state, attempt soft recovery:

eseutil /r E00 /l "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\DatabaseName\" /d "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\DatabaseName\"

5. Start the Exchange Information Store service:

Start-Service MSExchangeIS

6. Attempt to mount the database:

Mount-Database "DatabaseName"

7. Monitor the Application log for successful mount confirmation or additional error details.

Use ESEUTIL to perform comprehensive database integrity verification and repair if corruption is detected.

1. Ensure the Exchange Information Store service is stopped and create a backup copy of the database:

Stop-Service MSExchangeIS -Force
Copy-Item "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\DatabaseName\DatabaseName.edb" "C:\Backup\DatabaseName_backup.edb"

2. Run ESEUTIL integrity check to identify corruption:

eseutil /g "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\DatabaseName\DatabaseName.edb" /v

3. If corruption is found, run database repair (this process can take several hours):

eseutil /p "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\DatabaseName\DatabaseName.edb" /t "C:\Temp\repair.edb"

4. After repair completion, run defragmentation to optimize the database:

eseutil /d "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\DatabaseName\DatabaseName.edb" /t "C:\Temp\defrag.edb"

5. Verify the repaired database integrity:

eseutil /g "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\DatabaseName\DatabaseName.edb"

6. Start Exchange services and attempt database mount:

Start-Service MSExchangeIS
Mount-Database "DatabaseName"

When repair attempts fail, restore from backup or create a recovery database to extract mailbox data.

1. If recent backups are available, restore the database using your backup solution following vendor-specific procedures.

2. For Exchange Native Data Protection or third-party backup restoration, ensure Exchange services are stopped during the restore process.

3. If backups are unavailable or outdated, create a recovery database to extract data from the corrupted database:

New-MailboxDatabase -Name "RecoveryDB" -Server "ExchangeServer" -EdbFilePath "C:\Recovery\RecoveryDB.edb" -LogFolderPath "C:\Recovery\Logs" -Recovery

4. Copy the repaired database file to the recovery database location and mount it:

Copy-Item "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\DatabaseName\DatabaseName.edb" "C:\Recovery\RecoveryDB.edb"
Mount-Database "RecoveryDB"

5. Extract mailbox data using recovery database cmdlets:

Get-MailboxStatistics -Database "RecoveryDB"
New-MailboxRestoreRequest -SourceDatabase "RecoveryDB" -SourceStoreMailbox "UserMailbox" -TargetMailbox "user@domain.com" -TargetRootFolder "Recovered Items"

6. Monitor restore progress and verify data integrity:

Get-MailboxRestoreRequest | Get-MailboxRestoreRequestStatistics

7. After successful data recovery, remove the recovery database and restore normal operations with a new database or restored backup.