Hi,
we're facing an issue where the job queue sometimes suddenly stops in some of our companies.
After investigating the windows event log, I believe that the last stop was caused due to a deletion of a company.
Should the job queue be able to handle these operations or do I really need to stop the service that is running the job queue for those operations? This is something that the user wants to do on his own. But he might not have access to the job queue service.
0
Answers
NAS configuration have a parameter called "Company Name". If you delete the Company the NAS will try to look at table "<company>$Job Queue Entry" and will not found.
To Delete and Create a Company you will have to stop NAS, change the configuration and start NAS again (the new company must have job queue configured to work).
Regards,
parm
thank you for the reply.
I checked the properties for the NAS but I could not find a property named "Company Name". There is a property called "Service Default Company". It shows one of the companies where the job queue is set up.
We are using NAV 2015. There is a seperate service only for the job queue. But it is one service for all companies. The property "Service Default Company" just shows the main company.
But the main company is not the one that was deleted.
Since the category of the message is "NAV/Navision Classic Client" I reply with information about NAS version 2009 and bellow.
I not sure about this but if one periodic Job Queue Entry was run in company AAA the service will retry to read the same record to execute again. If you delete the company AAA the service cache sould be cleaned.
Its very usual to have to restart the service.
Regards,
parm