Announcements
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
This indeed solved the issue. Thanks so much Miljan.
Works for 2 out of two of our customers facing this problem
Hi Miljan,
Thanks for describing your experience with this issue. We will definitely give this a try and let you know if it solved the problem.
Thanks again,
Gaston
Hi, We stumbled upon the same issue with customer on NAV2016. We used CU56 at first and then CU65. The Problem persisted and my guess is that it only happens in the databases with more than one company.
The solution in the end was to enter a commit at the start of the function StartJobQueues in Codeunit 450. The Problem is not reproducible on versions NAV2017 or newer but probably reproducible on version older than NAV2016 that also had the table called "Job Queue" as the lock on this table is causing this issue. For all of affected partners/customer, please let me know if this COMMIT fixes the problem.
Looks like Marco is not longer a member.
Has anyone been able to solve this issue? we are experiencing the same issue in MS NAV CU39.
Thanks in advance
Gaston
Hello Marco
Sometimes MS does not tell every fix they add to CU packages, have you tried installing later CU's after CU 34? The latest one is CU40.
I remember one CU a long time ago that broke XML port export behavior very different from what it was, and then magically the next CU changed back the default functionality. It is possible that something similar has happened.
Edit: now I read the thread again, and you have already tried CU38 to no avail. Bummer!
Hi Alfredo, before CU34 we've 4 service to balance JOB-QUEUE and Client, now is a nightmare and all is running under 1 service.
I've planned 2018 migration
I know you've tried everything, how about creating another NAS instance( or maybe several) and associate half the Job Queues to the new NAS instance. See if it still locks up.
No solution... even with CU38.
for Test I've suspend all jobs (we've more than 50 jobs) except one (Inventory adjustment), but if the queue is executed from NAS service, we've a lock in in the Job Queue table.
So, I disable NAS and I manually start the queue from the client ... not so good but it works without lock.
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.
André Arnaud de Cal... 291,359 Super User 2024 Season 2
Martin Dráb 230,370 Most Valuable Professional
nmaenpaa 101,156