# Operator can not clock out. Epicor throwing record-locked error **Category:** [Epicor ERP 9](https://www.epiusers.help/c/e9/7) **Created:** 2017-01-12 18:39 UTC **Views:** 5028 **Replies:** 31 **URL:** https://www.epiusers.help/t/operator-can-not-clock-out-epicor-throwing-record-locked-error/36889 --- ## Post #1 by @emanpittfan We have a user who cannot clock out of any job she is currently in. When she tries to clock out, the MES program spins for about 3 minutes and then throws a (7243) (7241) error message. I tried running Conversion Program 8920 on the server to manually clock her out of the jobs but Epicor throws a "record lock" message when I try to change the "yes" to "no". Does anyone know of a way out of this or what might have caused it in the first place?? I've waited 4 hours now but the record(s) still appear to be locked and she cannot clock out at all. No other operators are having this issue. Any ideas???? --- ## Post #2 by @cchang Try conversion program 8930 on the Labor Header. --- ## Post #3 by @emanpittfan When I tried that, I get a popup message that says LaborDtl in use by ,49 on batch. Wait or choose CANCEL to stop. (2624) Any idea what "in use by ,49 on batch" means???? --- ## Post #4 by @Beth Is she logged in to more than one MES station? Is anyone trying to edit her record in Time & Expense? --- ## Post #5 by @emanpittfan Beth, I think originally early this morning she tried to goto another computer to see if it work there but it did the same thing (MES just hung and started with the spinning circle). I have shutdown and restarted all the MES computers and also made sure that our user that does labor edits isn’t trying to edit her record in Time & Expense. For the record, we tried to go in and manually change the entries in Time and Expense entry but it just hangs up just like in MES when we tried to do it. It is some kind of record – lock problem going on but I don’t know what to stop or shutdown to fix it.. --- ## Post #6 by @cchang I have never seen that popup message. I'm not sure if clicking CANCEL will release it. --- ## Post #7 by @Beth Did you reboot the PC that was running the Time and Expense entry, not just exit out of Epicor? Sometimes that will stop a record lock. Just thoughts... --- ## Post #8 by @emanpittfan I did notice in the App Server connections on our Epicor server, I have a “rogue” connection that has a status of “SENDING” where all of the other connections just say “CONNECTED”. It is coming from the very computer that originally had the issue this morning. I completely shutdown this PC but this App Server “sending” connection stays. Could this be part of the problem? Is there any way to “close” this one “sending” connection without having to reboot the server? --- ## Post #9 by @Beth Mike, There is a way and I'm trying to remember how (other than rebooting the server) to kill those connections. It's been a few years since I have had to do it and my memory is not going back that far at the moment. --- ## Post #10 by @cchang Can you cancel the PID connection that is hung? When you restarted the AppServer, did the date change on the "sending" connection to the date you restarted the appserver? --- ## Post #11 by @gpayne Yes, you can click on the link and kill that appserver. I have mine fathom open all of the time to monitor sending appservers that were abandoned. You do have to be careful the capture wip process is not running as it can be sending for as much as an hour. [cid:image001.png@01D26CF6.24C5E7B0] [cid:image002.png@01D26CF6.24C5E7B0] --- ## Post #12 by @emanpittfan Thanks Greg, once I kill it, do I need to do anything else in order for it to be used again? Best regards Mike Abell IT Manager Flexial Corporation a company of BOA Group 1483 Gould Drive, Cookeville, TN 38506, USA Phone: +1 931 432 8408 Fax: +1 931 432 1889 Mail: mabell@flexial.com Website: http://www.flexial.com http://www.boagroup.com --- ## Post #13 by @emanpittfan You will never believe this, but after 8 hours of being hung in “sending” mode, right before I was about to go in and kill it, the Appserver that was hung let go and went back to showing Available. Once it did this, I was able to go in and run conversions 8920 and 8930 and clock her out as I would normally do if something like this occurred. The only thing bugging me now is WHY a clock out transaction hung up the App server for seven hours. Anyone have ANY kind of notion why or how this could occur. This has never happened before so I’m a little worried. Thanks again for everyone’s help!! --- ## Post #14 by @gpayne No, Another should spin up to takes its place if you are under your min number of appservers. It will show as starting usually when you return to that page. If you refresh you will see the cpu use column for the new appserver to be high for the first few minutes. If you have your appserver in verbose mode you can see the last operation that occurred on the process you killed. I had to do this to find a rogue dashboard that would go into sending for 30 minutes. --- ## Post #15 by @Brinda_Whitaker In 9.05.xxx there is a utility that can be ran to clock out users. I think it is 8920 and 8930. --- ## Post #16 by @Kimberley I think I have seen this before. I believe I created a little tech note how it was fixed. let me dig for it and see if I can find it. Thanks --- ## Post #17 by @Randy This happens to us every so often. Epicor Support had us make a updatable BAQ to clear stuck MES users. We're on E10.0 though. --- ## Post #18 by @emanpittfan Brenda, thanks, yes I know about 8920 and 8930. Neither worked for me as both of them popped up a message that the record is locked and it cannot access it. After about 8 hours, it FINALLY let go of it on its own and I was able to get her clocked out. I have no clue how or why this happened or if it will happen again though… Best regards Mike Abell IT Manager Flexial Corporation a company of BOA Group 1483 Gould Drive, Cookeville, TN 38506, USA Phone: +1 931 432 8408 Fax: +1 931 432 1889 Mail: mabell@flexial.com Website: http://www.flexial.com http://www.boagroup.com --- ## Post #19 by @emanpittfan Kim, that would be great. Epicor hasn’t came up with anything yet…. Best regards Mike Abell IT Manager Flexial Corporation a company of BOA Group 1483 Gould Drive, Cookeville, TN 38506, USA Phone: +1 931 432 8408 Fax: +1 931 432 1889 Mail: mabell@flexial.com Website: http://www.flexial.com http://www.boagroup.com --- ## Post #20 by @cchang What fields are you updating in your updatable BAQ? Looking to create an updatable BAQ where the users can update it without having an admin run 8920 or 8930. --- ## Post #21 by @Randy Chia, The update is to the LaborDtl.AcriveTrans & LaborDtl_TimeStatus fields. The table is big so the BAQ limits it to last & current day. If you're thinking of a dashboard for this, you could use the JobNumber. The query syntax is: select [LaborDtl].[JobNum] as [LaborDtl_JobNum], [LaborDtl].[EmployeeNum] as [LaborDtl_EmployeeNum], [LaborDtl].[ActiveTrans] as [LaborDtl_ActiveTrans], [LaborDtl].[TimeStatus] as [LaborDtl_TimeStatus], [LaborDtl].[LaborHedSeq] as [LaborDtl_LaborHedSeq], [LaborDtl].[LaborDtlSeq] as [LaborDtl_LaborDtlSeq], [LaborDtl].[LaborType] as [LaborDtl_LaborType], [LaborDtl].[CreatedBy] as [LaborDtl_CreatedBy], [LaborDtl].[CreateDate] as [LaborDtl_CreateDate], [LaborDtl].[CreateTime] as [LaborDtl_CreateTime], [LaborDtl].[ChangedBy] as [LaborDtl_ChangedBy], [LaborDtl].[ChangeDate] as [LaborDtl_ChangeDate], [LaborDtl].[ChangeTime] as [LaborDtl_ChangeTime] from Erp.LaborDtl as LaborDtl where (LaborDtl.ChangeDate >= DATEADD (day, -1, GETDATE())) --- ## Post #22 by @gpayne Here are the updatable dashboards we use in E9. Unsets the clocked in on laborhed and active on labordtl. I have a trusted user that runs them so they are wide open. HTH Greg update laborhed.dbd (95.3 KB) update labordtl.dbd (85.9 KB) --- ## Post #23 by @cchang To unlock the records, do you just uncheck the LaborHed.ActiveTrans field when doing the update or is there another field that needs to be updated? --- ## Post #24 by @Randy The stuck ones are usually lines with active checked and a blank/null/whatever on LaborDtl. We uncheck and set it to A --- ## Post #25 by @gpayne Yes, just uncheck the active trans in LaborDtl. That is the same as 8920 LaborHed.Clockedin uncheck clockedin That is the same as 8930 --- ## Post #26 by @Kimberley let me know if you can see these images. --- ## Post #27 by @emanpittfan Kim, thanks so much. This isn't the exact problem we experienced but I have seen the problem you posted as well. --- ## Post #28 by @Jim_Lutz This is a common problem with our system as well. Many times this will happen and we'll see "Lock Wait Timeout" multiple times in the app server logs. This error is because of a deadlock in the SQL database caused by some sort of bug in Epicor that we can't get pinned down for support because it only happens coincidentally on the floor. Waiting a few minutes for all the locks to expire is the only remedy. Rebooting the server works because it takes longer than that for it to come up, but it's rather extreme. Keeping everybody's hands off after killing all the clients also achieves this. However, there doesn't seem to be a very easy method to resolve this issue. --- ## Post #29 by @emanpittfan Jim, we are on Progress DB, not SQL and this has never happened to us before but ours seems to stem from one particular job and one particular operation on that job. I have no clue “why” but it’s happened twice now during “ending activity” on the particular operation on the particular job. Any idea what could cause it? Best regards Mike Abell IT Manager Flexial Corporation a company of BOA Group 1483 Gould Drive, Cookeville, TN 38506, USA Phone: +1 931 432 8408 Fax: +1 931 432 1889 Mail: mabell@flexial.com Website: http://www.flexial.com http://www.boagroup.com --- ## Post #30 by @Beth Take a look at this job and one that doesn't have the problem that uses the same operation, if possible. What are the differences? I would look at the resources as well. Do you have more than one resource for the operation? I have seen this before but it has been quite some time ago. Beth --- ## Post #31 by @bordway >>Progress >> it’s happened twice now during “ending activity” on the particular operation on the particular job Not exactly the same as your situation.. Just something similar that happened to me this spring - V8.03.409C / Progress. Out of the blue certain operations where users couldn't clock out and a nasty side effect: - The bi file would start to grow continuously after a user would try to clock out of these labor records. Performance degraded for all users & if not corrected would eventually fill up the disk. - each night I ran the conversion programs ---- had to find the related process(es) in the task manager & kill those, reboot the server ------- and go back and verify labor records were inactive. sometimes rerunning the conversion program(s). After about a week I was told by tech support it was a known issue on 8.03.409C and patching to 8.03.410 was the only fix. I was skeptical but.. the patch actually worked in this case. --- ## Post #32 by @Brinda_Whitaker Is anyone else having an issue with the RDDs not migrating for Crystal Reports? First I thought Epicor was not migrating the report type base so I changed the type to Crystal. Unfortunately that did not nothing for the migration of RDDs . Some of the RDDs are still missing. It's interesting how only the last RDD for the form migrated. Why the last and not the first? --- **Canonical:** https://www.epiusers.help/t/operator-can-not-clock-out-epicor-throwing-record-locked-error/36889 **Original content:** https://www.epiusers.help/t/operator-can-not-clock-out-epicor-throwing-record-locked-error/36889