You cannot install Microsoft Dynamics CRM 2011, install Update Rollups for Microsoft Dynamics CRM 2011, or create additional organizations in Microsoft Dynamics CRM 2011 without system administrator privileges in Microsoft SQL Server

Symptoms

When you install Microsoft Dynamics CRM2011, install Update Rollups for Microsoft Dynamics CRM 2011, or when you create additional organizations in an existing deployment in Microsoft Dynamics CRM 2011, you must have system administrator privileges in Microsoft SQL Server. You expect to install Microsoft Dynamics CRM 2011, install Update Rollups for Microsoft Dynamics CRM 2011, and to create additional organizations in Microsoft Dynamics CRM 2011 without system administrator privileges in Microsoft SQL Server.

Resolution

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 the problem described in this article. 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:

http://support.microsoft.com/contactus/?ws=support


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.

Installation information

Install this hotfix on computers that are running the Microsoft Dynamics CRM 2011 Server components.

Case 1: When creating a new Dynamics CRM deployment by running Dynamics CRM Setup

To enable this hotfix when using Dynamics CRM Server setup to create a new deployment, follow these steps:

1. Install the hotfix.

Note: The language for the hotfix must match the language of the Dynamics CRM Server package to be installed.

Note:This hotfix contains one database file, a DLL file, a command script file, and three Microsoft SQL Server script files.

2. Locate the following files that are installed by the hotfix:

o Mscrm9688_1033mscrm7333.mdf

o HardDeleteJob.sql

o SiteWideCleanupJob.sql

o CreateOrgAndClrAssembly.cmd

o CreateOrgAndClrAssembly.sql

3. When logged into the SQL server as a SQL administrator, execute the windows command script CreateOrgAndClrAssembly.cmd. This command script will perform the following operations:

o Copy the Microsoft.Crm.SqlClr.dll and mscrm9688_1033.mdf file to the specified data directory on the SQL server.

o The database file name will be copied as orgname_mscrm.mdf

o A database for the Dynamics CRM Organization will be created as orgname_mscrm

o Microsoft Dynamics CRM SQL helper assembly will be created along with an associated encryption key, login, and helper function in the organization database.

Note: this CLR assembly is not enabled by default. To gain the performance benefit of this CLR integration, CLR integration must be enabled on the SQL server instance hosting the Dynamics CRM Organization database.


Usage:
CreateOrgAndClrAssembly OrganizationName DataPath [Instance]

OrganizationName: Specifies the Organization Unique Name.

DataPath:Specifies the Data path to use for the Dynamics CRM organization database files and the CLR helper assembly

Instance: Optional parameter in which the SQL instance name can be specified
If not specified, the default instance will be assumed

4. Create a SQL Server logon account for the CRM installing user and grant the user create database rights. The Microsoft SQL Server dbcreator role is required for the installing user to create the database MSCRM_CONFIG through setup.

5. For the database attached in step 3, change the owner to the user who will install Microsoft Dynamics CRM 2011.

6. Create a Microsoft SQL Server logon account for the following Microsoft Dynamics CRM security groups, and then grant the groups access to the attached database: 

o Priv Reporting Group

o Reporting Group

o SQL Access Group

7. On the computer on which you want to install the Microsoft Dynamics CRM Server 2011, add the following registry entries:

o HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM

o HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM\CrmAdminIsNotSqlSysAdmin

The CrmAdminIsNotSqlSysAdmin DWORD value is 1.

o HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM\IgnoreChecks

The IgnoreChecks DWORD value is 1.

8. Create a configuration file that can be used to install Microsoft Dynamics CRM 2011 to specify use of pre-created security groups.

Note When you create the configuration file, you must use preconfigured security groups.
For more information about how to create the configuration file, click the following TechNet article:

Sample server XML configuration file for installing with pre-created groups

9. Use the configuration file that you created to install Microsoft Dynamics CRM 2011.

10. After you install Microsoft Dynamics CRM 2011, log on to the instance of Microsoft SQL Server by using the credential of the Microsoft SQL Server administrator, and then install the following script files on the MSCRM_CONFIG database:

o SiteWideCleanupJob.sql

o HardDeleteJob.sql

One way to do this would be to use sqlcmd like the following:

o sqlcmd –s . –d MSCRM_CONFIG –i SiteWideCleanupJob.sql

o sqlcmd –s . –d MSCRM_CONFIG –i HardDeleteJob.sql

11. On the Organization Settings page, the Unique Database Name must match the OrgName portion of the database name used in step 1.



Case 2: Adding an organization to an existing Dynamics CRM deployment.

To add an additional organization to an existing deployment, follow these steps before you create the new organization using Microsoft Dynamics CRM Deployment Manager:

Note: language code of the hotfix package must match the base language of the organization to be created. If the organization base language is different from the Dynamics CRM server package, the Dynamics CRM language pack matching the organization language must be installed on the Dynamics CRM server from which Dynamics CRM Deployment Manager will be run.

1. When logged into the SQL server as a SQL administrator, execute the windows command script CreateOrgAndClrAssembly.cmd. This command script will perform the following operations:

o Copy the Microsoft.Crm.SqlClr.dll and mscrm9688_1033.mdf file to the specified data directory on the SQL server. o The database file name will be copied as orgname_mscrm.mdf
o A database for the Dynamics CRM Organization will be created as orgname_mscrm
o Microsoft Dynamics CRM SQL helper assembly will be created along with an associated encryption key, login, and helper function in the organization database.

Note: this CLR assembly is not enabled by default. To gain the performance benefit of this CLR integration, CLR integration must be enabled on the SQL server instance hosting the Dynamics CRM Organization database.

Note The OrgName placeholder represents the actual organization name.
2. For the newly attached database, change the owner to the Microsoft Dynamics CRM deployment administrator. 

3. On the computer on which you will use Microsoft Dynamics CRM Deployment Manager to create the additional organization, add the following registry entries:

o HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM\CrmAdminIsNotSqlSysAdmin

The CrmAdminIsNotSqlSysAdmin DWORD value is 1.

o HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM\IgnoreChecks

The IgnoreChecks DWORD value is 1.
4. If the SQL server instance used to host the new organization database does not also host the MSCRM_CONFIG database, it will be necessary to create SQL logins for the following Microsoft Dynamics CRM security groups, and then grant the groups access to the organization database: 

o Priv Reporting Group

o Reporting Group

o SQL Access Group
5. Use the Microsoft Dynamics CRM Deployment Manager New Organization wizard to create a new organization. When specifying Organization Settings:

o The Unique Database Name must match the OrgName portion of the database name used in step (a.)

o The Base Language must match the language of the original mscrm9688_lcid.mdf database file used in step (a.)

Note: The Diagnostics Page will report an error that the database files already exist. This is expected. If the Next button is not enabled, ensure the registry keys specified in step (c.) above are set, click Back, then Next again to rerun the diagnostics.