Lync Server 2013

  1. Lync Server startup is pending as configuration database is not yet available. Cause: Possible local configuration database ...
  2. Lync Server startup is pending. Some configured critical applications have not yet registered. Applications: %1. Resolution: ...
  3. Lync Server the call detail recording (CDR) agent has stopped sending messages to Message Queuing because Message Queuing ...
  4. Lync Server The call detail recording (CDR) agent is unable to send a message to Message Queuing queue. Queue: %1 Acknowledgement ...
  5. Lync Server Web Conferencing Server could not be started Message: %1 %2 Cause: Look in previous event logs for more information ...
  6. Lync Server Web Conferencing Server failed to load the external proxies list. Failed to connect external users because the ...
  7. Lync Server Web Conferencing Server Unhandled exception Message: %1 Stack: %2 Cause: Application error. Please look through ...
  8. Lync Web App failed to listen for incoming MTLS connections on assigned port. Configured port is %1. Cause: Failed to listen ...
  9. Machine FQDN %1 (IP address: %2, TCP listening port: %3, Type: %4) in pool %5 has been added to the topology, or the EnableBandwidthPolicyCheck ...
  10. Machine FQDN %1 (IP address: %2, TCP listening port: %3, Type: %4) in pool %5 has been removed from the topology, or the ...
  11. Machine {0} from the current topology has been removed from the topology you are now publishing. This machine was not found ...
  12. Machine {0} from the topology you are publishing was not found in Active Directory and will result in errors during Enable-CsTopology ...
  13. Maintenance task was executed successfully. This task ensures that the back-end performs well over time. It is executed once ...
  14. Maintenance task was executed successfully. This task ensures that the Local back-end performs well over time. It is executed ...
  15. Make sure host exists. If host exists check whether there is a proxy or firewall client on this machine and make sure run ...
  16. Make sure that you prevent new sessions to service "{1}" by running "Stop-CsWindowsService -Name {1} -Graceful" when preventing ...
  17. Many security events have been identified by the proxy stack. In the past %1 seconds, %2 security events have been identified ...
  18. Max retry limit has been reached for the item. Component: %1 Queue item ID: %2 Cause: Cannot process item. Resolution: Notify ...
  19. Maximum difference between the OverallAvgNetworkMOS and the maximum possible OverallAvgNetworkMOS for the codec used. High ...
  20. Maximum jitter in the arrival time between RTP packets. High jitter values can be caused by congestion or an overloaded media ...
  21. Maximum RTP packet loss rate for video packets. High values indicate frozen or choppy video and can be caused by network ...
  22. Maximum RTP packet loss rate. High loss values can be caused by congestion, exceeding available bandwidth, wireless congestion/interference, ...
  23. Maximum RTP round-trip time between the endpoints. High round-trip time values can be caused by international call routing, ...
  24. Maximum video bit rate. Low values indicate choppy or jerky video and can be caused by high network packet loss, low lighting, ...
  25. may only begin with a letter, underscore, or colon and can only contain letters, digits, underscores, colons, hyphens, and ...
  26. McuFactory could not be initialized. Lync Server MCU Factory could not be initialized. Exception: %1. Stack: %2. Cause: Application ...
  27. McuFactory could not find the pool associated with one of the conference directories. Failed to read pool FQDN associated ...
  28. McuFactory could not populate Conference Directories. MCU Factory could not populate Conference Directories. Exception: %1. ...
  29. Mcx Server can't connect to the configured Push Notification Proxy: %1 Cause: The Push Notification Proxy is currently unreachable. ...
  30. Mcx Server did not find its SIP listening port from topology document. The startup failed. %1 Cause: The SIP listening port ...
  31. Mcx Server encountered an unexpected exception during configuration change notification processing. Exception: %1 Cause: ...
  32. Mcx Server encountered an unexpected exception during initialization. Exception: %1 Cause: An unexpected error has occurred ...
  33. Mcx Server encountered an unexpected exception during web service settings change notification processing. Exception: %1 ...
  34. Mcx Server encountered an unhandled exception. Exception: %1 Cause: An unhandled exception happened. Application error. Please ...
  35. Mcx Server failed to authenticate with the Push Notification Proxy with the configured certificates %1 Cause: The Push Notification ...
  36. Mcx Server failed to find a trusted application endpoint. Cause: Global activation was not run after installing Push Notification ...
  37. Mean opinion score (MOS) of the overall connection based on the speech, noise, echo and delay for the call. Use the related ...
  38. Media Access Control (MAC) address format is invalid. Specify a valid MAC address (for example, 01:23:45:67:89:01) and then ...
  39. Media bypass will be enabled if you use one of the following voice infrastructures, and the media bypass rate will be set ...
  40. Media file could not be played since the file is missing or is not in the correct format. Calls may be disconnected. Media ...
  41. Media file could not be played since the file is missing or is not in the correct format. Media file: %1 Cause: Media file ...
  42. Media file could not be played since the file is missing or is not in the correct format. Media file: %1 culture: %2 Cause: ...
  43. Media file could not be played since the file is missing or is not in the correct format. Media file: %1 culture: %2 Cause: ...
  44. Mediation Server cannot reach the Trunk. Additional failures will not be logged. Cannot reach Trunk: %1 Cause: Trunk IP address ...
  45. Mediation server caught an exception that it never expected. The exception may have side-effects where Mediation server cannot ...
  46. Mediation Server could not apply settings changes. The settings were ignored. Setting Name: %1 Property Description: %2 Old ...
  47. Mediation Server does not support changing these settings dynamically. The settings were ignored. Setting Name: %1 Property ...
  48. Mediation Server encountered a problem while trying to apply setting changes. Setting Name: %1 Property Description: %2 Old ...
  49. Mediation Server encountered an internal error but ignored the failure. Server will keep running. Exception: %1 Cause: Internal ...
  50. Mediation Server encountered an invalid setting that has been ignored. Setting: %1 Reason: %2 Cause: Settings configured ...
  51. Mediation Server failed to start because it was unable to contact the Management Store. Exception: %1 Cause: The Management ...
  52. Mediation server hit an internal exception from the signaling layer. The current call may be dropped. Mediation server will ...
  53. Mediation Server service could not be started. Exception: %1 Cause: Internal error or a previous failure. Resolution: Examine ...
  54. Mediation Server was able to contact the A/V Authentication Service. However, there were no valid relay candidates returned ...
  55. Meeting participants can join the audio portion of a meeting from a traditional telephone or mobile phone if dial-in conferencing ...
  56. Members have read access to Lync Server 2013 configuration and are placed in the Local Administrators group of survivable ...
  57. Members of this group can enable and disable users for Lync Server 2013, move users, and assign existing policies to users. ...
  58. Members of this group can view the deployment, including user properties and policies, and can execute specific troubleshooting ...
  59. Members of this group can view the Lync Server 2013 deployment, including server information, in order to monitor deployment ...
  60. Members of this group have the lowest level of rights for E911 management. They can create E911 locations and network identifiers, ...
  61. Members of this group receive the same rights as RTCUniversalUserReadOnlyGroup to read Lync Server attributes on users with ...
  62. Microsoft Lync Server 2013 Archiving is a service to archive instant messaging conversations as well as data conferencing. ...
  63. Microsoft Lync Server 2013 mobility helps to support Lync Server functionality on mobile devices. You can perform activities ...
  64. Microsoft Lync Server 2013 Monitoring is a service that captures call detail records relating to unified communications sessions, ...
  65. Microsoft Lync Server 2013 provides disaster recovery service which ensures the continued operation of those systems, or ...
  66. Microsoft Lync Server 2013 support environments of IPv4, IPv6, and both IPv4 and IPv6. You can choose one of the following ...
  67. Microsoft Lync Server 2013, Backup Service central management backup module detected a change in its backend. The change ...
  68. Microsoft Lync Server 2013, Backup Service central management backup module encountered an exception that was handled gracefully ...
  69. Microsoft Lync Server 2013, Backup Service central management backup module encountered an exception that was handled gracefully ...
  70. Microsoft Lync Server 2013, Backup Service central management backup module failed to complete export operation. Configurations: ...
  71. Microsoft Lync Server 2013, Backup Service central management backup module failed to complete import operation. Configurations: ...
  72. Microsoft Lync Server 2013, Backup Service central management backup module failed to register with back-end database. The ...
  73. Microsoft Lync Server 2013, Backup Service central management backup module failed to register with the back-end, because ...
  74. Microsoft Lync Server 2013, Backup Service central management backup module failed to set the backend state to backup. Backup ...
  75. Microsoft Lync Server 2013, Backup Service central management backup module has backup data that never gets imported by backup ...