The server selected for next hop could not be reached, or did not reply. A server selected as a proxy target for HTTP traffic could not be reached or did not reply: %1. Performance Counter Instance: %2 Failure occurrences: %3, since %4. Failure Details: %5 Cause: The remote server may be experiencing problems or the network is not available between these servers. Resolution: Examine the event logs on the indicated server to determine the cause of the problem.
The server failed to import a shared session key due to invalid signature in a referrer identity digest. In the past %1 minutes, ...
The server has returned RPC Access Denied responses. %1 RPC Access Denied responses were sent due to connecting clients not ...
The server must be restarted before installation can continue. To continue the installation after the server has restarted, ...
The Server received conferencing requests destined for another Pool. Target Pool: %1. Cause: Incorrect routing configuration. ...
The server selected for next hop could not be reached, or did not reply. A server selected as a proxy target for HTTP traffic ...
The server was configured to use a Clearinghouse %1]. Discovery of federation partners is not supported when using a Clearinghouse. ...
The service cannot start because the global configuration settings are missing. Cause: The Lync Server 2013, Response Group ...
The service cannot start because the pool configuration is not valid. Cause: The Lync Server 2013, Response Group Service ...
The service could not be started - error accessing perfcounters. AV MCU does not have the right permissions. Make sure to ...