Hi everyone,
I know that there are a lot of topics dealing with this issue, but none of them solved my scenario.
I have an instance of Microsoft Dynamics Ax R2 installed on the homologation environment of a client and the batch jobs on this server stopped running. I don't have any information on changes on the environment, but they worked for years until last february.
New jobs stay with "Waiting status" and never start. Older ones stopped running after Feb 20th.
The same batch job that I'm trying to run runs perfectly on production environment, but I tried running some standard Ax jobs and they also keep with "Waiting" status forever.
Here is what I've checked/tried so far:
* The server runs a single AOS and it's configured as a batch server on Server Administration
* The schedule for the batch server is configured from 00:00:00 to 23:59:59, with 8 maximum batch threads.
* I tried running with the empty batch group and also tried creating a new one (both of them have my AOS configured as batch server).
* I tried schedulling it for some time on the future (2 minutes or so).
* Also tried removing the batch group from the server and then adding it again.
* I deleted every batch process previously configured and then tried running my job with no success.
* I tried generating a full CIL compilation (also tried excluding the contents from the XPPIL folder and XPPASSEMBLY table and then running a full CIL compilation)
* Also tried restarting the AOS service and the server itself.
None of the above tries did work. Is there something I might be missing?
