Batch Tasks not executing

(0) Share

Report

Posted on by Community Member

Hello All,

We have recently moved a copy of out AX Prod environment to a new domain to build a new development environment, and I am having issues getting the batch jobs working.

What is currently happening is that Batch Jobs themselves are getting picked up and marked as executing, but the tasks in the jobs are stuck in the "ready" status.

So far, I have done the following.

1) Configured Admin > Setup > System > Server Configuration to make the new AoS servers batch servers.

2) Configured the Batch Groups to that the would run on my batch AoS servers.

3) We are running under a new service account, so I have imported the account as a user and configured Admin > Setup > System > System Service Accounts to use the new account.

I have never seen behavior like this before, so ideas on what I might have over looked would be very helpful.

Thanks,

Phil

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (0)

Report

Hi Phil,

The batch jobs runs under the user account of the user which created them. Do you have batch jobs with a user which is not a valid user anymore?

Also make sure you remove the old servers in the Server configuration.

You can try to regenerate a full CIL, then restart the AOS servers as well.

Was this reply helpful? Yes No
Iulian Cordobin 8,201 on at

Like (0)

Report

Are they coming out of the execution step? Or they are left like this indefinetely?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

They are stuck like this indefinitely.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

All of the users are still valid.

My understanding is that we moved our AX dev environment to a new domain, but it is still able to be accessed by our original Active Directory Accounts. The permissions on SQL server are the same as in Prod as well.

I also tried your other suggestions, but I am still seeing the same issue.

Was this reply helpful? Yes No
Iulian Cordobin 8,201 on at

Like (0)

Report

If you can I would suggest wiping all the batch jobs (axfaq.blogspot.ro/.../batch-jobs-ax-2012-wont-run-troubleshoot.html) and then add them once more.

Was this reply helpful? Yes No
Waller Walker 345 on at

Like (0)

Report

@lulian, doesn't deleting all the batch jobs hurt the system? will they regenerate..? will users need to submit actions once agian?

Was this reply helpful? Yes No
Suggested answer

Denis Macchinetti 16,444 on at

Like (0)

Report

Hi Phil

My suggestion is to modify the account to the batch already scheduled.

Take a look here about how to do community.dynamics.com/.../modify-a-batch-job-39-s-created-by-user-after-it-is-saved

Was this reply helpful? Yes No
Suggested answer

Ismael Utitiaj 426 on at

Like (0)

Report

You need to choose the right AOS and set like batch server. Often when we created a new instance, old data is copied in the new instance, and if you check Server configuration (Admin-Setup-System-) it display two AOS and by default the bad AOS is activate. Then check Batch Table information and verified that ServerId field value exist for your jobs.

Was this reply helpful? Yes No