Hi Guys, Our exchange database backup has been failing recently because of a single log file which seems to have become corrupted. If i try to open the log file i get 'Access is Denied' This error is logged on my exchange server: "Information Store (3640) First Storage Group: An attempt to delete the file "E:\Exchange\Logs\E00160E0.log" failed with system error 5 (0x00000005): "Access is denied. ". The delete file operation will fail with error -1032 (0xfffffbf8)." My backup will not complete because this dam log file is broken!! I have read this article http://support.microsoft.com/kb/248122. I have used eseutil before but never for a log file. You need to dismount the databases before running it right??? Any help would be greatly appreciated. thanksWhen i run eseutil /ml on the affected log i get this:D:\Program Files\Exchsrvr\bin>eseutil /ml e:\exchange\logs\e00160e0.logMicrosoft(R) Exchange Server Database UtilitiesVersion 6.5Copyright (C) Microsoft Corporation. All Rights Reserved.Initiating FILE DUMP mode... Base name: e00 Log file: e:\exchange\logs\e00160e0.log ERROR: Cannot open log file. Error -1032.Operation terminated with error -1032 (JET_errFileAccessDenied, Cannot access file, the file is locked or in use) after 11.15 seconds.However it works with any other log file, without the databases being detached... any ideas?

Clarify: Backup failed, one log cant be accessed, right? Troubleshooting: 1. Is there any error info in the application log? 2. All transaction logs, STM, EDB and other exchange related directories have been excluded from AV scan, right? [Refer to File-Level Scanners section in KB 328841] 3. Try to schedule timing to dismount database [DB] and clear transaction log files in case theres unexpected issue for the DB corruption Notes: It will be downtime for product environment! a. Dismount all DBs in the storage group which the infected transaction log is located b. Make sure all DBs is clean shutdown Cd EseutilToolPath Eseutil /mh Full EDB file path Check State c. Clear all transaction logs and checkpoint files to other place d. Remount all DBs, check transaction log files directory. New transaction logs shall start to be generated, and then you can backup again