Article ID: 2255979 - View products that this article applies to.
Consider the following scenario in Microsoft Dynamics CRM 4.0:
This problem occurs because the Microsoft CRM Setup Wizard maintains a dictionary of roles that are required to be installed on the server. When you select the Custom installation type, the application server role is added to a RoleManager dictionary. Additionally, another list stores the user-specified role names. When you change the installation type from Custom to Typical, the RoleManager dictionary is updated to use the FullServer role. However, the list that stores the names is not updated. During the installation, the list is written to the registry. When you run a repair process, the roles that are required on the server are read from the registry. Because the incorrect values were written to the registry during the installation, only the user-specified roles are reinstalled on the server. Other roles, such as the Async service role, are missing.
A setup update is available from Microsoft. When you install Microsoft Dynamics CRM 4.0, or when you upgrade to Microsoft Dynamics CRM 4.0, you can check for setup updates. If you select the option to check for setup updates, the application downloads any new setup updates and applies them to the installation while the setup process is running.
Installation informationYou can use the Update Installation Files option during setup of Microsoft Dynamics CRM 4.0 to obtain this fix.
For more information about how to use the Update Installation Files option or how to manually download the setup update, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/948917/ )How to obtain the setup updates for Microsoft Dynamics CRM 4.0
PrerequisitesNo prerequisites are required to apply this setup update.
Removal informationThe setup update cannot be removed.
Article ID: 2255979 - Last Review: October 15, 2010 - Revision: 1.0