locked
SCCM 2012 - Secondary Site Install Errors RRS feed

  • Question

  • Just installed A secondary site, receiving DB replication errors.

    Environment is SCCM 2012 R2 SP1 with no CU's applied.

    Pre- Req  checks were all green. Secondary site install completed with no issues.

    \Administration\Overview\Site Configuration\Sites shows the new site as active.

    Database replication is stuck at "Link is being configured". Replication link analyzer states: SQL Broker login is missing for site:XXX on database server: YYY\CONFIGMGRSEC.

    Recreate SQL Broker Login does nothing. 

    SQL Server logs on the primary site server's DB shows:

    2017-03-28 10:18:22.97 Logon       Service Broker login attempt failed with error: 'Connection handshake failed. The login 'public' does not have CONNECT permission on the endpoint. State 84.'.  [CLIENT: XXXXX].

    The setup. Primary Site server with remote SQL DB.

    One thing to note about the SQL DB for primary site DB: the the SQL DB was setup to host system DB files on an SMB share. The DB instance files for CM_XXX are local on the SQL DB server.

    The secondary site is being installed using default options - SQL express.

    Please let me know if more information is required for help.



    • Edited by NeerajV Tuesday, March 28, 2017 7:02 PM more info.
    Tuesday, March 28, 2017 5:53 PM

All replies

  • Why aren't you using a local SQL Express installation for the secondary site?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, March 28, 2017 6:33 PM
  • Secondary site is getting a local SQL express installation only. The primary database's files are on SMB shares.
    Tuesday, March 28, 2017 6:45 PM
  • Sorry, missed that.

    The error shown above is a connection error though. Have you reviewed the security event logs as well as the SQL Server logs on the server hosting the primary site's DB instance?

    Is the secondary site server in a trusted domain?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, March 28, 2017 7:04 PM
  • Yes it is in the same domain.
    Tuesday, March 28, 2017 8:28 PM
  • What about the logs?

    As noted, from the error messages, permission simply are not configured correctly. This should be taken care of automatically but if someone has changed anything from the default configuration in your SQL instance, then YMMV.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, March 28, 2017 8:38 PM