Incoming client connection failed to establish. Over the past %1 minutes Lync Server has experienced incoming connection failures %2 time(s). The error code of the last failure is 0x%3 (%4) while handling a connection from host "%5". Cause: This can occur if the connection attempt by the client was rejected due to the client's failure to provide appropriate credentials, or failure to complete TLS negotiation, because the client dropped the connection before it was completed, or due to high load on the server. Resolution: Verify the connection came from a trustworthy client.
In order to run the software, Windows Powershell V2 or later must be installed. Please install Windows Powershell V2 or later ...
In the published topology, the site that you are deleting includes the pool ({0}) that hosts the Central Management Server. ...
Inbound Routing Application is running under an account that is not authorized to connect to the server. Cause: The RTCSRV ...
Inbound Routing Application is unable to load routing script defined in the InboundRouting.exe.config key='%1' path='%2' ...
Incoming client connection failed to establish. Over the past %1 minutes Lync Server has experienced incoming connection ...
Incoming MSODS data is not valid. TenantId: '%1', ObjectId: '%2' Message=%3 Exception: %4 Stack Trace: %5 Cause: Data coming ...
Incomplete hosted voicemail configuration HostedVoicemailPolicy is not completely configured for %1]. Cause: Destination ...
Incomplete voicemail configuration. The phone number of Exchange UM Auto Attendant or the Subscriber Access Number for users ...
Initialization of Authorization Resource Manager failed. Error: 1!_HRX! (%2!_HRM!). Cause: Please look at the error message ...