Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 302 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Known problems with Task Scheduler in NAV2017 CU19?
kellebra
Member Posts: 2
Hi!
We are currently updating our NAV2017 from CU5 to CU19.
In CU5 we had some trouble with the task scheduler and hoped it would get better in CU19.
Sadly we still have problems with it.
Currently we have more 40 job queue entries in 2 categories.
There are many days were everything works fine in our test system. But on other days one category is not currectly processed.
Let´s call the first category "A". Entries in category "A" are processed correctly.
Category "B" seems to work correct. No errors and the tasks are schaduled.
But it looks like the tasks in category "B" are only rescheduled and not executed.
It is a very annoying thing, because it is difficult to monitor.
Does someone have similar experiences or an idea what could cause the problems?
Kind regards
We are currently updating our NAV2017 from CU5 to CU19.
In CU5 we had some trouble with the task scheduler and hoped it would get better in CU19.
Sadly we still have problems with it.
Currently we have more 40 job queue entries in 2 categories.
There are many days were everything works fine in our test system. But on other days one category is not currectly processed.
Let´s call the first category "A". Entries in category "A" are processed correctly.
Category "B" seems to work correct. No errors and the tasks are schaduled.
But it looks like the tasks in category "B" are only rescheduled and not executed.
It is a very annoying thing, because it is difficult to monitor.
Does someone have similar experiences or an idea what could cause the problems?
Kind regards
0
Answers
Did you upgrade the NAV application (objects) to CU19 too? Or did you only upgrade the NAV platform to CU19? A few critical issues are resolved in the platform updates, but there are also quite some fixed made in the application. I don't know the details of all fixes or your issue. But your description sounds a bit like ID 273824 (last one in the following list)
Description: Recurring job queue entries are not rescheduled after the first run.
Changed objects: COD 453
Description: "Multiple recurring job queue entries stuck in process if they have a same job queue category code and they are processing at the same time."
Changed objects: COD 137 COD 1502 COD 448 COD 450 COD 453 COD 5334 COD 6700 COD 88 COD 98 PAG 672 PAG 682 TAB 472
ID: 262725
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."
Changed objects: COD 448 TAB 472
Description: "The length of the string is 344, but it must be less than or equal to 250 characters." error message on the Job Queue Entry page.
Changed objects: COD 400 TAB 409
Description: Task scheduler processes too slow when there are nonrecurring job queue entries with the same job queue category code, and the process gets stuck.
Changed objects: COD 448 COD 449
ID: 271726
Description: USERID on the Job Queue Entries page is changed every time a user logs in.
Changed objects: COD 455
ID: 273824
Description: Job queue entries are never set as the In Process status during execution.
Changed objects: COD 448
We have both updated.
May be the fix from CU20 will help. I think it should be quite safe to import only the changes from COD 448,448 and 455. What do you think?