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
- 305 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Issue: Jobs being stuck in Navision
divyaseekunta
Member Posts: 24
Dear All,
I have been experiencing an issue with jobs whereby there is a particular job being blocked with object type=0 and object id=0 and the field 'Active' is ticked but the 'process running' is unticked.
The issue here is that this is blocking all other jobs and no jobs running at all after this.
Note: The NAS has been restarted but still after some time of correct processing the same issue is being encountered.
Could you please help and suggest an idea why this is happening?
Thanking you in advance,
Best Regards,
Divya
I have been experiencing an issue with jobs whereby there is a particular job being blocked with object type=0 and object id=0 and the field 'Active' is ticked but the 'process running' is unticked.
The issue here is that this is blocking all other jobs and no jobs running at all after this.
Note: The NAS has been restarted but still after some time of correct processing the same issue is being encountered.
Could you please help and suggest an idea why this is happening?
Thanking you in advance,
Best Regards,
Divya
0
Comments
This issue has been resolved. There was a new job which had been causing this issue. A DB restore has been done to resolve this issue.
Thanks & Regards,
Divya