Transport Mail Database issues crashing Transport service

Question

We are experiencing frequent issues on Hub servers (as often as once a week) where Transport Mail DB issues crash the Transport service.  Had an MS specialist in the other day who could not exactly figure out the root cause.  The pattern usually is as follows:
1. Event ID 486 - This event refers to a failure to move a log file (associated with Transport Mail DB queues) because it is being used by another process.  What that process could be is unknown.
2. Event ID 413 - Unable to create a new logfile because the database cannot write to the log drive.
3. Event ID 492 - The logfile sequence in <dir> has been halted
4. Event ID 17019 - A database operation has encountered a I/O error. The Microsoft Exchange Transport service is shutting down. Exception details: Microsoft.Exchange.Isam.IsamLogWriteFailException: Failure writing to log file (-510)
Also followed by events 7001,1022,1002, and 1003.
Haven't been able to determine what is causing Event ID 486.  Not aware of any process that would be tying up the access to the log file.  These queue files are stored on a local disk, not a SAN. 
Any ideas as to what could be causing this?  Running E2K7SP1 Rollup 2 currently on all Exchange systems.

Answer 1

Hi,
I suggest that you use the following method to check which process access the log file indicated in the event 486:
Using Process Explorer
http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx
Then, we did the following:
1. Launch Process Explorer
2. Click Find, Find Handle or DLL
3. Enter the log name indicated in the event 486 and click Search
In addition, please also check whether any events such as 150004 occur before the Transport service crashes. If you notice the event, I also suggest that you refer to the following article:
http://technet.microsoft.com/en-us/library/bb201658(EXCHG.80).aspx
Mike