85
Hello,
I just made a migration from 2015 to 2017 and I have a problem with job queues entries.
My service is set up like this (services picture)
In NAV, my job queue run once and after the job status is automatically "On Hold"
My Job is a reccurent job with a next execution time (job queue picture).
Someone can help me ?
Thanks a lot.
*This post is locked for comments
Yes
Hi everybody,
we have the same problem in CU 14. In CU 11 it is working fine. Different versioning between the two cus exist between around job queue entry area: Table 472 Job Queue Entry, codeunit 474 Job Queue Log Entry, codeunit 448 Job Queue Dispatcher,codeunit 453 Job Queue - Enqueue. By importing them from cu11,they seem job queue entries working correctly in cu14.
I know it's not the best solution,but it is a workaround if you are in need
Kind regards
Sorry NAS isn't use for schedule in nav 17.
However in found the source of the problem but i don't know why.
In codeunit 453, there is a function for schedule the task.
Before schedule the task, program check if a record with the job queue entry record id exist in the system table "schedule task"
And the record is always find but there is nothing in the data table.
It seems like, the program find the current job queue entry task.
BUG Microsoft ?
I thing the job queue run in my current session and not by nas services
#1
André Arnaud de Cal...
292,516
Super User 2025 Season 1
#2
Martin Dráb
231,409
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
