NAV 2016 CU 34-35 and Job Queue Locking

(0) Share

Report

Posted on by Community Member

Hi,

we have a very frustrating problem with job queue... We've two company in same db. For company A I've setup a NAV_A service with NAS enable and for company B I've setup NAV_B service also with NAS enalble for Scheduling process.

All works great before cumulative update 34: after that we've Job Queue Locking after 10 minutes that the process start.

If I stop Nav_B service all work. In event viewer I've this usual message... The operation could not complete because a record in the Job Queue table was locked by another user.

Are there other user with this problem?

Thanks!

MArco

*This post is locked for comments

I have the same question (0)

All responses (19)

Answers (0)

ManishS 86 on at

Like (0)

Report

Did you verified your NAS service which you configured is still the same.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes, 2 services configured on different ports with same domain account service on the same db. Services have configured with 2 different Services Default Company

The default company that is used for Client, OData, and NAS Services.

Was this reply helpful? Yes No
Damogran 360 on at

Like (0)

Report

Hello Marco

Did you do binary upgrade, object upgrade or both?

br, urpo

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello Urpo, I've done binary and Object Upgrade

Thanks

Was this reply helpful? Yes No
Damogran 360 on at

Like (0)

Report

OK, next thing you have to do is check all recurring jobs in your Job Queue, and see what runs every 10 minutes. Then you should have a good picture what is causing the problems.

Is it It is possible that you have a job that accesses more than one companies?

Was this reply helpful? Yes No
Emad Akhtar 60 on at

Like (0)

Report

Make user that you have a Location in warehouse with the same name as the user.

The user location should be linked to a location profile (license plate enabled) specially created for the users and setup as "user profile location" in warehouse management parameters general tab.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

[quote user="urpok"]

OK, next thing you have to do is check all recurring jobs in your Job Queue, and see what runs every 10 minutes. Then you should have a good picture what is causing the problems.

Is it It is possible that you have a job that accesses more than one companies?

[/quote]There is a job that copy dimension and dimension values from one company to another: this job is running from nav 2009, i think that something is change from nav2016 cu 31

Was this reply helpful? Yes No
Damogran 360 on at

Like (0)

Report

Maybe a solution for this would be refactoring the code so every time a dimension or value is inserted or deleted, they gets inserted/deleted to other companies as well.

I know this does not fix the issue, only the appearance, but that is what I would do.

There are multiple issues with Job Queues, and that is mainly the reason why MS has rewritten it to NAV2017 and later versions.

Oh, I also came to think one basic thing you could try; if you have not re-compiled all objects after upgrade, you should do it now.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I think that Migration to 2018 is the best solution Urpo.

Thanks for answer!

Was this reply helpful? Yes No
Sleepy7 15 on at

Like (0)

Report

Yes, there are (CU38). I'm wondering if you have found a solution, because I can't seem to find out what's going wrong.

Was this reply helpful? Yes No