John
Martoccio wrote:
I have had this happen a few times to me, and what I do is this:1) Stop SCSMFILTER2) Run TLIST looking for Tr_Finder, TrashFinder threads still running and try to shut them down with STOP or KILL, (and finally KILL /F) commands.3) Open Regedit goto: HKLM\Software\AXE\Trash-FinderIf you will see a $LOCK key (folder). I just delete that, and then I am able to re-run the Trashfinder again.Restart SCSMfilter....I have also been successful in just deleting the $LOCK key without doing the rest.... but I have no idea what that does with the current running sessions.If Randy has a better method, it might be best to check with him !That's the best way to fix that problem. Usually, the threads are just waiting for the lock to be freed, so there is no problem just killing the lock. But the belt-and-suspenders approach is going to work fine no matter what.I've got a note to look at this problem; I haven't had it happen to me much, but it is nasty when it does happen. The problem is that a lock is a lock; a lock that purposely doesn't work part of the time is potentially a trouble spot.As always try at your own risk, I am not taking responsibility for anything that happens as a result of this information !Nothing risky about your procedure; it's exactly what needs to be done. It's mentioned in the Troubleshooting section of the TF help file (not sure when I added that though; it might not be mentioned in the Classic version). I do realize that Reading The Fine Manual is something that most of us don't try unless we've exhausted all other possibilities. :-)Randy.
