Applies to Product - Dynamics 365 Finance
What’s happening?
Customers reported system hang issues that resulted in all users being blocked, as well as specific batch jobs locking the BATCH table, preventing other processes from executing.
Reason:
The underlying cause identified was SQL blocking issues, where one batch job was locking the BATCH table, leading to a complete halt of BatchOS threads. Additionally, high CPU usage was observed due to a custom process running concurrently, which disrupted the operation of other batch processes.
Resolution:
- For the SQL blocking issue, it was monitored and identified that the blocking was resolved by stopping the blocking process through the system monitoring tools.
- To mitigate the BATCH table lock issue, the following recommendations were provided:
- Reduce execution count to allow other processes to access shared resources.
- Divide execution count into smaller chunks to distribute the load more effectively.
- Leverage batch operations for actions consuming heavy resources.
- Schedule batch operations during off-hours to minimize competition for resources.
- A thorough review and redesign of the custom code was recommended to optimize resource management and efficiency, ensuring it operates within acceptable CPU usage limits.
- Ensure PBS Best Practices followed - PBS Best Practices