We are experiencing frequent issues on Hub servers (as often as once a week) where Transport Mail DB issues crash the Transport service. 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. Event Type:ErrorEvent Source:ESEEvent Category:General Event ID:486Date:2/17/2009Time:8:55:21 AMUser:N/AComputer:DSVPWM10Description:edgetransport (7064) Transport Mail Database: An attempt to move the file "D:\exchange\TransportRoles\data\Queue\trn00093CEF.log" to "D:\exchange\TransportRoles\data\Queue\trntmp.log" failed with system error 2 (0x00000002): "The system cannot find the file specified. ". The move file operation will fail with error -1811 (0xfffff8ed). For more information, click http://www.microsoft.com/contentredirect.asp. Event Type:ErrorEvent Source:ESEEvent Category:Logging/Recovery Event ID:413Date:2/17/2009Time:8:55:29 AMUser:N/AComputer:DSVPWM10Description:edgetransport (7064) Transport Mail Database: Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1811. For more information, click http://www.microsoft.com/contentredirect.asp. Event Type:ErrorEvent Source:ESEEvent Category:Logging/Recovery Event ID:492Date:2/17/2009Time:8:55:29 AMUser:N/AComputer:DSVPWM10Description:edgetransport (7064) Transport Mail Database: The logfile sequence in "D:\exchange\TransportRoles\data\Queue\" has been halted due to a fatal error. No further updates are possible for the databases that use this logfile sequence. Please correct the problem and restart or restore from backup. For more information, click http://www.microsoft.com/contentredirect.asp. Event Type:ErrorEvent Source:MSExchangeTransportEvent Category:Storage Event ID:17019Date:2/17/2009Time:8:55:29 AMUser:N/AComputer:DSVPWM10Description:Transport Mail Database: 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) at Microsoft.Exchange.Isam.?A0xf73de38c.HandleError(Int32 err) at Microsoft.Exchange.Isam.Interop.MJetCommitTransaction(MJET_SESID sesid, MJET_GRBIT grbit) at Microsoft.Exchange.Transport.Storage.Transaction.Commit(TransactionCommitMode mode) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.We are using theUpdate Rollup 5 for Exchange Server 2007 Service Pack 1Some one has suggested solution in the below URL, but that is not clear.http://social.technet.microsoft.com/Forums/en-US/exchangesvrtransport/thread/c8819ef0-5a62-4b79-9b3d-bf4df9864fa3/?ffpr=0Please suggest.ThanksFunnyghost

Hi,Please check if Antivirus is not causing the issue. This can be done by first switchting off the antivirus product is this fixes your issue then exclude the database folders from the Antivirus directory.Also try the solution mentioned by Mike: 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 Regards,Johanblog: www.johanveldhuis.nl

1. Launch Process Explorer 2. Click Find, Find Handle or DLL 3. Enter the log name indicated in the event 486 and click SearchI did the steps, you have mentioned. Then how can I proceed further?Funnyghost

Hi,Are there any results found by the process explorer ?Regards,Johanblog: www.johanveldhuis.nl

Yep, I got the below one;Process PIDTypeHandle or DLLEdgeTransport.exe12260HandleD:\exchange\TransportRoles\data\Queue\trntmp.logFunnyghost

Dear FunnyGhost, From your post, I understand that the Transport service crash as often as once a week on Exchange server 2007. And you have installed Update Rollup 5 for Exchange Server 2007 Service Pack 1. Base on my research, many reasons can cause the issue. such as antivirus software, disk error, backup job. You can try the following steps to fix the issue: 1. Check whether you install antivirus software on your Exchange server, if so, please refer to the following article to configure it; File-Level Antivirus Scanning on Exchange 2007 http://technet.microsoft.com/en-us/library/bb332342.aspx 2. Check whether the disk that queue database reside in has bad section? If so, try to replace the disk and move the queue database to the new location, 1. Stop the MS Exchange Transport Service. 2. Move the Queue Database and Transaction Logs to the new location, for instance D:\Queue. 3. Open the EdgeTransport.Exe.Config file via text editor such as Notepad.exe. 4. Modify the QueueDatabasePath and QueueDatabaseLoggingPath as appropriate: <add key="QueueDatabasePath" value = "D:\Queue" /> <add key="QueueDatabaseLoggingPath" value = "D:\Queue" /> 5. Restart the MS Exchange Transport Service. Note: The QueueDatabasePath and DatabaseLoggingPath cannot point to the root of a directory, such as C:\ or D:\, these files MUST be in a subdirectory. 3. Check whether you install third party software on your Exchange server, if so, uninstall them, 4. Check whether you enable backup job on your Exchange server, if so, disable them, Also, please collect the following information for further analyze. l Did the issue occur regularly or randomly? l Collect application log file and send it to v-rocwan@microsoft.com. a) On Hub Transport server, open Event Viewer, navigate to application and right click it, cleanup it; b) Open EMS, run the following command : Get-EventLogLevel MSExchangeTransport | set- EventLogLevel level expert c) Wait for the issue occur, d) Save the new application log as .evtx or .evt file and send it to me for analyze. If anything is unclear, please feel free to let me know. Regards, Rock Wang - MSFT