Article ID: 923818
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows registry
Consider the following scenario in Microsoft Dynamics CRM 3.0:
This problem is fixed in Microsoft Dynamics CRM 3.0 Update Rollup 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/922815/ )Update Rollup 2 is available for Microsoft Dynamics CRM 3.0
Installation informationInstall this hotfix on computers that are running Microsoft Dynamics CRM 3.0 server. This hotfix installs a registry entry that is named "ImportAllRelationships." The entry is installed in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM registry subkey. The value is set to 1. This value enables this hotfix.
Note When you install Update Rollup 2 (KB 927751), this registry hive is not automatically added. Therefore, you must add it manually. To do this, follow these steps.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
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:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
(http://support.microsoft.com/kb/887283/ )Microsoft Business Solutions CRM software hotfix and update package naming standards
Article ID: 923818 - Last Review: June 20, 2014 - Revision: 5.0
Contact us for more help