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
- 301 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
Why do some job queues lose their heartbeat?
afarr
Member Posts: 287
We have a client with several companies, and several job queues in each, for a total of some 250 Job Queues.
We sometimes find that some Job Queues have stopped updating their heartbeat, although other Job Queues in the same company are working fine.
The system is Nav 2016 W1 build 46621.
The Job Queues are set to start automatically from NAS.
The problem occurred even when CPU and RAM usage was moderate.
Have you ever encountered similar behavior?
What steps (that don’t involve service restarts) could prevent this?
Thanks for your help.
Alastair
We sometimes find that some Job Queues have stopped updating their heartbeat, although other Job Queues in the same company are working fine.
The system is Nav 2016 W1 build 46621.
The Job Queues are set to start automatically from NAS.
The problem occurred even when CPU and RAM usage was moderate.
Have you ever encountered similar behavior?
What steps (that don’t involve service restarts) could prevent this?
Thanks for your help.
Alastair
Alastair Farrugia
0
Answers
I would suggest create a second NAS tier that checks those job queues that have been, lets say more than 2 hours running without ending and sends you an email. This way you can realise if the service stopped working and needs a restart.
Thanks for the suggestion. That is one of the workarounds that we are considering.
Of course, if some problem affects NAV services, then the second NAS tier might be affected too, so we might implement this at SQL level (a scheduled job run by the SQL Server Agent), instead of in NAV.
Regards
Alastair
My experience about this is usually some unexpected error happened when running job queue. You may find the error in windows event log.
I think maybe NAS is not stable enough, that's why microsoft add TaskScheduler in administration tool from NAV 2017.