Jump to content

Search the Community

Showing results for tags 'install primary site'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 1 result

  1. We are running Configuration Manager 2012 SP1 with 1 CAS server, 2 Primary's, and a SQL server. I was tasked with bringing up a 3rd Primary site and I have run into some issues. I created the DB on the SQL server and set the static ports. The"Assess Server Readiness" tool did not show any issues so I continued with the install. I selected to join the primary site to an existing hierachy. During the install the following error came up: 5/16/2014 2:50:30 PM: ConfigMgrSetupWizard Verbose: 1 : Received error [setup failed to configure SQL Service Broker. Possible Cause: Each Configuration Manager site must have its own SQL Server instance. Verify that the selected SQL Server instance is not in use by another Configuration Manager site.] from native code. - I verified nothing else is accessing this instance. - If I pull up the SCCM console I can see the the new Primary site in the administration section and it is showing as an active site. My question is - How do I proceed from here? Do i need to uninstall the site and start over or is there a way to pick back up from where it failed? If I try and start the install again I get the error: 5/19/2014 4:52:06 PM: ConfigMgrSetupWizard Information: 1 : Setup detected an existing SCCM installation. Currently installed version is 7804 I have attached the install log.
  • Create New...