Constant issue with 'G/L Entry table was locked by another user' message

(0) Share

Report

Posted on by MeltedCoin

Hello Everyone,

We are based in the UK and we are new users of Business Central after having recently migrated over from NAV.

Our users are complaining that they are constantly receiving the message 'The operation could not complete because a record in the G/L Entry table was locked by another user. Please retry the activity.' and they are having to wait a long time (sometimes up to a minute) before they are then able to post. We do raise quite large sales orders with lots of lines (some times in the region of 30/40 lines), however I wouldn't have thought this should result in such a long lock down, it certainly didn't take that long in NAV.

Does anybody have any idea what might be causing the issue or could anybody offer some advice?

Thanks...

Categories:

Other

Business Central

I have the same question (0)

All responses (14)

Answers (0)

Alexey Finogenov 1,659 on at

Like (0)

Report

This is a common cloud / on-prem story.. I think. Try to search via Web.

some links:
https://forum.mibuso.com/discussion/63745/g-l-entry-table-lock

Was this reply helpful? Yes No
MeltedCoin on at

Like (0)

Report

Thanks for your response, but I don't understand why our experience on Business Central should be so different to NAV 2018 on premise. We occasionally got the same message in NAV 2018 on premise but only rarely, and it didn't take nearly as long to clear.

Was this reply helpful? Yes No
Claus Macali.dk 1,045 on at

Like (0)

Report

If you still on a slow server ask your partner to get Microsoft to,move you to a premium server, its for free.

And you will also here in April or May get upgrade to version 14, were speed will a point they have fixed, so this

Get you going..

Was this reply helpful? Yes No
MeltedCoin on at

Like (0)

Report

Thanks for your response. We have already been upgraded but we are still facing this issue. We are hoping the April release will solve the problem because right now it is very frustrating for our users.

Was this reply helpful? Yes No
Steve Lazanas on at

Like (0)

Report

I would not expect this to occur from a 2018 to BC upgrade, and certainly not with SO's 40 lines deep. It does not sound like it is something standard causing this. Good luck.

Was this reply helpful? Yes No
Claus Macali.dk 1,045 on at

Like (0)

Report

Well they are running on BC Sass not on prim, and its well known thats the Sass can be slow… We all hope for the best when upgrading to Spring version

Was this reply helpful? Yes No
Adam Shilton 460 on at

Like (0)

Report

I've seen this error raised a few times and it is a pain. Happy to have a discussion with you on what may be causing this, although a good start would be to look into what version of Business Central you're running. If you're not yet on the Spring release, you may see improvements after the update.

I'll send you a message so you can contact me directly.

Was this reply helpful? Yes No
Claus Macali.dk 1,045 on at

Like (0)

Report

I have made a sandbox, on the spring release, you can already do this, now with demo data. Its working faster :)

Was this reply helpful? Yes No
Bryan Tschosik on at

Like (0)

Report

IF you have Automatic Cost Adjustment = ALWAYS within Inventory setup, that is more than likely the cause of the problem. The Adjust Cost process locks tables as it is running through it's calculations and adjustments...it needs to lock tables. The setting of ALWAYS is Not for everyone...many variables go into the decision on whether or not a company can have costs adjust on the fly, during posting. If it is already set to ALWAYS, set it to NEVER and see if that makes a difference. Then they will need to run Adjust Cost manually, while nobody is posting, or in nightly job queue….which many people do.

Was this reply helpful? Yes No
MeltedCoin on at

Like (0)

Report

Thanks for your response Bryan. Unfortunately I'm not convinced this is the issue. We've checked the instance of NAV we upgraded from, here's a screengrab of the settings taken from that:

So it was set to ALWAYS in NAV and we didn't experience this issue. Obviously all our data, the number of users and processes are identical. I find it hard to believe that we would need to make what I would deem a retrograde step by changing this setting when we've 'upgraded' to Business Central. I appreciate that this running on Sass and not on prem however it just doesn't sound correct to me.

I think the issue is probably around a setup/posting issue but am not convinced this is it.

Was this reply helpful? Yes No