Lync Server 2010

  1. The Group Chat Server is not trusted by the Lync Server. Reason string: %1 Error code: %2 Cause: This problem is usually ...
  2. The hash algorithm specified in the registry cannot be used. The "%1" registry key is not supported by this operating system ...
  3. The hash algorithm specified in the registry cannot be used. The hash algorithm "%1" set in the "%2" registry key is not ...
  4. The header parsing failed. This can be caused by a non ASCII, CR, or LF character in the name or value or if format does ...
  5. The heartbeat stored procedure failed. It will be retried, but if this error continues to occur, the Lync Server service ...
  6. The high watermark for server throttling. If throttling is not engaged and the number of messages that are held by the server ...
  7. The highlighted volumes do not have enough disk space available for the currently selected features. You can remove some ...
  8. The highlighted volumes do not have enough disk space available for the currently selected features. You can remove some ...
  9. The idle timeout cannot be set for outgoing connections when not using server connection manager. Use the DefaultOutgoingConnectionTimeout ...
  10. The IM Conferencing Server successfully sent health notifications to the MCU factory at %1. Any previous errors have been ...
  11. The IMMCU was not able to stay connected to the Front End over the C3P channel (HTTPS Connection). The IM Conferencing Server ...
  12. The IncomingFederation Application is waiting for the Lync Server to start. Cause: The IncomingFederation Application is ...
  13. The input passed to parameter "{0}" was incomplete. When providing input by using a pipeline, ensure that all data is passed ...
  14. The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. ...
  15. The installer has insufficient privileges to access this directory: 2]. The installation cannot continue. Log on as administrator ...
  16. The installer must restart your system before configuration of 2 can continue. Click Yes to restart now or No if you plan ...
  17. The internal pool, Mediation Server, and PSTN Gateway configuration can be automatically discovered; you must, however, manually ...
  18. The Kerberos configuration on {0} is invalid. The expected assigned account is {1}. Ensure that the account has not expired, ...
  19. The last attempt to move the Central Management Server from "{0}" to "{1}" either failed or is in progress. Ensure that there ...
  20. The last attempt to move the Central Management Server from "{0}" to "{1}" either failed or is in progress. Ensure that there ...
  21. The last attempt to move the Central Management Server from "{0}" to "{1}" either failed or is in progress. Ensure that there ...
  22. The last time taken (in milliseconds) by a failed endpoint resolution in the UserServices RPC Component of the Lync Server. ...
  23. The last time taken (in milliseconds) by a successful endpoint resolution in the UserServices RPC Component of the Lync Server. ...
  24. The list of services and pools to which connection attempts have failed has changed. A new event 14584 will be reported shortly. ...
  25. The listening URL for focus adapter is not set. Cause: Listening URL for focus adapter is not set Resolution: Set a valid ...
  26. The location "{0}" is ambiguous. Because this operation is applicable to multiple services in this pool, you must specify ...
  27. The location "{0}" is ambiguous. You must specify both a role name and a fully qualified domain name (FQDN) separated by ...
  28. The location policy tag ID "{0}" referenced by network site "{1}" cannot be resolved to a tag name. The policy does not exist. ...
  29. The location policy tag name "{0}" referenced by network site "{1}" cannot be resolved to a tag ID. The policy does not exist. ...
  30. The location specified does not appear to be correct. Please locate the directory on the Lync Server installation media where ...
  31. The log file prefix is used when formatting events to log files. The real time prefix is used when formatting events to the ...
  32. The log path specified already contains a log file for the Lync Server user database. Please specify a different location ...
  33. The low watermark for server throttling. If throttling is engaged and the number of messages that are held by the server ...
  34. The LS topology is not configured to run the LS Bandwidth Policy Service (Core). %1 Cause: LS Bandwidth Policy Service (Core) ...
  35. The Match Making client was not able to connect to the active Match Making Service. The following exception occurred when ...
  36. The Match Making client was successfully connected to the active Match Making service. The Match Making client has returned ...
  37. The Match Making service could not transfer the call because of an error in the queue configuration. Call ID %1 received ...
  38. The Match Making service failed to load the new configuration. Action: %1 Item: %2 Identifier: %3 Cause: The Lync Server ...
  39. The Match Making Service was not able to start. An exception occurred when binding to the WCF remoting port. This can occur ...
  40. The Match Making Service was not able to start. An exception occurred when binding to the WCF remoting port. This can occur ...
  41. The Match Making stub was not able to connect to Match Making Service. An exception occurred when connecting to the Match ...
  42. The MCU Factory listener URL is null. Cause: Configuration or setup error. Resolution: Configure a valid listener URL for ...
  43. The Mcu Factory returned failure for a request sent to it. Conferencing requests for this Mcu type will be retried but if ...
  44. The MCU factory successfully connected to the %1 database located on the %2 sever. Any previous database connectivity errors ...
  45. The mcu information is not available. The conference may not support this MCU type or the conference session may not be connected ...
  46. The MCUFactory failed to find an Application Sharing Conferencing Server to service an application sharing modality request. ...
  47. The MCUFactory failed to find an Audio Conferencing Provider Server to service a phone conferencing modality request. Cause: ...
  48. The MCUFactory failed to find an Audio-Video Conferencing Server to service an audio video modality request. Cause: All Audio ...
  49. The MCUFactory failed to find an IM Conferencing Server to service an chat modality request. Cause: All IM Conferencing Servers ...
  50. The MCUFactory failed to find an Web Conferencing Compatibility Server to service an web conferencing compatibility modality ...
  51. The MCUFactory failed to find an Web Conferencing Server to service an web conferencing modality request. Cause: All Web ...
  52. The MCUFactory succeeded in finding an available Application Sharing Conferencing Server. Any previous errors have been resolved. ...
  53. The MCUFactory succeeded in finding an available Audio Conferencing Provider Server. Any previous errors have been resolved. ...
  54. The MCUFactory succeeded in finding an available Audio-Video Conferencing Server. Any previous errors have been resolved. ...
  55. The MCUFactory succeeded in finding an available Web Conferencing Compatibility Server. Any previous errors have been resolved. ...
  56. The MCUFactory succeeded to process a health notification from the following MCU: %1. Any previous errors have been resolved. ...
  57. The Media Listening Port Range configuration value is invalid. Cause: Possible misconfiguration issues. Resolution: Please ...
  58. The Mediation Server pool requires one or more PSTN media gateways. The default listening port for the Mediation pool is ...
  59. The Mediation Server service definition is removed from topology configuration. The service will be running using the old ...
  60. The Mediation Server service failed a call because of too little bandwidth available on the gateway leg of a call. The Mediation ...
  61. The Mediation Server service failed a call because of too little bandwidth available on the proxy leg of a call. The Mediation ...
  62. The Mediation Server service gateway peer call completion failure has been resolved. Most recent PSTN Gateway Service Cluster ...
  63. The Mediation Server service gateway peer connectivity failure has been resolved. Most recent PSTN Gateway Service Cluster ...
  64. The Mediation Server service has encountered a major call completion problem with the proxy peer. Proxy Peer FQDN: %1 Cause: ...
  65. The Mediation Server service has encountered a major call completion problem with these gateway peer(s). Affected PSTN Gateway ...
  66. The Mediation Server service has encountered a major connectivity problem with the proxy peer. Proxy Peer FQDN: %1 Cause: ...
  67. The Mediation Server service has encountered a major connectivity problem with these gateway peer(s). Affected PSTN Gateway ...
  68. The Mediation Server service has encountered a major internal problem that may be causing it to fail calls. Cause: Check ...
  69. The Mediation Server service has encountered a major MRAS connection problem with the proxy peer. Cause: The MEDIATIONSE ...
  70. The Mediation Server service has encountered a major problem with its configurations. Cause: Check the following MOM alerts ...
  71. The Mediation Server service has received a call that does not support comfort noise. This event is throttled after 5 calls ...
  72. The Mediation Server service startup is pending as configuration database is not yet available. Cause: Possible local configuration ...
  73. The message id supplied cannot be used for the operation invoked. Ensure that it corresponds to an outstanding message delivered ...
  74. The message queue cannot be opened for reading. The Quality of Experience (QoE) monitoring agent cannot collect any data. ...
  75. The message queue cannot be opened for reading. The Quality of Experience (QoE) Monitoring service continues to run, but ...