You’re offline. This is a read only version of the page.
5
After upgrading from NAV 2016 CU 18 to CU 30, our NAS stops working after approximately 10 minutes after several locking errors on the Job Queue table. Our issue looks very similar to the issue reported for NAV 2016 with number 261178 and description "Task scheduler causes a heavy locking and deadlocks in the application that makes it impossible to port job queue scheduling from Dynamics NAV 2016.".
Since the operation of the job queue is different between NAV 2016 and NAV 2017, it's not obvious to implement the update of NAV 2017 in NAV 2016. What alternative options are there?
*This post is locked for comments
Please take a look at this topic as I found the solution to this problem:
Good afternoon Kristof, did you have a solution on that? I'm facing the same problems on a customer implementation of 2016 CU30.
Thanks is advance for your time,
Regards,
Celia
Hi, we are also experiencing the same thing when we performed a technical upgrade to NAV 2018.
Do you manage to resolve?
Put all you Job Queue entries on "Hold". Make sure there aren't any conflicts with the Job Queue Entries, like they are calling the same object. You may need to stagger the "Earliest Start Date/Time". Restart the NAS server within the Administrative Client. If that doesn't work, create a new "NAS" service. Associate the Job Queue Entries with the new "NAS" server.
Same issue here, after a technical upgrade to CU38. Everything seemed to work in test, but since it's live we need to restart the jobqueue about every 15 minutes.
I tried to make a few changes to prevent locks, but have only had a little bit of succes.
Did nobody manage to solve this yet?
#1
Sohail Ahmed
2
#1
mmv
2
#1
Amol Salvi
2
Share
Report
All responses (
Answers (
