Microsoft Lync Server 2013, File Transfer Agent successfully registered with the back-end, but a schema or sproc version mismatch was detected. The service will not start until this problem is resolved. Database version: Actual = %1, Expected = %2. Cause: Installation error. Resolution: Ensure both Microsoft Lync Server 2013, File Transfer Agent and back-end were installed or modified by the same installation package.
Microsoft Lync Server 2013, File Transfer Agent service is stopping. Reason: Connection point in AD changed from '%1' to ...
Microsoft Lync Server 2013, File Transfer Agent service is stopping. Reason: Machine '%1' is in pool '%2' that does not have ...
Microsoft Lync Server 2013, File Transfer Agent service is stopping. Reason: Machine '%1' is not defined in the topology. ...
Microsoft Lync Server 2013, File Transfer Agent service is stopping. Reason: The service is trying to start as %1 service ...
Microsoft Lync Server 2013, File Transfer Agent successfully registered with the back-end, but a schema or sproc version ...
Microsoft Lync Server 2013, File Transfer Agent will not be functional until the AD connection point refers to a central ...
Microsoft Lync Server 2013, File Transfer Agent will not be functional until the AD connection point refers to a central ...
Microsoft Lync Server 2013, Master Replicator Agent is trying to connect to a backend that whose state does not match with ...
Microsoft Lync Server 2013, Master Replicator Agent service could not be started. Exception information: %1. Cause: Startup ...