Microsoft Dynamics CRM stops responding when you customize Microsoft Dynamics CRM to add a new 1-to-Many relationship between two entities

When you customize Microsoft Dynamics CRM 3.0 to add a new 1-to-Many relationship between two entities, Microsoft Dynamics CRM stops responding. Additionally, the CPU usage of the server that is running Microsoft SQL Server reaches 100 percent.

This problem occurs if you use the Referential, Restrict Delete relationship behavior type for one of the relationships.

For example, consider the following scenario:

• You create two custom entities. The entities are named Entity A and Entity B.
• You create a 1-to-Many relationship between Entity A and Entity B. This 1-to-Many relationship uses the Referential, Restrict Delete relationship behavior type.
• Then, you create another 1-to-Many relationship between Entity B and Entity A.

In this scenario, the SQL Server Profiler monitor is repeating SQL statements. This problem indicates that Microsoft Dynamics CRM is in an infinite loop.

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: 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 server

Prerequisites

To apply this hotfix, you must have installed the update that is described in Microsoft Knowledge Base article 925874. For more information about this update, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

If you are prompted, restart the computer after you install the hotfix.

Removal information

To remove this hotfix from a computer that is running Microsoft Windows Server 2003, Microsoft 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 Microsoft Windows Server 2003, Microsoft Windows XP, or Microsoft Windows 2000.

The Spuninst.exe tool is located in the %Windir%\$NTUninstallKB934859$\Spuninst folder.

Installation information

Install this hotfix on computers that are running the Microsoft Dynamics CRM Server and the Microsoft Dynamics CRM client.

For more information about the terminology that is used to describe Microsoft software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base: