Yes. In my case it is a single user merged application and in a long running "cron" process. No one else is using the database and no other process accessed the records. My error handler would randomly report the record was locked by process 0. I had to restart to fix it.
I don't think I have seen it in the last few weeks since upgrading from 16.1HF2 to 16.2. John DeSoi, Ph.D. > On Sep 18, 2017, at 9:10 AM, Jeffrey Kain via 4D_Tech <[email protected]> > wrote: > > Has anyone who uses v16 run across false record locks being reported? > > On two occasions now over the past 3 weeks, we've run across locked records > where 4D reports that the user locking the record is not even signed in to > 4D. > > Locked Attributes seems to be giving the same information that 4D's user mode > locked record dialog displays (which is good I guess), but since that user > isn't even connected to the server there's nothing that can be done to > resolve it, other than to restart the server. > > Curious if anyone else has seen this? ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
