locked file(s)... And useful --- UNLOCKER application

Reggie Freedman BS rdfreedman at bellsouth.net
Wed Apr 11 09:17:32 PDT 2012


F Y I...

Way, way back when, I created a batch script to automated a nightly export 
of an accounting application's databases (handled / controlled by Pervasive 
10.x) to corresponding files in filePro as name(s).txt on a Windows 2008 
server. After the exports, the script continues to run dxmaint on each 
exported file (example: dxmaint bkarcont -rf 1,10:7,1,d -oa -e) and indexes 
all applicable automatic indexes. I index in reverse order... D C B A. If I 
should be watching the script run, I know index.A is the last one before the 
script moves down the list to the next file.

This exercise is necessary to create custom reports such as list of 
customers who purchased a group of products for one manufacturer and who 
will then qualify and receive a $50.00 gift gas card if purchases of the 
qualifying product group totals more than $2,500 for the month. The 
accounting package cannot do this level of detail / selection.

For some time I've experienced dxmaint to recreate most, but not all, 
automatic indexes (around 20MB in size) in the larger exported filePro files 
(file size of 130MB and 600,000 line items). Recently filePro simply freezes 
on a specific file. I found this was to a bad index.c. Deleting index.c and 
recreating it fixed this problem. This fixed the specific freeze problem but 
not the locked file problem. Also nothing to do with filePro's own lockfile.

Restarting the server fixed the issue, the script runs without crashing. 
I.e., all filePro indexes will rebuild. The exports have always completed. 
Rebuilding filePro indexes and zipping these files nightly has not always 
worked. Restarting the server nightly (resetting Windows) before running the 
script is not acceptable.

This problem began some months ago. Maybe a windows update or ? This week, I 
added some pauses into the batch script to identify where / when the problem 
occurred. Looking at running processes, etc., nothing showed: no open files, 
no open sessions, no users connected, etc. I Googled and found an 
interesting application at http://www.filehippo.com/download_unlocker/

snip...........................
If you've ever been unable to delete a file in
Windows, and can't figure out what program's
using it, Unlocker is the solution. Have you
ever seen these Windows error messages?

    Cannot delete folder: It is being used
         by another person or program
    Cannot delete/copy file: Access is denied
    There has been a sharing violation.
    The source or destination file may be in use.
    The file is in use by another program or user.
    Make sure the disk is not full or
         write-protected and that the file
         is not currently in use.

Unlocker can help! Simply right-click the folder
or file and select Unlocker. If the folder or
file is locked, a window listing of lockers
will appear. Simply click Unlock All and you
are done!
..........................snip end

When I right clicked the bkarcont.txt and selected Unlocker (which I had 
installed) it showed bkarcont.txt was locked by four instances of rreport. 
Clicking unlock, fixed the locked bkarcont.txt and dxmaint ran ok. Being 
unlocked, nightly backup's copied filePro name(s).txt files.

Since then, while troubleshooting windows and apps, I have use Unlocker 
several times to unlock, move or rename .dll's, .ini's etc.,. Wish I had 
discovered this jewel years ago! Maybe Unlocker would be useful to you. It's 
freeware too!

I have no answer to why rreport shows as the locking app. Rreport is run 
last, after automatic indexes are recreated, to update another filePro file 
with information such as last purchased date, contact or address change, YTD 
purchases, etc. If one of the name(s).txt files is accessed and is locked 
this scripted rreport update processing fails too.

I would not know of the locked file(s) till the next day and then only if I 
looked as these files are not for general use by anyone. Seeing four 
instances of locker rreport simply could be four days passed by the time I 
looked or since rebooting the server. This is not always happening. I looked 
today and no problem. Over a week has passed since I discovered and 
unlocked. Weird. I am aware this has been happening for some time and I have 
no idea why.


Reggie Freedman
CPI of South Florida, Inc.
954 562-6727 (cell)
DamnComputer.com



More information about the Filepro-list mailing list