Microsoft Dynamics AX (Archived)

How to cancel executing batch job in AX 2009?

(0) Share

Report

Posted on by Tyre Hollander

I have an orphan batch job executing and cannot figure out how to kill it. Any suggestions?

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

spot 2,515 on at

Like (0)

Report

Hi, go to basic module in inquires select batch jobs and delete the respective batch job.

Regards

Was this reply helpful? Yes No
Ty Hollander 180 on at

Like (0)

Report

Tried that, but I get an Infolog stating
"Error Message (07:55:44 am) Cannot delete Batch job in the Executing or Cancelling state
Error Message (07:55:44 am) Cannot delete a record in Batch Job (BatchJob).
The corresponding AOS validation failed."

Was this reply helpful? Yes No
Verified answer

Arun Keerthy 360 on at

Like (0)

Report

Goto Basic -> Batch Job

Select the particular Job and Select the Functions -> Change Status

Select the Cancelling.

Once Job is cancelled (Confirm by Batch Job History in status field. It will take some time to Cancel)

Again goto Functions -> Change Status

Select withhold

And then you can delete the job.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Change status button is disabled on jobs in executing state

Was this reply helpful? Yes No
Tim Andaya 670 on at

Like (0)

Report

I have the same problem in the Contoso database; can't run the CU7 update jobs becuse of a posting that is executing somewhere on the Microsoft campus two years ago.

Can't delete it, can't change the status, can't do anything to it.

Was this reply helpful? Yes No
Suggested answer

Tim Andaya 670 on at

Like (0)

Report

Try this in the MicrosoftDynamicsAX database What you could try, since this is your sandbox/playground AOS (afaik), is to stop the AOS, head over to the DB and update the table Batch by running this query;

UPDATE BATCH SET STATUS = 0 WHERE STATUS > 6,

then BatchJob with

UPDATE BATCHJOB SET STATUS = 0 WHERE STATUS > 6.

Then start the AOS and continue from there. There could be something wrong with the jobs themself. You should also just open the table browser (or SQL Query the tables) and see if the AOSID is correct for the jobs in question.

Was this reply helpful? Yes No