web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Batch job is still running even after deletion (D365O)

(0) ShareShare
ReportReport
Posted on by 735

I have created a custom DataEntity (myDE) for custom table (myTbl). On Production Environment (PROD) I created an Export Project (myEP) and put myDE for incremental export into my local SQL DB into myTbl_Staging.

After while, I’ve got a requirement to increase the length in one of string field of myTbl (and definitely, the requirement says, that in local SQL DB the string value in already exported records also MUST be increased).

For this purpose, I stopped incremental export of myDE in myEP, and created a new Export Project (myTmpEP).

In myTmpEP I created a recurrent job (recurrentJob_1) to export ALL records via myDE by FULL PUSH (in a recurrent job (recurrentJob_1) settings I specified: stop execution after one time). After couple hours I checked the result of export in my local SQL DB (in myTbl_Staging) and discovered, that something goes wrong. The expected quantity of records is 71500, but when the qty of records (my local SQL DB in myTbl_Staging) had had been reaching 71500, after some time (I don’t’ know the exact time interval, I think it’s about 5-15 minutes) ALL records are deleted from myTbl_Staging and the process of fulfilling the myTbl_Staging started again. I decided that I created a recurrent job (recurrentJob_1) in wrong manner, so decided to delete recurrentJob_1

I navigated: System administration/Data management (please do not pay attention to the content in picture, I just want to show the way how I did it)

Step1. Exection details

1.1_2E00_.jpg

Step2. View execution log (please do not pay attention to the content in picture, I just want to show the way how I did it)

52051.2.jpg

Step3.  Selected an appropriate job and click "Delete" button.

3617.3.jpg

Step4.  then I deleted and execution of the project

7510.1.jpg

After that, I went to my newly created Export Project (myTmpEP)

14316.4.jpg

and clicked "Export" (so in fact I created a second batch  job (recurrentJob_2))

1033.5.jpg

Than decided to check the result in myTbl_Staging  (in my local SQL DB), and I discovered, that first recurrentJob_1 is still running (together with recurrentJob_2) - I confirmed in this by selecting distinct values of EXECUTIONID field from myTbl_Staging  table:

SELECT count(distinct INVENTSERIALID), EXECUTIONID  FROM [D365DH].[dbo].[DeviceInventTableStaging] GROUP BY [EXECUTIONID] 

Once again, I decided to delete execution by repeating Step1-Step4. Unsuccessfully. The data is still fullfilling into myTbl_Staging (in my local SQL DB).

I checked SystemAdministration\Inquiries\Batch jobs\Batch jobs - there is no my job in the list. Also, I was trying to find the same value of EXECUTIONID from myTbl_Staging (in my local SQL DB) in DMFDefinitionGroupExecution.ExecutionId field (on PROD) but there is no such records there.

The only place where I found same EXECUTIONID is in DMFExecution.ExecutionId table.

1108.6.jpg

So, the question is: how can I stop the execution of batch job? (taking into account - the the batch job is not in the list of batch jobs (SystemAdministration\Inquiries\Batch jobs\Batch jobs))

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    André Arnaud de Calavon Profile Picture
    304,293 Super User 2026 Season 1 on at

    Hi Ragoza,

    When you click the Export button to export data from a data project, it is not using the batch framework, but a kind of "client thread". When this thread stops for a certain reason, the status of the export project is not updated.

    To create a batch job, you have to use the Export options menu and choose to export using the batch framework.

    I do think that the current export job indeed stopped processing. You can either restart it or delete it and create a new one.

  • Ragoza Oleksandr Profile Picture
    735 on at

    Hi Andre, thank you for your attempt to help.

    Yes, I know that “Export button to export data from a data project … kind of "client thread", but still – I have no idea why the export of data was continuing running even after the batch job had been deleted. Any, with help of my colleague, we created an ‘urgent’ request via LCS (to restart a batch service) and this is what I received: ‘The engineering team investigated the environment and there is one long running query but DTU is good and there are no blocking statements. We need to try to figure out the root cause of why one recurring job failed, you don’t need to worry about restarting individual services’.

    After my ‘long running query’ has completed (it was taken over 6 hours), I clicked the “Export” button again and all required information was exported to my local SQL database.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 26

#2
imran ul haq Profile Picture

imran ul haq 8

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 4 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans