Microsoft Dynamics NAV (Archived)

The error " record in the General Journal line table was locked by another user"

(0) Share

Report

Posted on by G VIGNESH

Why does the below error occurs? I got this while posting the payment entry.

I found a solution in google. stating- Wait for few minutes,

But it took around 10 hours for me.

What should be done if this error comes again ? Is there any permanent solution for this? - if yes, please do let me know.

I would appreciate if someone helps me in this.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

bharathkarunakaran 475 on at

Like (1)

Report

Hi,

You are getting this error when you are trying access/open the gen. journal line table?

If i am right, Some other user have locked the table you have until that user unlocks that table.

Regards,

Bharath K

Was this reply helpful? Yes No
G VIGNESH 37 on at

Like (0)

Report

Thank you for your kind response Mr. Bharath.

Can you please guide me to unlock the table? ( How to unlock the table)

Was this reply helpful? Yes No
bharathkarunakaran 475 on at

Like (0)

Report

Can you tell me how many users are there in your NAVISION.

The table that your trying to open will have the fields LOCKED,LOCKEDBY.

There you can find who have locked your table and you can request them to unlock

Was this reply helpful? Yes No
G VIGNESH 37 on at

Like (0)

Report

Around 50 users.

Was this reply helpful? Yes No
Bodhi 558 on at

Like (1)

Report

Create more batches for every payment user, if some one is opening this batch at the same time, block is possible

and Try to compile all objects again

Was this reply helpful? Yes No
Rajendra Gangwar 150 on at

Like (1)

Report

This usually happens when any of the transactions were running in the back end with access to particular table and we were trying to do transaction on same table. Try to restart the services if it get in deadlock process.

Was this reply helpful? Yes No
Suggested answer

Rahman Erlebach on at

Like (0)

Report

Hello,

First of all Locking situations are an indicator of over all performance issues, this involves checking your overall sizing and structure following our best practise, to know if your sizing for this installation is ok or not.

Second, you have 50 users, are they al lon one service tier? that's wrong, divide them on more than one service tier.

Third, try to do the postin gthat causes the issue using the job queue, so as it goes in the background, in this case we advise you to also create a new service dedicated just for the job queue.

After all of this, there is a very importan property in NAV, with controls the timeout for this locking:

Alter database-->Advanced--> Lock timeout.

Try to set it to 20 and tets again, try to 30 and test again to see if it gets better.

Finally you could disable the lock timeout conpletely and try again.

After all of this, if this does not help, then you need more advanced traces, Our known Guru the greatLars Lohndorf already blogged about this more than 10 years ago:

https://blogs.msdn.microsoft.com/microsoft_dynamics_nav_sustained_engineering/2008/03/28/simple-query-to-check-the-recent-blocking-history/

This should be your way to go, and based on the tracing you can use SQL Profiler or NAV applicatino profiler more to get more clues, and see how to boost the performance to overcome the issue:

Perhaps deleting not used indexes, set the righ tindexes, correct code that has issues, ...etc

Thanks,

Rahman

Was this reply helpful? Yes No