Batch jobs can create a problem when the database is restored or refreshed from one environment to other environment.
Given below the trouble shooting steps and solution to handle this issue.
- Check if there are any batch jobs in ‘Executing’ state . If yes, cancel them. These jobs consume most of the threads in the system.
- Check if the AOS is configured as ‘Batch Server’ . This…
Continue Reading AnithaEswaran’s Article on their blog
Batch job not executing – Ax2012
Batch jobs can create a problem when the database is restored or refreshed from one environment to other environment. Given below the trouble shooting steps and solution to handle this issue. Check if there are any batch jobs in ‘Executing’ state . If yes, cancel them.
Blog Syndicated with AnithaEswaran’s Permission
More About This Author
Array
Dyn365O2021.08.31Purge Lifecycle Services assets – New feature in LCS
Dyn365O2021.07.05Import Data using Azure Data Factory – D365FO DIXF(Recurrence)
Dyn365O2021.06.28Troubleshooting Key vault script execution -Data Export Tool CE
Dyn365O2021.06.22Data copy from D365 to Azure Db – Data Export Service Tool
