Job Queue Entry stays in progress

elwin68
Member Posts: 153
We are using a codeunit in the classic client of NAV5 SP1 which scans a folder for files. When a file is found it is read and checked for a specific content. Then the file is moved to another folder.
When running the codeunit manual everything works fine.
When using an open client to run the codeunit through a timer form everything works fine too.
When running the codeunit through the Job Queue the entry stays in progress. The Job Queue Log Entry gives no error message.
I hope somebody can give me a hint.
Thanks in advance.
When running the codeunit manual everything works fine.
When using an open client to run the codeunit through a timer form everything works fine too.
When running the codeunit through the Job Queue the entry stays in progress. The Job Queue Log Entry gives no error message.
I hope somebody can give me a hint.
Thanks in advance.
0
Best Answer
-
Do you have any Dialog Windows appearing during the process? This can cause NAS to hang.5
Answers
-
Job queue is running by NAS. You can check whether the account that running NAS has proper permission to access the folder. It may cause job queue is always running if permission issue.0
-
The account has proper permissions to access the folder.0
-
If NAS encounters a deadlock, it will restart, this is expected behavior. However the job queue that was in process remains with status InProcess after the restart, but has in fact to be re-started manually after NAS restart0
-
Do you have any Dialog Windows appearing during the process? This can cause NAS to hang.5
-
One ERROR command was still in the codeunit without using GUIALLOWED. I overlooked this completely.
Thanks for sending me in the right direction.
0 -
ERROR statements shouldn't cause a problem and you shouldn't wrap them round IF GUIALLOWED because you still want the error to occur.
What I was actually referring to was the use of variables of type "Dialog" e.g. showing progress information - this can cause problems/hanging and these should be wrapped around an IF GUIALLOWED0 -
The codeunit had no variables of the type 'dialog' in it only one ERROR-statement. After removing this statement the job queue was running correctly and don't stay inprocess anymore.0
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions