Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
Options
NAV 2017 Job Queue
Jan87
Member Posts: 26
Hello experts,
we have an issue with the Job Queue and I have no clue whats the reason or a possible fix. Maybe you guys can help.
We have a longrunning reoccuring process queued in the Job Queue. It seems to work fine when started once and not restarted later.
The problem is, when someone tries to restart the queue while it is still running we have two threads processing the same Codeunit and they run on errors, because they are not supposed to run parallel.
We have to stop the Service to kill all but one thread. But this is not enough. Next time we start the client one thread starts again. Even if we put the Job Queue Entry on hold or set a different user. It is only possible to stop it when we wait until it is in the ready state and set it on hold.
we have an issue with the Job Queue and I have no clue whats the reason or a possible fix. Maybe you guys can help.
We have a longrunning reoccuring process queued in the Job Queue. It seems to work fine when started once and not restarted later.
The problem is, when someone tries to restart the queue while it is still running we have two threads processing the same Codeunit and they run on errors, because they are not supposed to run parallel.
We have to stop the Service to kill all but one thread. But this is not enough. Next time we start the client one thread starts again. Even if we put the Job Queue Entry on hold or set a different user. It is only possible to stop it when we wait until it is in the ready state and set it on hold.
0
Answers
Fill "Job Queue Category Code" in this job queue.
In this case it should wait until current running queue is finished.