ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Manufacturing >> DC-A File BKDCTLAB Locked!
http://www.istechforum.com/YaBB.pl?num=1121956802

Message started by Rbuchanan on 07/21/05 at 06:40:02

Title: DC-A File BKDCTLAB Locked!
Post by Rbuchanan on 07/21/05 at 06:40:02

I've been fighting problems getting shop floor data collection to work smoothly over the last couple weeks. Mon-Wed everything seemed to be working fine, but today the machines give an error that BKDCTLAB is locked by another user, do they want to try again. Over and over they say yes and it keeps coming back.

If they say no it gives them more error messages about the locked files and the dumps them back to the menu. Unfortunately, it also adds an un-editable record to their work orders in process and they cannot close out of it, I have to delete it in the maintain database mode!

The only change I can come back to, even remotely, is that my office staff started entering labor tickets in WO-M on Wednesday, but why didn't the problems start until today!!??

Why is DC-A looking at TLAB when it stores data in PLAB? And what processes actually lock TLAB??

Title: Re: DC-A File BKDCTLAB Locked!
Post by Lynn Pantic on 07/21/05 at 07:03:33

BKDCTLAB is only used by DC-A/B/C so using WO-M is unrelated. It is a file that is used to temporarily hold the records actually being logged into and out of in the DC programs. Once the DC program saves the record, it is stored in BKDCPLAB.

Make sure your Pervasive is PSQL 2000i and not 2000 on the server and all workstations because there were some page locking versus record locking improvements with 2000i.

Title: Re: DC-A File BKDCTLAB Locked!
Post by Rbuchanan on 07/21/05 at 09:35:50

Lynn-

Thanks for the quick response!!

I'm fairly certain that they are all 2000i, but I'll double check. THis has been an on-going problem over the last few weeks. It seems to come and go at will, not affecting us for days on end, then they all start to complain. Something tells me that when somebody gets and error, they are just walking away from the machine and leaving it, AND NOT TELLING ME!

Title: Re: DC-A File BKDCTLAB Locked!
Post by JNAPIER on 07/21/05 at 10:29:55

I have seen a case where an employee had to 3 finger salute Classic not EVO and the files that were open or locked in pervasive stayed that way until you deleted that user. We have the workstations on multi session for DBA.

John

Title: Re: DC-A File BKDCTLAB Locked!
Post by Dave Miller on 07/22/05 at 08:59:00

I have been fighting the same situation for weeks. I have tried deleting Pervassive from the server and workstations and re-installing a fresh copy, I have tried downloading the trial version of client server pervassive - the problem still persisits. If anyone has any other options I would sure like to hear - I am frustrated - as are my employees who are all fighting to use one computer.

Title: Re: DC-A File BKDCTLAB Locked!
Post by timgolds on 07/26/05 at 07:21:03

Just a small suggestion.

Check your network settings on machines gathering labor and parts.

I had this problem and it turned out it was a network timeout problem and Pervasive thought the files was still locked even though the workstation was released.

It was a bug in our wireless router and a firmware update fixed the problem (MTU was set wrong and couldn't be set correctly) I have also heard rumors that having protocols that are not available turned on can also cause nasty delays that effect locks.

One way I found there was an issue was through monitor. I was showing the same user logged in twice even though they were only logged in once.

Hope it helps,

Tim

Title: Re: DC-A File BKDCTLAB Locked!
Post by Rbuchanan on 07/29/05 at 12:49:26

Just a note to all. Lynn has worked this out for us and has a new patch that changes the locking scenario. If you are having this trouble you need to contact her!!

Title: Re: DC-A File BKDCTLAB Locked!
Post by Rbuchanan on 08/05/05 at 05:41:43

Lynn-

Sorry to bug you again, but the problem has seemed to move on me! Now the file getting locked is BKDCPLAB. If I hit the "retry" button six or eight times it finally goes through, so this does'n't appear to be as bad as the last go 'round, but equally as annoying seeing how I have nine shop floor machines all waiting to do input and that doesn't count the staff in the office trying to work on Labor!

Rob