Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message when you try to install Microsoft Dynamics CRM 3.0 on a computer that is running a named instance of SQL Server: "MachineName value [server_name]\[instance_name] is invalid"


View products that this article applies to.

Symptoms

When you try to install Microsoft Dynamics CRM 3.0 on a computer that is running a named instance of Microsoft SQL Server, you receive the following error message in the Environment Diagnostics Wizard:
"MachineName value server_name\instance_name is invalid"
Note The server_name placeholder is a placeholder for the name of the computer that is running SQL Server. The instance_name placeholder is a placeholder for the name of the instance of SQL Server.

↑ Back to the top


Resolution

To resolve this problem, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services telephone numbers and for information about support costs, visit the following Microsoft Web site:

↑ Back to the top


More information

Verify that the NT Authority\Network Service account has the correct access

In Microsoft Windows Server 2003 and in Microsoft Small Business Server 2003 environments, you must verify that the NT Authority\Network Service account has the correct access to the Microsoft CRM and SQL Server Reporting Services databases after you install Microsoft CRM. To do this, follow these steps:
  1. On the computer that is running SQL Server, click Start, click All Programs, click Microsoft SQL Server, and then click Enterprise Manager.
  2. Expand Microsoft SQL Server, expand SQL Server Group, expand the name of the computer that is running SQL Server, expand Security, and then click Logins.
  3. Right-click NT Authority\Network Service, and then click Properties.

    Note If the NT Authority\Network Service account is not listed as a login, you must add the NT Authority\Network Service account. For more information, see the "How to add the NT Authority\Network Service account" section.
  4. Click the Database Access tab, and then verify that the account has the correct permissions for the correct databases, as shown in the table in the "Databases and roles" section.

How to add the NT Authority\Network Service account

If the NT Authority\Network Service account is not listed as a login, follow these steps to add the account:
  1. Expand Microsoft SQL Server, expand SQL Server Group, expand the name of the computer that is running SQL Server, expand Security, and then click Logins.
  2. Right-click Logins, and then click New Login.
  3. Type NT Authority\Network Service, and then click OK.
  4. Click the Database Access tab, and then grant the correct permissions for the correct databases, as shown in the table in the "Databases and roles" section.

Databases and roles

Collapse this tableExpand this table
DatabaseRoles
Company_Name_MSCRMpublic and db_owner
Company_Name_Metabasepublic and db_owner
ReportServerpublic and RSExecRole
ReportServerTempdbpublic and RSExecRole
masterpublic and RSExecRole
msdbpublic and RSExecRole

Support for named instances of SQL Server

When Microsoft CRM 3.0 was released, we did not support installing the Microsoft CRM databases on a computer that is running a named instance of SQL Server. After the release, additional testing was performed. Therefore, we now support installing Microsoft CRM on a computer that is running a named instance of SQL Server.

↑ Back to the top


Keywords: KB921971, kberrmsg, kbmbsinstallation, kbtshoot, kbmbscrm40no

↑ Back to the top

Article Info
Article ID : 921971
Revision : 4
Created on : 2/8/2007
Published on : 2/8/2007
Exists online : False
Views : 284