%11Site Control Manager will ignore this site configuration change request ("%1" from site "%2").%12
This change request was already processed as part of an older delta site control file. Hierarchy Manager at site "%2" will continue to submit this site configuration change request until it receives a copy of the new actual site control file from site "%3" that confirms the change was successfully processed. If you find that Hierarchy Manager continues to submit this site configuration change request for an extraordinarily long time, there might be a problem with Hierarchy Manager at any of the sites between and including sites "%2" and "%3". Or, if "%2" and "%3" are different sites, there might be a communication problem between them or any sites between them. If you suspect this is happening, check for Warning and Error status messages from Hierarchy Manager, Replication Manager, Scheduler, and the Sender components at these sites.%0
Site Control Manager modified the properties of the "%1" item named "%2" in the actual site control file %7.%12 This modification ...
Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager as a heartbeat ...
Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager as a heartbeat ...
Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager.%12 This ...
Site Control Manager will ignore this site configuration change request ("%1" from site "%2").%12 This change request was ...
Site Control Manager will maintain copies of the %1 most recent actual site control files in the directory "%2".%12 The actual ...
Site Control Manager wrote a copy of the actual site control file %1 to %2.%12 In a moment, Site Control Manager will move ...
Site databases cannot be upgraded when they are configured for replication. Before you begin the upgrade process, disable ...
Site has finished processing resync request for replicationgroup %1]. Please refer to dmpuploader.log for further details.%0 ...