INCORRECT SERVICE BROKER PORT CAUSING REPLICATION FAILURE

[surferstylee]

SITE

 

I have a site with a CAS and two primary sites running SCCM
2012 SP1. Each site server has it’s DB
located on a dedicated remote SQL cluster running SQL Server 2008 R2 SP2.

Problem:

During the installation of each server, the Service Broker
Port was incorrectly configured with port 1433 (rather than the default
4022). Due to this mistake, the
replication between the site servers is not working. Both Primary sites are in read-only mode due
to the initial replication with the CAS not taking place.

The link between the CAS and the primary sites is showing
as:

 

fom the CAS: Link is being configured. In initializing data between the parent site
and the child site

 

from the Primary: Link Unknown. Link state is unknown

Question:

How can this be resolved???

 

1. Changing the the default port for SQL?

2. Changing the SSB port on the SQL?

3. If creating a new SQL instance and running a repair to
point CM at the new DB instance and changing the SSB port?

4. Wiping it all down and starting over?

 

 

[surferstylee]

RESOLVED

 

Managed to reconfigured the SSB port on the CAS then uninstalled the 2 primaries. Re-installed CM12 with new site codes and the proper SSB port.

 

There was an additional challenge with the SCCM 2012 prerequisite failing with CM DB already residing on the SQL cluster. Although the DB had been removed the following registry keys in BOLD need to be deleted:

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_SITE_SQL_BACKUP_<SITESERVERNAME>]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\OperationsManagement\Components\SMS_SITE_SQL_BACKUP_<SITESERVERNAME>]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing\SMS_SITE_SQL_BACKUP_<SITESERVERNAME>]