%11Site Control Manager is configured so that no more heartbeat site control files will be submitted to Hierarchy Manager.%12 Possible cause: If the site is functioning properly, this configuration will not produce any problems. However, if inter-site communication problems interrupt the proper replication of site control files and replicated site control files are lost, the site hierarchy might take a long time to recover or might not recover at all. During this time, parent sites might not have the most up-to-date configuration of this site. Solution: If this happens, you can either reconfigure Site Control Manager to submit heartbeat site control files again, or you can cause it to immediately submit a heartbeat site control file by stopping and restarting Site Control Manager using the Configuration Manager Service Manager application.%0
Site Control Manager created serial number %2 of the actual site control file %1.%12 This creation occurred in response to ...
Site Control Manager created the temporary file "%1".%12 In a moment, Site Control Manager will rename this file to %2, and ...
Site Control Manager deleted the "%1" item named "%2" from the actual site control file %5.%12 This deletion occurred as ...
Site Control Manager is beginning to process delta site control file "%1".%12 Configuration Manager Server Components and ...
Site Control Manager is configured so that no more heartbeat site control files will be submitted to Hierarchy Manager.%12 ...
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 ...