Tom,

There may be a SO01<batch no>.LCK file in the MAS90\LOCK\_<company code> folder that is still locked.  MAS90 locks a batch by locking that file.

Natasha

thanks!

Natasha,

We are in this same situation now, but our batch has a status of "Print/Update." I see the lock file (SO0103697.LCK). What am I supposed to do with it? Delete it? Rename it? I am prevented from doing either; a message pops up saying that the action cannot be completed because the file is open in another program. Right now, I am assuming that I will be able to delete or rename it at the end of the day when everyone exits MAS 200 (v. 4.4). Thanks for any advice you can give us!

You can use MS Process Explorer to find the process holding that file open.

Steve

MAS200 V4.30.21

Thanks, Steve. I installed Process Explorer on my workstation, but how would I use it to find the process holding the file open when the file is on the server?

Use the "Find" feature. You can "find" a filename with the search button. Search for the lock file. The results will show the PID, and you can use task manager to kill the task.

Steve

MAS200 V4.30.21

Ooops! You want to run Process Explorer on the server...

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.

Interesting. The process must have released the file for you to be able to do that.

Safe & happy 4th!

Steve

MAS200 V4.30.21

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.