VirtualSpy's Answers

Install Microsoft CRM 3.0 on a SQL Named Instance with MachineName invalid error

Situation

As part of redeploying CRM to be used for a test upgrade to CRM 4.0, the redeployment tool worked great to prepare the database, but the new installation of CRM 3.0 on a new box was the problem.  Because the test upgrade was to be kept separate from production, a new SQL instance was created.

Symptoms

The CRM 3.0 Environmental Diagnostics Wizard, gives a red X with the error MachineName value [server\instance] is invalid.

 

MachineName invalid error

 

Solution

Add the following registry key, which will enable the NEXT button in the wizard (you may not have to exit the wizard, simply go back, enter the registry key, and click NEXT):

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
• New DWORD value “IgnoreChecks” with a value of 1

NOTE:  The MSCRM key may not exist yet if it hasn’t been installed, in that case, you will have to create both the key and the DWORD value

Acknowledgements

Special thanks to Kale Davis with the registry hack in his blog: http://kaledavis.com/2006/12/30/using-crm-with-a-sql-named-instance/