NAS Performance

MatStephensSandA

Hi.

I am having trouble running a report via a function in the Job Queue on a 2009 classic.
the standard Job Que functionlaity is called, it calls a codeunit with a parameter string, that parametere string determins which function within the Codeuint is called.
My custom report is called via the parameter string on the standard job que.
Within this function parameters are passed to a custom report, the report is saved as HTML and part of the report is to create a csv export.
After two hours the report still has not finished processing so i restarted all the relevent services and abandoned the process.

I then exported the code to a normal codeunit, ran the codeuint and it works fine and in a timely fashion. The client i ran it from is on the same server that runs the Application Server and uses the the same credentials. the report runs fine, saved as html and csv file created as expected all within a matter of minutes.

I have made sure that there are no other jobs due to be processed so all that should be triggered by the job queue is my one call to this custom report.

Has anyone ever had an issue like this???

Any ideas???

Marije_Brummel

You can debug the NAS process or look at the Windows Event log.

kriki

[Topic moved from 'NAV Three Tier' forum to 'NAV/Navision Classic Client' forum]

MatStephensSandA

Hi.

There is nothing in the event viewer as ther is no actual fault..
Its not as if the report has crashed it just takes hours to run..
Just dont understnad why the NAS Service takes so long to run the report

Marije_Brummel

Have you tried debugging the process?

These things are sometimes also related to the userid that the NAS is running. Maybe it has no access to a folder.

kine

You can try to run the NAS in console. Than you can try to use SQL Profiler to see if NAS is communicating with SQL. Check if you are using Automations in your process. If yes, look at how often you are initializing them. Too many automation initialization under NAS leads to freezed NAS. Try to use singleinstance codeunit to keep the initialization on minimum.

MatStephensSandA

first of all thanks for the help...

Permissions, i dont think this is the issue as the file does get created eventually it just takes (litterally) hours. If it was permissions then I would have thought iut would not be created at all.
Automation... I dont explicity call any, I check if a CSV file exists if it does then delete it if not then create it. The CSV then gets populatd via the reuslts of the report. So the values of the CSV are populated by the report which writes to the created csv file. -This is the footer of the Aged debt report for all customers. I know this will take a while to run but i dont see why it takes hours using the Job Scheduler (which calls a single instance codeunit) -I do pass some variables to the report via a function in the report i then tell the reoprt to saveashtml.

Its all like clockwork from a user perspective but as soon as i put it on the Job Queue it is stupidly slow.

Im not sure how to run the NASSQL Session in a debugger mode. however if nothign is failing then im not sure what i will find anyway?

again i do aprechiate the assistance.

ta5

What is the setting for "object cache" in NAS?
Regards
Thomas

MatStephensSandA

Object cash is 32000kb

ta5

Maybe it's worth to test with at least the double. What's the setting for the clients?
Thomas