Thanks. At the end of the day, I was able to rename the lock file with a BAK extension. Then, when I went into Daily Sales Reports/Updates to reset the status on that batch, I found that I didn't need to. It was already marked as Available and was enabled to be selected.

I know this is old, but I am just putting a note here for future benefit of others.  Sometimes these errors occur as a result of a crash on the comptuer that was processing the batch.  When this happens, there may be a task open that you would see in Master Console that is associated with the register that in Print/Update status.  This process might have to be terminated in Master Console to release the LOCK file.  That happened to me today and killing the task after confirming the user was fully logged out solved the problem and got rid of the lock file.  Prior to that, the LOCK file was in use and could not be moved or renamed.

I know this is old, but I am just putting a note here for future benefit of others.  Sometimes these errors occur as a result of a crash on the comptuer that was processing the batch.  When this happens, there may be a task open that you would see in Master Console that is associated with the register that in Print/Update status.  This process might have to be terminated in Master Console to release the LOCK file.  That happened to me today and killing the task after confirming the user was fully logged out solved the problem and got rid of the lock file.  Prior to that, the LOCK file was in use and could not be moved or renamed.