I have one PC that fails it's backup every now and then with this particular error:
Error EBAB03F1: The process cannot access the file because another process has locked a portion of the file.
This PC is backing up to an external drive, G:, and it runs successfully some of the times. Here's the latest series of entries in the Backup Exec System Recovery.log file:
12/3/2012 23:00:10 PM High Priority Info: Info 6C8F1F65: The drive-based backup job, * - Backup to G:, has been started automatically. 0x00 (Backup Exec System Recovery)
12/4/2012 0:47:38 AM High Priority Warning: 0x800706BA (Backup Exec System Recovery)
12/4/2012 0:47:38 AM High Priority Error: Error EC8F17B7: Cannot create recovery points for job: * - Backup to G:. Error E7D1001F: Unable to write to file.
Error EBAB03F1: The process cannot access the file because another process has locked a portion of the file. 0xE7D1001F (Backup Exec System Recovery)
(UMI:V-281-3215-6071)
I cannot figure out what is locking the file and I don't know what file is actually locked. I've been using a program called Processlock:
(http://windowsxp.mvps.org/processlock.htm) to try to figure out what has the file locked, but I need to provide the exact file name in order to do so. I've found a few Symantec knowledge base documents about this error, but they always reference backing up to a network share/admin share as the issue and this isn't the case here as this is a local external drive. Is there anywhere where I can find more detailed logging to see what file actually is being locked and therefore cannot be accessed? Thanks