NAS & JOB QUEUE

nromain
Member Posts: 57
Hi all,
i have a really really strange issue using Job queue via NAS on a 5.00 SQL database. I explain :
We want to automatically run report 499 everyday. So we add test on GUIALLOWED before all dialog vars and we setup the job queue, restart the NAS and we have the error "You cannot use C/AL variable of type DIALOG blablabla..."
So, i decide to launch NAS in debug mode to see where we forget to put the "IF GUIALLOWED THEN". I deactivate Job queue, reinitialize the job queue task and enter in the DOS prompt to launch the nas with debug. Debugguer starts correctly, i deactivate breakpoints on triggers and then, the debugguer doesn't find any error. but when i open the database and see in the job queue log, i see always the same error "You cannot use C/AL variable of type DIALOG blablabla..." But the NAS debugguer is still running and no error encountered !
So, i stop everything, restup the job queue task, reopen the dos prompt and launch the NAS with debug but then i decide to follow the code line by line and the strange thing happens. It is as if the NAS only active the job queue but not manage the tasks. In the job queue log, always the same error but my debugguer not even enter into the report!! It was as if the task was done on another session. Strange!
Do you have any idea? an explanation?
Thank you so much and pardon my poor english
Best regards,
Nicolas ROMAIN
i have a really really strange issue using Job queue via NAS on a 5.00 SQL database. I explain :
We want to automatically run report 499 everyday. So we add test on GUIALLOWED before all dialog vars and we setup the job queue, restart the NAS and we have the error "You cannot use C/AL variable of type DIALOG blablabla..."
So, i decide to launch NAS in debug mode to see where we forget to put the "IF GUIALLOWED THEN". I deactivate Job queue, reinitialize the job queue task and enter in the DOS prompt to launch the nas with debug. Debugguer starts correctly, i deactivate breakpoints on triggers and then, the debugguer doesn't find any error. but when i open the database and see in the job queue log, i see always the same error "You cannot use C/AL variable of type DIALOG blablabla..." But the NAS debugguer is still running and no error encountered !
So, i stop everything, restup the job queue task, reopen the dos prompt and launch the NAS with debug but then i decide to follow the code line by line and the strange thing happens. It is as if the NAS only active the job queue but not manage the tasks. In the job queue log, always the same error but my debugguer not even enter into the report!! It was as if the task was done on another session. Strange!
Do you have any idea? an explanation?
Thank you so much and pardon my poor english

Best regards,
Nicolas ROMAIN
0
Comments
-
Did you disable the request form on that report?
I never used NAS in debugger mode but when used with Job Queue I always make a copy of the object to run and modify it for NAS usage (delete all dialog variables, any code reference to those vars,disable the request form,...) so a clean version of the object is used. Always worked for me.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