Hi,

 

Whenever I run Replication Link Analyzer between my CAS and Primary Site, I receive this error message:

Please Update conflicting SQL Server Service Broker port for sites CAS and Primary Site on SQL Server.

*Both sites use separate instances installed on the same SQL server.

 

But I don't see where the conflict is.

The Parent Site (CAS) uses 4022 while the Child Site (Primary Site) uses 4023.

What is conflicting? How should I resolve it?

If I change the Primary Site to use 4022 as well, replication breaks down entirely.

Thank you.

Are both the CAS and Primary site installed on the same SQL server? if so it is never recommend to share the same SQL server for both a CAS and Primary site.

For other that see this post, 99% of the time a CAS is only need if you are managing over 100,000 devices.

Hi,

I understand it's not recommended but this is the infrastructure I have inherited.

I would prefer if someone has useful suggestions towards a solution.

Does the logfile of the replication link analyzer contain anything useful (e.g. port numbers)?

Hi,

You need to configure the different SQL Port and SQL Broke service port e.g.

SQL port 1433 SQL Broke Service port 4022 for CAS instance

SQL port 1434 SQL Broke Service port 4023 for PRI instance

Please refer to the thread below:

SCCM central site and primary site use the same SQL SERVER with two Instance.

http://social.technet.microsoft.com/Forums/en-US/aacafd83-ac65-4c8c-a9e8-0ede3c8f8228/sccm-central-site-and-primary-site-use-the-same-sql-server-with-two-instance?forum=configmanagerosd

That is how it has been set up and runing Replication Link Analyzer gives the error message.

Hi,

Please review the log ReplicationLinkAnalysis.log as Torsten mentioned.

For more information, please review the link below:

Tips for troubleshooting SC 2012 Configuration Manager Data Replication Service (DRS)

http://blogs.msdn.com/b/minfangl/archive/2012/05/16/tips-for-troubleshooting-sc-2012-configuration-manager-data-replication-service-drs.aspx

Hello,

Have same problem. Did you solve it?

Thanks.

Hello,

Have same problem. Did you solve it?

Thanks.

No solutions provided - everyone who replied didn't bother reading my post properly.

Also got the same problem

Even if the others have not understood it, have you solved it ?

It's not that we didn't read or understand it, it's that it's terrible design and makes no sense to have a single DB server host both a primary and CAS. You shouldn't be doing this in the first place. It's like asking how do I stop the other drivers from honking at me when I drive down the freeway going the wrong way?