The AsyncOperationBase and WorkflowLogBase tables grow very large and performance issues occur when you use many workflows in Microsoft Dynamics CRM 4.0

Fix it for me

To enable the hotfix automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.

Notes

• This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.

• If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Then, go to the "Did this fix the problem?" section.

Let me fix it myself

To enable this hotfix, follow these steps:

1. Click Start, click Run, type regedit, and then click
   OK.

2. In Registry Editor, locate the following subkey:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
   

3. Determine whether a DWORD registry entry that is named AsyncRemoveCompletedWorkflows exists. The value data of the AsyncRemoveCompletedWorkflows registry entry must be 1.

4. If the AsyncRemoveCompletedWorkflows registry entry does not exist, add the entry. To do this, follow these steps:
   

   1. Right-click MSCRM, point to
      New, click DWORD Value, and then type
      AsyncRemoveCompletedWorkflows in the
      Name box.

   2. Double-click
      AsyncRemoveCompletedWorkflows, and then type
      1 in the Value data box.

   3. Click Start, click
      Run, type iisreset, and then click
      OK.
      
      Note If the value in the Value data box for the AsyncRemoveCompletedWorkflows DWORD value reverts to 0, Microsoft Dynamics CRM will continue to retain the Workflow records in the database even if the tasks are completed.

Note This hotfix is proactive only. Therefore, when the hotfix is installed and activated, only new workflow records are deleted automatically. If the AsyncOperationBase and WorkflowLogBase tables are already large because of these workflow records, you must perform a cleanup of these tables by using the Microsoft SQL Server cleanup script that is included in the following Microsoft Knowledge Base article:

968520 Performance is slow if the AsyncOperationBase table becomes too large in Microsoft Dynamics CRM 4.0

Did this fix the problem?

• Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support.

• We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog or send us an email message.