Locked record
Richard Kreiss
rkreiss at verizon.net
Thu May 27 08:21:36 PDT 2010
Since I am not sure which process might be locking the record, it probably
would take a server reboot.
Thanks for the reply.
Richard
> -----Original Message-----
> From: Scott Walker [mailto:ScottWalker at RAMSystemsCorp.com]
> Sent: Thursday, May 27, 2010 11:15 AM
> To: 'Richard Kreiss'; filepro-list at lists.celestial.com;
fpsupport at fptech.com
> Subject: RE: Locked record
>
> Richard,
>
> Surely you know that a filePro "lockfile" has nothing to do with a locked
> record. Kill the process that has the record locked, or perhaps reboot
the
> server. Some process has the record locked. Can you kill that process?
>
> Regards,
>
> Scott
>
>
> -----Original Message-----
> From:
> filepro-list-bounces+scottwalker=ramsystemscorp.com at lists.celestial.com
>
[mailto:filepro-list-bounces+scottwalker=ramsystemscorp.com at lists.celestial.
> com] On Behalf Of Richard Kreiss
> Sent: Thursday, May 27, 2010 10:39 AM
> To: filepro-list at lists.celestial.com; fpsupport at fptech.com
> Subject: Locked record
>
> One of my clients called to say they had a record locked. This occurred
> last night when only one person was in the system. He exited the file and
> deleted the lockfile.
>
> When he checked again, the record was/is still locked. The message is
> waiting for record to be unlocked.
>
> Any suggestion on how or why this record should remain locked?
>
> Windows server 2008, FP 5.6.10, Win XP Pro.
>
>
> Richard Kreiss
> GCC Consulting
> rkreiss at gccconsulting.net
>
>
>
>
>
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
More information about the Filepro-list
mailing list