Batch remains in status Executing or Canceling, never End or Waiti

[Caroline]

Hi,

On AX2009, I have multiple batches/jobs setup and running on the server but
they actually run only once and then they stay in the status Executing,
instead of going to End or Waiting.

I have the same issue if I cancel a batch, the status is Cancelling but
never Canceled.

It seems that the batch is updated only once by the system and that's it!

Is somebody has an idea?

Caroline.

[Ron Larsen]

Hi Caroline,
It’s quite likely there is an error during batch processing of the job.
Because the batch is running in the service you may not see the AX error
message.

One way to test this is to disable the batch processing on the AOS, then run
batch processing in the client the old-fashion way
(Basic->Periodic->Processing).

When your jobs execute you will get messages/errors in the infolog. That
may lead you to the cause.

-Ron

[Richard]

I have the same problem with a few batches which export data. Once they've
started they keep the status 'Executing'. I've tried to run the batches the
'old-fashioned'-way like Ron suggested, but no errors occur.

They'll produce an info-log after the export, but if this would be the
cause, I should see the exports, but they are not created.

Anyone have another solution?

[Victor Gornostaev]

Check [table BatchGlobal, field LastProcFinishedJobs]. You should see datetime value, that AOS used to check if it is necessary to change statuses like Executing to Waiting, Cancellig to Waiting etc.
Set this value to current time (should do it from SQL server).

This fault can appear when system time changed value to future & AOS finished job, then write future time in this table.

PS. Sorry for my english.

> On Wednesday, November 05, 2008 7:02 PM Carolin wrote:

> Hi,
>
> On AX2009, I have multiple batches/jobs setup and running on the server but
> they actually run only once and then they stay in the status Executing,
> instead of going to End or Waiting.
>
> I have the same issue if I cancel a batch, the status is Cancelling but
> never Canceled.
>
> It seems that the batch is updated only once by the system and that's it!
>
> Is somebody has an idea?
>
> Caroline.

>> On Friday, November 07, 2008 3:00 PM RonLarse wrote:

>> Hi Caroline,
>> It???s quite likely there is an error during batch processing of the job.

>> Because the batch is running in the service you may not see the AX error
>> message.
>>
>> One way to test this is to disable the batch processing on the AOS, then run
>> batch processing in the client the old-fashion way
>> (Basic->Periodic->Processing).
>>
>> When your jobs execute you will get messages/errors in the infolog. That
>> may lead you to the cause.
>>
>> -Ron
>>
>>
>> "Caroline" wrote:

>>> On Friday, December 04, 2009 9:34 AM Richard wrote:

>>> I have the same problem with a few batches which export data. Once they have
>>> started they keep the status 'Executing'. I have tried to run the batches the

>>> 'old-fashioned'-way like Ron suggested, but no errors occur.
>>>
>>> They'll produce an info-log after the export, but if this would be the
>>> cause, I should see the exports, but they are not created.
>>>
>>> Anyone have another solution?
>>>
>>>
>>> "Ron Larsen" wrote:

>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>> ObjectDumper LINQ To Export Collection Via .NET Reflection
>>> http://www.eggheadcafe.com/tutorials/aspnet/21737599-5a63-4672-a32c-a36cca282a3f/objectdumper-linq-to-export-collection-via-net-reflection.aspx