Error installing a new instance of MSCRM 4.0 "The instance name must be the same as computer name"

I am trying to install a new instance of CRM 4.0.
CRM App Server Name - CRM01
CRM DB Server Name - CRMDB (SQL Server 2008 R2)
CRM DB Instance Name - CRMDB\Dev

@@Servername = CRMDB\Dev
sp_helpserver = CRMDB\Dev

I get the error message "The instance name must be the same as computer name".

- I have tried the sp_dropserver and sp_addserver as many users have pointed out.
- The server name has never changed.
- In fact there was another instance of CRM installed on this same server but on a SQL Server 2005 instance and that worked fine

Now I am trying to install CRM on a SQLServer 2008 R2 instance.

Any help will be greatly appreciated.
CAHCOAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Feridun KadirPrincipal ConsultantCommented:
Is the SQL 2005 instance still on the same computer as the 2008 R2 instance?

One thing you can try to confirm whether it is an instance name problem is to run
select @@servername

Open in new window

against the 2008 R2 instance.
You can also try
EXEC sp_helpserver

Open in new window

as additional confirmation
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
I get the error message "The instance name must be the same as computer name".
You can't rename a SQL Server instance. You'll need to perform a new install and give the correct instance name during the setup.
0
CAHCOAuthor Commented:
Vitor,
I did not rename the instance.
The server had a 2005 instance and had CRM 4.0 installed on it.
Now I installed a new 2008 instance and am trying to install CRM 4.0 on the new 2008 instance.
Is that an issue? Is the fact that the same computer has both 2005 and 2008 instances, an issue?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

CAHCOAuthor Commented:
feridun,
Yes both 2005 and 2008 instances exist on the same server.
I had installed CRM 4.0 on the 2005 instance few years back. Now I am trying to install CRM 4.0 on the 2008 instance.
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Is that an issue? Is the fact that the same computer has both 2005 and 2008 instances, an issue?
Looks like it's an issue for the CRM since you can't have 2 instances sharing the same name. So, or you install a new instance in a new server or you upgrade the MSSQL 2005 to 2008 so it can use the same name.
0
Feridun KadirPrincipal ConsultantCommented:
It sounds like you have CRM 4 installed on a server, say SERVERA which uses SQL 2005
SQL 2005 and 2008 on a server, say SQLDB
And you are trying to install CRM 4 on another server, say SERVERB and want to use SQL 2008 on SQLDB.

If that is the case then that should work. The second "deployment" of CRM 4 on SQL2008 shouldn't know or care about the deployment on SQL 2005. Each deployment of CRM has its own MSCRM_CONFIG database and therefore requires its own instance of SQL. You will have a problem with CRM reporting extensions because that can only be instanced once on a server and therefore reporting can only be made to work for one of you CRM deployments. But that is for later, the first hurdle is to get CRM 4 installed on SQL 2008.

Is my summary at the beginning of the servers correct?
0
CAHCOAuthor Commented:
I was able to install on CRM 4.0 a server without a named instance.
Server Name = CRMDB
@@ServerName = CRMDB
sp_helpserver = CRMDB

Since the names all matched up, I was able to install.

My problem is when installing on a named instance.
Server Name = CRMDB
@@ServerName = CRMDB\Dev
sp_helpserver = CRMDB\Dev

**There are other named instances running on the server CRMDB.
0
CAHCOAuthor Commented:
Well, nothing helped. Looks like CRM 4.0 has a problem installing on a named instance.

Here is what I did to resolve the issue.

1 - Installed CRM pointing to another SQL Server (default instance. non named)

2 - Backed up the Config and Org databases

3 - Restored the Config and Org databases on the named instance

4 - Set the IgnoreChecks registry key to 1

5 - Changed settings to point CRM to the new server(Follow https://support.microsoft.com/en-us/kb/952934)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CAHCOAuthor Commented:
It seems to me that this is an issue with MSBR 4.0 that it cannot be installed on a named instance.
The workaround, as I found out, is to install on a default sql instance and then move the databases and IGNORECHECKS.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.