Information:
Delete FXP Files Classic/2007 may not be able to delete files under certain situations. These known situations (and how to address them) are:

• The Administrator has been specifically denied access to a particular object. This is the most common cause of "Access Denied" errors when trying to delete the object.
  • Use the "Take Ownership" functionality of the application to regain ownership of the object and then try to delete it again.
    
• The object is being used by another process. This often results in "The process cannot access the file because it is being used by another process" or "The process cannot access the file because another process has locked a portion of the file" errors, but can sometimes result in "Access Denied" errors as well.
  • The solution here is to find out what processes are using the object and then stop those processes.  Using the Delete On Reboot (DOR) functionality will usually help here.  Note that you must delete all of a directory's contents before using DOR on a directory. The Process Finder feature, available in Professional/Standard Edition and above, can determine what processes are using a file or folder/path.
    
• Under very rare situations, the permissions information for an object (its metadata) may have been corrupted. Running chkdsk will usually fix any problems like that. A good time to schedule chkdsk is right before you reboot after using the DOR functionality to try to delete some files. When chkdsk does not solve the corruption problem, turn to Disk Explorer, which has resolved many corruption scenarios like this.  Seeing any of the following (illegal) characters like / \ : * ? " < > | in a filename is a good indication that you have real disk corruption - those characters are reserved and have special meanings.