Microsoft Lync Server 2013, Master Replicator Agent will not be functional until the AD connection point refers to a central management database that is in an available state. The Central management database is being moved out of %1 SQL instance. Resolution: Please ensure that the central management database was successfully moved to another pool and that the AD connection point was not manually changed.
Microsoft Lync Server 2013, Master Replicator Agent service is stopping. Reason: Machine '%1' is in cluster '%2' that does ...
Microsoft Lync Server 2013, Master Replicator Agent service is stopping. Reason: Machine '%1' is not defined in the topology. ...
Microsoft Lync Server 2013, Master Replicator Agent service is stopping. Reason: The service is trying to start as %1 service ...
Microsoft Lync Server 2013, Master Replicator Agent successfully registered with the back-end, but a schema or sproc version ...
Microsoft Lync Server 2013, Master Replicator Agent will not be functional until the AD connection point refers to a central ...
Microsoft Lync Server 2013, Master Replicator Agent will not be functional until the AD connection point refers to a central ...
Microsoft Lync Server 2013, Persistent Chat Compliance could not become active due to the following exception: %1 at %2. ...
Microsoft Lync Server 2013, Persistent Chat Compliance restored its connection to the Persistent Chat Compliance database ...
Microsoft Lync Server 2013, Persistent Chat Compliance restored its connection to the Persistent Chat database using connection ...