We recently had Transport service crashing on one of our Hub servers. The following events were logged in Event Log.

Event Type:     Error
Event Source:   ESE
Event Category: Logging/Recovery
Event ID:       455
Description:
edgetransport (2856) Transport Mail Database: Error -1811 (0xfffff8ed) occurred while opening logfile e:\Exchange\Queue\trn.log.
Event Type:     Error
Event Source:   MSExchangeTransport
Event Category: Storage
Event ID:       17005
Description:
Transport Mail Database: The database could not be opened because a log file is missing or corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required. The exception is Microsoft.Exchange.Isam. IsamMissingLogFileException: Current log file missing (-528)

We checked to confirm that the file E:\Exchange\Queue\trn.log was missing and there were only two log files (trn00605D42.log and trn00605D43.log) in the path. As per Microsoft TechNet, we moved the log files to another folder and tried starting Transport service – only this time to receive a new error. (However, a new e:\Exchange\Queue\trn.log file was created while the service was trying to start).

Event Type:     Error
Event Source:   MSExchangeTransport
Event Category: Storage
Event ID:       17005
Description:
Transport Mail Database: The database could not be opened because a log file is missing or corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required. The exception is Microsoft.Exchange.Isam.IsamDatabaseDirtyShutdownException: Database was not shutdown cleanly. Recovery must first be run to properly complete database operations for the previous shutdown. (-550)

Running ESEUTIL /mh e:\Exchange\Queue\mail.que confirmed that the database was in a ‘Dirty Shutdown’ state. ESEUTIL /P on a copy of mail.que seemed to have worked. So ran it on the original to resolve the issue.

– Thanks, Jinesh.

Advertisements