locked
CRM 4.0 and SQL 2008 - The instance name must be the same as computer name. RRS feed

  • Question

  • Here is my scenario. I need to create a demonstration environment for CRM, SharePoint, Performance Point and a whole slew of other tools. This environment must be portable, so it all needs to be self contained and useable from a (rather grunty) laptop.

     

    What I have done is:

     

    1. Installed Windows 2008 Enterprise on a new virtual image.

     

    2. Enabled and configured:

    2.1 Active Directory Domain Services

    2.2 Application Server

    2.3 DNS Server (Part of ADDS role)

    2.4 File Services (For 2003 Indexing service)

    2.5 Web Server (IIS)

     

    3. Install SQL Server 2008 Enterprise with all options turned on. I configured this with separate accounts for the various services as per best practice requirements.

     

    I used defaults where applicable and made preciously few tweaks to the system. Keep it simple, in essence. Now I am getting stuck on the CRM 4.0 installation with, as far as my searches thus far have turned up, the infamous "The instance name must be the same as computer name." error.

     

    1. SQL Server is installed to it's default instance.

    2. The computer name has not changed.

    3. The local machine is not visible to the Dynamics CRM 4.0 installer when viewing the list of SQL Servers. Other SQL Servers on the network are visible though.

    4. I can connect to the SQL Server using sqlcmd -S[Servername]

    5. I am not running SQL Server Developer edition, but named pipes are enabled (Trying everything I can think of)

     

    I suspect the answer is fairly simple and easy, but - does anyone have a recommendation or a suggestion as to what I can try? How is the CRM 4.0 installer attempting to test that so I can replicate it and perhaps get a more detailed error message?

     

    Thank you in advance!

    Wednesday, September 17, 2008 4:38 AM

Answers

  • Alright, I have found the problem. The warning message as it was given was indeed correct. The Instance Name did not match the Computer name the installer was discovering.

     

    My computer name was set to W2K8EnterpriseServer. A rather unimaginative name, but suitably descriptive for the demonstration setup. This had been truncated to W2K8ENTERPRISES for the NETBIOS name and was the name that SQL Server had used.

     

    When I ran select @@server_name; it responded with W2K8ENTERPRISES, which was the name I provided to the CRM 4.0 installer. However, when I clicked [Back] [Back] a few times the CRM installer had changed that name to W2K8EnterpriseServer.

     

    I am guessing that it is somehow resolving the slightly richer name and getting that and electing to use that, rather than the name entered. So, I changed the computer name to W2K8ENTERPRISES and rebooted.

     

    It is most assuredly not a pretty name, but once I had done that what the CRM 4.0 installer was picking up was matching what SQL Server 2008 was picking up and the installation could complete.

     

     

    Thursday, September 18, 2008 12:26 AM

All replies

  • Hi Pascal

     

    I may be wrong here but I am sure that CRM 4.0 doesn't support SQL Server 2008 yet.  This may of course have changed since the last time I did an install so if anyone knows differently I would be happy to be proved wrong.

     

    http://www.microsoft.com/dynamics/crm/product/systemrequirements.mspx

     

    Regards,

     

    Douglas

    Wednesday, September 17, 2008 12:46 PM
  • Hi Douglas,

     

    Thank you for the response. I was slightly encouraged by some of the results I'd seen online:

     

    http://forums.microsoft.com/Dynamics/ShowPost.aspx?PostID=3815279&SiteID=27

    http://blog.customereffective.com/blog/2008/08/microsoft-dyn-1.html

     

    And then a few support articles that indicate they are releasing patches:

    http://support.microsoft.com/kb/952601

    http://support.microsoft.com/kb/952602

     

    Those gave me the impression that it should be possible in some form at least. But, it would seem this is not possible then, unfortunately.

     

    Would you by any chance know if they have a fully supported release date in mind? I'll contact Microsoft here in NZ and see if they have any advice on this in any event, it would be useful to know then when we can use this because we will need this configuration in the nearby future.

     

    Regards,

     

    Pascal

    Wednesday, September 17, 2008 8:23 PM
  • Alright, I have found the problem. The warning message as it was given was indeed correct. The Instance Name did not match the Computer name the installer was discovering.

     

    My computer name was set to W2K8EnterpriseServer. A rather unimaginative name, but suitably descriptive for the demonstration setup. This had been truncated to W2K8ENTERPRISES for the NETBIOS name and was the name that SQL Server had used.

     

    When I ran select @@server_name; it responded with W2K8ENTERPRISES, which was the name I provided to the CRM 4.0 installer. However, when I clicked [Back] [Back] a few times the CRM installer had changed that name to W2K8EnterpriseServer.

     

    I am guessing that it is somehow resolving the slightly richer name and getting that and electing to use that, rather than the name entered. So, I changed the computer name to W2K8ENTERPRISES and rebooted.

     

    It is most assuredly not a pretty name, but once I had done that what the CRM 4.0 installer was picking up was matching what SQL Server 2008 was picking up and the installation could complete.

     

     

    Thursday, September 18, 2008 12:26 AM
  • Found this link which may be of some interest to you if you haven't seen it already:

     

    http://blog.customereffective.com/blog/2008/08/microsoft-dyn-1.html

     

    Regards,

     

    Douglas

     

    Monday, September 22, 2008 1:59 PM
  • Hi guys,

    I had the same problem here but it was the SQL Server.

    Solution:

    First of all go to your SQL 2008 and execute the query "select @@SERVERNAME", if it returns NULL the problem is your SQL 2008 and you have to resetup the server name. It is simple, just run the procedure below:

    sp_addserver 'new_name', 'local'

    Here is the MSFT article where explains how to do that http://support.microsoft.com/kb/303774

    After that you can try to install the CRM and it will works.

     

    Cheers,

     

    Cleiton

    Monday, July 12, 2010 7:09 PM