Installing a secondary System Center 2012 Configuration Manager site fails when using the default SQL instance name

Applies to: Microsoft System Center 2012 Configuration ManagerMicrosoft System Center 2012 R2 Configuration Manager


Consider the following scenario:
  • You have a primary Microsoft System Center 2012 Configuration Manager site.
  • On the primary site, you start the Create Secondary Site Wizard, and you enter the necessary information for the secondary site.
  • On the SQL Server Settings page, you select the Use an existing SQL Server database option, and in the SQL Server instance name, if applicable text box, you type MSSQLSERVER.

    NOTE By default, this text box is blank. However, you type the default instance name, MSSQLSERVER, in the text box.
  • You complete the wizard.

In this scenario, the secondary site installation is not completed successfully. Additionally, the following is logged in the ConfigMgrSetup.log file on the secondary site:

<date><time>Could not connect SQL Server 'master' db.
<date><time>Could not verify SQL Server is clustered or not because the setup could not connect to the SQL Server SCCM52659 or failed to run the query. 
<date><time>Configuration Manager v.Next Could not connect or execute SQL query.


To work around this problem, leave the SQL Server instance name text box blank if you want to install the secondary site to the default instance name.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.