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

Announcements

Introducing our New Video Series: Community Spotlight
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Batch job stuck with &...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Batch job stuck with "Executing" status or "NotRun"

(0) ShareShare
ReportReport
Posted on by PB-27051451-0 20

Hi,

we are having some issues with the batch job executions.

This is our scenario:

- we have two data package that exports data entities to our database (BYOD)

- an external service authenticate and require the execution of the two data package via REST API (ExportToPackage)

- the exetrnal service asks the status of the executions using the executionId until is not Suceeded or Error via REST API (GetExecutionSummaryStatus)

This setup worked well for months but recently from time to time some execution of one of the data package (random) start to stuck on Executing or NotRun without any apparent reason.

We had also the same problem, mostly with the Executing status, with the "Execute now" button from the user interface.

Do you have any idea on the possible solution or cause for this problem? 

In order to temporary fix the problem we are scheduling the jobs but we can't find a way to get the executionId in order to understand if the datapackage job failed or suceeded.

Thank You for your help.

Paolo

I have the same question (0)
  • Suggested answer
    Alireza Eshaghzadeh Profile Picture
    Alireza Eshaghzadeh 14,839 Super User 2026 Season 1 on at

    Hi Paolo,

    These issue can have several aspects.

    When it comes to the to the BYOD batch jobs, you need to create a logical start time for each BYOD batch jobs that they do not start at the same time and a recurrence that is calculated based on the batch job end time (e.g. if a BYOD batch job, in average need 1 hour to be finished, it is not logical to set a recurrence less than 1 hour.

    There is a feature (i.e. Batch framework contention reduction) that you can activate to reduce in blocking on batch framework tables.

    pastedimage1634028596693v1.png

  • PB-27051451-0 Profile Picture
    PB-27051451-0 20 on at

    Hi Alireza,

    thank you for your reply.

    Can you please elaborate more on the start and recurrence part? We are not using the scheduled jobs.

    We decided to schedule them just to fix the problem and this way it worked but it's not easy to orchestrate so we would prefer to call the execution from our external service.

    If you are talking about the schedule of the external service that should be fine because it just take 30 minutes and it runs once per day so we don't have any overlap on the executions.

    Am I missing something on your reply?

    Thank you for your help

    Paolo

  • Suggested answer
    Alireza Eshaghzadeh Profile Picture
    Alireza Eshaghzadeh 14,839 Super User 2026 Season 1 on at

    Hi Paolo,

    Thanks for the response. I meant if you have a scheduled BYOD jobs that runs based on a recurrence (e.g. hourly or daily), it is better that these batch jobs does not start at the same time to minimize throttling.

    Do you still have issues with BYOD batch jobs that have "Executing" status? Have you checked from data management to check what error message you get for these BYOD jobs?

    Have you checked if the "Batch framework contention reduction" is activated?

  • PB-27051451-0 Profile Picture
    PB-27051451-0 20 on at

    Hi,

    thanks for your time. Correct, we don't have jobs that start at the same time on the BYOD.

    I checked now and we don't have the "Batch framework contention reduction" enabled.

    I also checked the errors.

    When we have "NotRun" we don't have any error while when we have "Executing" one of the data entity in the package is stuck on executing with a SSIS connection timeout error:

    -1071636471Connection manager "OLE DB Destination Connection"SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "Login timeout expired".
An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".
An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "TCP Provider: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
".
-1071611876OLE DB Destination [2]SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "OLE DB Destination Connection" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.
-1073450985SSIS.PipelineOLE DB Destination failed validation and returned error code 0xC020801C.
-1073450996SSIS.PipelineOne or more component failed validation.
-1073594105There were errors during task validation.

Impossibile generare il file di esportazione dell'entità.....

    Because of this error we asked to scale up our database BYOD but we are not sure if it's a problem related to the database or the batch server.

    Thank you for your help.

    Paolo

  • Suggested answer
    Alireza Eshaghzadeh Profile Picture
    Alireza Eshaghzadeh 14,839 Super User 2026 Season 1 on at

    Hi,

    Please try to activate this feature and then add the timeout time for the BYOD jobs on Data Management > Framework parameters > Bring your own database

    pastedimage1634033139201v1.png

    Then start the BYOD export job.

  • PB-27051451-0 Profile Picture
    PB-27051451-0 20 on at

    Hi Alireza,

    we already tried to increase the framework parameters, but probably we will try to increase more as you suggested.

    Unfortunately I can't quickly enable the "Batch framework contention reduction" on this environment but we will plan also this change and test the export with this configuration.

    Thank you a lot for your help.

    I'll be back with some feedback after our tests.

    Regards,

    Paolo

  • Morten Albaek Profile Picture
    Morten Albaek 5 on at

    Hi Paolo,

    We are experiencing similar issues with our BYOD exports.

    Like you, we are using the REST API to start the export, and monitor the status of several data packages.

    Did you ever find a solution other than having to schedule the jobs?

    Regards,

    Morten

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

News and Announcements

Introducing our New Video Series: Community Spotlight

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the January Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

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

#2
Abhilash Warrier Profile Picture

Abhilash Warrier 280 Super User 2026 Season 1

#3
Martin Dráb Profile Picture

Martin Dráb 213 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans