Steps to Configure Replicator with Cloned Web Applications (4281718)

Symptom

Internally, Replicator uses a web application’s GUID to uniquely identify the web application in your Replication Network. Cloned web applications that have the same GUID will cause issues with Replicator.
There are no specific errors to look for when this happens. We’ve seen confusing messages on the Monitor Replication page around package transfers and misleading indicators of where the package originated from. For example, an inbound package may be marked as an outbound package.
In Replicator 5.1, you can see the GUID Replicator users on the Configure Web Application Central Administration page under Advanced Settings.

This was caused by a design choice in earlier versions of Replicator.

Using Replicator 5.1, you can assign a new GUID to a web application. This GUID is only used by Replicator and will not have any impact on your SharePoint environment.

Run either the repadm –o ConfigureWebApplication or the Replicator Management Shell Set-ReplicatorWebAppConfig command with the –ChangeExternalID argument.

If you had previously configured a connection to this web application, then you must refresh the connection, either by editing it on the Configure Replication Connection Central Administration page or by running the repadm –o RefreshConnections command.