Good Evening:

I am having a slightly odd issue installing configuration manager with a remote SQL server.  Bottom line is a few days ago I targeted a remote SQL instance that was already in use (did not know it had to be dedicated).  So I circled back and now getting errors finishing the install.

I see this in the setup log

ERROR: SQL server's Name '[SQLSERVERNAME\SYSCTR]' in sys.servers does not match with the SQL server name '[SQLSERVERNAME\SCCM]' specified during setup. Please rename the SQL server name using sp_dropserver and sp_addserver and rerun setup.

I searched high and low and what I found, was people were targeting another separate SQL server.  I will be on the same server, just targeting a separate instance.

EXEC sp_dropserver your old server name
GO

I found that however still a little lost on documentation, can anyone help me please?  Ie:  If I do have to do this in the SSMS, what instance do I need to be connected to, and what query syntax should i use?

Thanks for any help anyone can  provide!!!

• Edited by adam.wisowaty 21 hours 42 minutes ago

Did you changed the system name of SQL server after the installation of SQL?

Please follow the steps in this post: http://www.itexperience.net/2012/10/17/the-sql-server-name-specified-during-setup-must-match-the-name-in-sccm-2012/

Hi Idan:

Thanks for the reply - that is the thing.  The SQL Server has remained identical, server name never changed - lets say for example

SQLSERVERNAME\SYSCTR is what I targeted intially, I then targeted

SQLSERVERNAME\SCCM - the new instance I created.

I see the above errors in my logs, however I did follow that link, do I run that on the initial instance SYSCTR?

The thing is SYSCTR is a very busy DB and I really do not want to severe any connections.

• Edited by adam.wisowaty 21 hours 53 minutes ago

Secure  $$<Configuration Manager Setup><04-15-2014 23:59:53.927+300><thread=3132 (0xC3C)>
INFO: Getting SQL's server name from sys.servers on SQLSERVERNAME.domain.local\SCCM.  $$<Configuration Manager Setup><04-15-2014 23:59:53.959+300><thread=3132 (0xC3C)>
ERROR: SQL server's Name '[SQLSERVERNAME\SYSCTR]' in sys.servers does not match with the SQL server name '[SQLSERVERNAME\SCCM]' specified during setup. Please rename the SQL server name using sp_dropserver and sp_addserver and rerun setup.  $$<Configuration Manager Setup><04-15-2014 23:59:54.005+300><thread=3132 (0xC3C)>

SQLSERVERNAME = my SQL box, and I am attempting to use instance SCCM, where I initially targeted SYSCTR

• Edited by adam.wisowaty Wednesday, April 16, 2014 5:42 AM SP

I DID not create my SCCM DB prior  - also my language collation is not an issue.

Juke, what instance should I be connected to when executing that query - I saw and used the same syntax from the link above.  However, it states, your OLD server name and new server name

It is the SAME server, just a different instance.

1. Did you pre-create SCCM DB? if you did, delete it and let setup create it by itself.
2. SCCM only needs dedicate instance per SCCM SITE or if your original collation is not is not set to SQL_Latin1_General_CP1_CI_AS.

Is this SQL ONLY use for CM12?

If not then I would avoid performing any of the drop server commands as this might affect other DB / applications that access the server.

Garth:

Thanks for your reply - my exact concern.  This SQL server is used for quite a few other System Center products.  All with unique instances.

So the answer is no, this SQL server is used for many other items.

I am just stuck at this point, I even tried spinning up a brand new instance with the same results.

It is not best practice to show one SQL server for all SC product. For CM12 it is generally best practice to install SQL locally to CM12.

Thanks Garth-

I completely understand that it for best practice should live locally and best practice.  I will push our platform admin on this and DBA.

In the meantime, is there anyone that could chime in to a work around?

After executing the SP, you need to reboot the SQL Server, then run the ConfigMgr setup again.

EXEC sp_dropserver your old server name
GO

EXEC sp_addserver your current server name, local
GO