As you learn about Workflows in Microsoft Dynamics CRM , you may encounter an issue where you find a workflow stuck in “In Progress”. You can see an example of this below. Sometimes these workflows might get processed after a long delay.
Today we’ll go over how to resolve this issue in an on-premise instance of Microsoft Dynamics CRM. The issue might be related to a missing or wrong value in the MSCRM_CONFIG database.
- To find out, run the following SQL query and AsyncSdkRootDomain value should be same as the remaining two.
Select ColumnName, NVarCharColumn
- If they don’t have the same values, then update AsyncSdkRootDomain value using the following statement. In this ‘<servername>’, should be same value as ADSdkRootDomainresult.update [MSCRM_CONFIG].[dbo].[DeploymentProperties]
- Restart CRM Async Service and the workflows should start working again.
WARNING: Always backup your databases if you are updating data in SQL directly.
If this doesn’t resolve your issue, consider opening a request with PowerObjects for support.