locked record
Richard Kreiss
rkreiss at gccconsulting.net
Mon Jan 5 14:57:45 PST 2015
Nancy,
Thanks for your reply. My client usually has to reboot the database server which requires getting his office staff off as well as those using remote login to their IIS server with RDP.
As you indicate there are really no tools for seeing who has this lock on the file as it was initiated on a client computer connected to the database server either with a direct login or through the RDP server and exists even when the client is disconnected or has logged off.
If they can operate with the particular record locked, they will wait until just after mid-night to reboot. This is when everyone is off the system and not tasks are scheduled to run.
This is one reason a *nix system is easier to administer. :)
Richard
> -----Original Message-----
> From: Filepro-list [mailto:filepro-list-
> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Nancy
> Palmquist
> Sent: Monday, January 05, 2015 11:29 AM
> To: filepro-list at lists.celestial.com
> Subject: Re: locked record
>
> Richard,
>
> I have had issues with Record Locks on Windows Computers that are System
> Errors and like you said, no sessions are open and no file locks are listed in
> the system logs. The Windows System has a portion of the file locked and
> has forgotten why and who locked it. I don't think filepro can deal with this
> kind of lock properly or is left with no knowledge of the lock existing.
>
> This is some kind of Windows issue and I have found it is fastest to just
> reboot the server. I have never found any Administration tool that will
> release the lock. Even getting all users out by logging out and closing sessions
> does not work.
>
> I have seen this on Win XP, Win7 and Windows Server versions. Not often,
> but often enough to be something I check for when the filepro locking has
> been released and users have been reviewed in Computer Management on
> Windows Administration.
>
> I assume that some broken session has left Windows with a file lock and no
> way to unlock it properly.
>
> Nancy
>
>
> On 12/19/2014 3:10 PM, Richard Kreiss wrote:
> > One of my clients called today with a locked record problem.
> >
> > Short of rebooting his Windows 8 server, is there way to clear the lock on
> this record?
> >
> > 1. Record is locked with no one logged into the system 2. Reports
> > hang-up on this record 3. The only possible time to reboot the server
> > would be just after midnight.
> >
> > Is there a way that, when using either Procexp or procmon to see what
> might be locking this record if rclerk or rreport are running on a local
> computer and not the server?
> >
> >
> > Richard Kreiss
> > GCC Consulting
> >
> > Office: 410-653-2813
More information about the Filepro-list
mailing list