Many security events have been identified by the proxy stack. In the past %1 seconds, %2 security events have been identified by the proxy stack. A large number of security events could indicate that the server is under attack. The last event was: %3 Cause: The server may be under attack, or there might be a configuration problem that is causing errors. Resolution: Launch the Lync Server 2013 Logging Tool. Select the "SIPStack" component, the "Errors" level and the TF_SECURITY flag. Review the events reported to the trace log using the "Analyze Log Files" feature of the logging tool.
Maintenance task was executed successfully. This task ensures that the back-end performs well over time. It is executed once ...
Maintenance task was executed successfully. This task ensures that the Local back-end performs well over time. It is executed ...
Make sure host exists. If host exists check whether there is a proxy or firewall client on this machine and make sure run ...
Make sure that you prevent new sessions to service "{1}" by running "Stop-CsWindowsService -Name {1} -Graceful" when preventing ...
Many security events have been identified by the proxy stack. In the past %1 seconds, %2 security events have been identified ...
Max retry limit has been reached for the item. Component: %1 Queue item ID: %2 Cause: Cannot process item. Resolution: Notify ...
Maximum difference between the OverallAvgNetworkMOS and the maximum possible OverallAvgNetworkMOS for the codec used. High ...
Maximum jitter in the arrival time between RTP packets. High jitter values can be caused by congestion or an overloaded media ...
Maximum RTP packet loss rate for video packets. High values indicate frozen or choppy video and can be caused by network ...