CAN NOT UNLOCK FILEPRO RECORD

[Richard Kreiss]

Mark,

The two programs give more information than task manager but are not meant for the general public. 

Richard
Sent from my iPhone

> On Sep 24, 2021, at 3:37 PM, Fairlight via Filepro-list <filepro-list at lists.celestial.com> wrote:
> 
> Iarsn TaskInfo is my go-to.
> 
> That said, Task Manager will do the minimalistic job you describe, and
> it's built in.
> 
> m->
> 
> 
> On Fri, Sep 24, 2021 at 11:29:22AM -0400, Richard Kreiss via Filepro-list thus spoke:
>> There are two programs available from MS for Windows computers which can help locate a process and then kill it.  The first is process Explorer ands the second is Process monitor. These are free utilities
>> 
>> Richard Kreiss
>> GCC Consulting
>> 
>> 
>> 
>> -----Original Message-----
>> From: Filepro-list <filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com> On Behalf Of Nancy Palmquist via Filepro-list
>> Sent: Monday, August 9, 2021 3:38 PM
>> To: filepro-list at lists.celestial.com
>> Subject: Re: CAN NOT UNLOCK FILEPRO RECORD
>> 
>> I have seen this behavior on Windows Servers.  I don't recall seeing this on any *NIX system.  Usually stopping and dclerk or dreport process on that file will fix it.
>> 
>> On windows Server - a reboot was most reliable.  We even had trouble killing sessions when this happens.
>> 
>> Nancy
>> 
>>> On 8/3/2021 8:30 AM, Josh Reader via Filepro-list wrote:
>>> pkill -u <username>
>>> 
>>> This will kill all sessions for the specified user.
>>> 
>>> Josh
>>> 
>>> -----Original Message-----
>>> From: Filepro-list 
>>> <filepro-list-bounces+josh.reader=mercuryelectronics.com at lists.celesti
>>> al.com> On Behalf Of Jack Hagin via Filepro-list
>>> Sent: Monday, August 2, 2021 5:36 PM