Error message when you apply a workflow rule to an entity in Microsoft Dynamics CRM 3.0: "SQL Server timeout expired. For more information, contact your system administrator"

When you apply a workflow rule to an entity in Microsoft Dynamics CRM 3.0, you receive the following error message: Specifically, this problem occurs if the following conditions are true:

• You create a workflow rule that updates a field for one of the following entities:
  • A quote
  • An order
  • An invoice
• You apply the workflow rule to the entity without assigning the entity.

This problem also occurs if the following conditions are true:

• You create a workflow rule that updates a field for one of the following entities:
  • A quote
  • An order
  • An invoice
• You apply the workflow rule to the entity when you assign the entity.
• You open the entity records.

When this problem occurs, other Microsoft Dynamics CRM 3.0 users cannot access or open records for the entity to which the workflow rule is applied.

This problem was corrected in Microsoft Dynamics CRM 3.0 Update Rollup 3.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Microsoft Dynamics CRM client for Microsoft Office Outlook

Microsoft Dynamics CRM client for Microsoft Office Outlook Compatibility Update

Microsoft Dynamics CRM server

Installation information

Install this hotfix on computers that are running the Microsoft Dynamics CRM 3.0 server software.

Prerequisites

You must have the Microsoft Dynamics CRM 3.0 server software installed to apply this hotfix.

Additionally, you must have Update Rollup 2 for Microsoft Dynamics CRM 3.0 installed before you apply this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

If you are prompted to restart the computer, you must restart the computer after you apply this hotfix.

Removal information

To remove this hotfix from a computer that is running Windows Server 2003, Windows XP, or Microsoft Windows 2000, use Add or Remove Programs in Control Panel. System administrators can use the Spuninst.exe tool to remove this hotfix from a computer that is running Windows Server 2003, Windows XP, or Windows 2000.

The Spuninst.exe tool is located in the %Windir%\$NTUninstallKB941448$\Spuninst folder. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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