Select the product you need help with

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

Article ID: 968755 - View products that this article applies to.

SYMPTOMS

You use many workflows in Microsoft Dynamics CRM 4.0. The AsyncOperationBase and WorkflowLogBase tables grow very large, and performance issues occur.

Back to the top | Give Feedback

This issue occurs because, when the workflow rules are fired, a workflow instance and a workflow record are created in the AsyncOperationBase and WorkflowLogBase tables of the MSCRM database. However, when the workflow instance is completed, the workflow record remains in the database. Therefore, the AsyncOperationBase and WorkflowLogBase tables continue to grow. Eventually, performance decreases.

Note The AsyncOperationType property for these records is set to 10.

Back to the top | Give Feedback

RESOLUTION

This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

949256

(http://support.microsoft.com/kb/949256/ )

Microsoft Dynamics CRM 4.0 updates and hotfixes

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756

(http://support.microsoft.com/kb/322756/ )

How to back up and restore the registry in Windows

After you install the hotfix, to have us enable this hotfix for you, go to the "Fix it for me" section. If you prefer to enable the hotfix yourself, go to the "Let me fix it myself" section.

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.

Fix this problem
Microsoft Fix it 50835

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:

Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
Determine whether a DWORD registry entry that is named AsyncRemoveCompletedWorkflows exists. The value data of the AsyncRemoveCompletedWorkflows registry entry must be 1.
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

(http://support.microsoft.com/kb/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
(http://support.microsoft.com/contactus)
.
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
(http://blogs.technet.com/fixit4me/)
" blog or send us an email
(mailto:fixit4me@microsoft.com?Subject=KB)
message.

Back to the top | Give Feedback

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684

(http://support.microsoft.com/kb/824684/ )

Description of the standard terminology that is used to describe Microsoft software updates

For more information about Microsoft Business Solutions CRM software hotfix and update package terminology, click the following article number to view the article in the Microsoft Knowledge Base:

887283

(http://support.microsoft.com/kb/887283/ )

Microsoft Business Solutions CRM software hotfix and update package naming standards

Back to the top | Give Feedback