UI Translation

Lync Server 2013

  1. The following machines from the current topology has been removed from the topology you are now publishing. These machine ...
  2. The following machines from the topology you are publishing were not found in Active Directory and will result in errors ...
  3. The following recommended deployment steps are based on your organization's topology. For details about a deployment step, ...
  4. The following tables show metrics for caller location and callee location. Caller location are listed in rows, callee locations ...
  5. The following tables show metrics for caller location and callee location. Caller location are listed in rows, callee locations ...
  6. The following trunks are associated with this Mediation Server. Click Make Default to mark a trunk as default. A default ...
  7. The format you provided, "{0}", is unknown. The correct format is "X509: CN=Issuer CN=Subject". Note that the issuer part ...
  8. The forwarding URI '%1' for contact %2 is not a valid SIP URI. Cause: The forwarding URI value stored in the 'otherIpPhone' ...
  9. The Front End cannot be contacted. Mediation server will keep trying; however additional failures will not be logged. The ...
  10. The Front End cannot be reached by the Mediation Server service. Additional failures will not be logged. The Front End, %1, ...
  11. The front end no longer owns the task and is therefore shutting down. Cause: SQL Connectivity issues. Resolution: Verify ...
  12. The global container was not found. Please make sure that all the prep steps are performed and the account has read rights ...
  13. The Global Enhanced Emergency Services Disclaimer has been deprecated in Microsoft Lync Server 2013. Use the property in ...
  14. The hash algorithm specified in the registry cannot be used. The "%1" registry key is not supported by this operating system ...
  15. The hash algorithm specified in the registry cannot be used. The hash algorithm "%1" set in the "%2" registry key is not ...
  16. 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 ...
  17. The heartbeat stored procedure failed. It will be retried, but if this error continues to occur, the Lync Server service ...
  18. The high watermark for server throttling. If throttling is not engaged and the number of messages that are held by the server ...
  19. The highlighted volumes do not have enough disk space available for the currently selected features. You can remove some ...
  20. The highlighted volumes do not have enough disk space available for the currently selected features. You can remove some ...
  21. The idle timeout cannot be set for outgoing connections when not using server connection manager. Use the DefaultOutgoingConnectionTimeout ...
  22. The IM Conferencing Server successfully sent health notifications to the MCU factory at %1. Any previous errors have been ...
  23. The IMMCU was not able to stay connected to the Front End over the C3P channel (HTTPS Connection). The IM Conferencing Server ...
  24. The incoming URL mapped to domains from multiple tenants. This may indicate a possible configuration problem. Incoming URL. ...
  25. The IncomingFederation Application is waiting for the Lync Server to start. Cause: The IncomingFederation Application is ...
  26. The input passed to parameter "{0}" was incomplete. When providing input by using a pipeline, ensure that all data is passed ...
  27. The input passed to parameter "{0}" was incomplete. When providing input by using a pipeline, ensure that all data is passed ...
  28. The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. ...
  29. The installer has insufficient privileges to access this directory: 2]. The installation cannot continue. Log on as administrator ...
  30. The installer must restart your system before configuration of 2 can continue. Click Yes to restart now or No if you plan ...
  31. The internal pool, Mediation Server, and PSTN gateway configuration can be automatically discovered. You must manually specify ...
  32. The IP Addresses assigned to the external interface in the perimeter network and behind a hardware load balancer. The server ...
  33. The IP addresses may not be in DNS but are referenced by the internal Access Edge, Web Conferencing and A/V Conferencing ...
  34. The Kerberos configuration on {0} is invalid. The expected assigned account is {1}. Ensure that the account has not expired, ...
  35. The last attempt to failover the Central Management Server from "{0}" to "{1}" either failed or is in progress. Ensure that ...
  36. The last attempt to move the Central Management Server from "{0}" to "{1}" either failed or is in progress. Ensure that there ...
  37. The last attempt to move the Central Management Server from "{0}" to "{1}" either failed or is in progress. Ensure that there ...
  38. The last attempt to move the Central Management Server from "{0}" to "{1}" either failed or is in progress. Ensure that there ...
  39. The last time taken (in milliseconds) by a failed endpoint resolution in the UserServices RPC Component of the Lync Server. ...
  40. The last time taken (in milliseconds) by a successful endpoint resolution in the UserServices RPC Component of the Lync Server. ...
  41. The list of services and pools to which connection attempts have failed has changed. A new event 14584 will be reported shortly. ...
  42. The listening addresses for the Persistent Chat Server have changed. Listening addresses have changed to: IPAddress - %1, ...
  43. The listening URL for focus adapter is not set. Cause: Listening URL for focus adapter is not set Resolution: Set a valid ...
  44. The location "{0}" is ambiguous. Because of this, you need to specify the cluster FQDN instead of the Trunk friendly name. ...
  45. The location "{0}" is ambiguous. Because this operation is applicable to multiple services in this pool, you must specify ...
  46. The location "{0}" is ambiguous. You must specify both a role name and a fully qualified domain name (FQDN) separated by ...
  47. The location policy tag ID "{0}" referenced by network site "{1}" cannot be resolved to a tag name. The policy does not exist. ...
  48. The location policy tag name "{0}" referenced by network site "{1}" cannot be resolved to a tag ID. The policy does not exist. ...
  49. The location specified does not appear to be correct. Please locate the directory on the Lync Server installation media where ...
  50. The log path specified already contains a log file for the Lync Server user database. Please specify a different location ...
  51. The low watermark for server throttling. If throttling is engaged and the number of messages that are held by the server ...
  52. The LS topology is not configured to run the LS Bandwidth Policy Service (Core). Cannot locate this machine in the topology. ...
  53. The LS topology is not configured to run the LS Bandwidth Policy Service (Core). No certificate is configured for PDP. Cause: ...
  54. The LS topology is not configured to run the LS Bandwidth Policy Service (Core). No registrar service is found for site: ...
  55. The LS topology is not configured to run the LS Bandwidth Policy Service (Core). No service is defined for this computer. ...
  56. The LS topology is not configured to run the LS Bandwidth Policy Service (Core). The PDP ports are not defined. Cause: LS ...
  57. The LS topology is not configured to run the LS Bandwidth Policy Service (Core). This computer is not associated with any ...
  58. The LS topology is not configured to run the LS Bandwidth Policy Service (Core). This machine does not belong to an OCS site. ...
  59. The LS topology is not configured to run the LS Bandwidth Policy Service (Core). Unexpected change in Site Id, Cluster Id, ...
  60. The Lync Server Migration service throttled incoming connections for specific tenant. In the past %1 minutes, the server ...
  61. The Lync Server Migration service throttled incoming connections. In the past %1 minutes, the server rejected %2 user migration ...
  62. The machine can not release its task due to too many errors in some functions, as it is already over the max times. Task ...
  63. The machine is ready to release its task due to too many errors in some functions. Task switch times: '%1', Priority: '%2', ...
  64. The mapping between the workflow "{0}" and the holiday set "{1}" was successfully stored in the Application Database "{2}". ...
  65. The Match Making client was not able to connect to the active Match Making Service. The following exception occurred when ...
  66. The Match Making client was successfully connected to the active Match Making service. The Match Making client has returned ...
  67. The Match Making service could not transfer the call because of an error in the queue configuration. Call ID %1 received ...
  68. The Match Making service failed to load the new configuration. Action: %1 Item: %2 Identifier: %3 Cause: The Lync Server ...
  69. The Match Making Service was not able to start. An exception occurred when binding to the WCF remoting port. This can occur ...
  70. The Match Making Service was not able to start. An exception occurred when binding to the WCF remoting port. This can occur ...
  71. The Match Making stub was not able to connect to Match Making Service. An exception occurred when connecting to the Match ...
  72. The MCU Factory listener URL is null. Cause: Configuration or setup error. Resolution: Configure a valid listener URL for ...
  73. The Mcu Factory returned failure for a request sent to it. Conferencing requests for this Mcu type will be retried but if ...
  74. The MCU factory successfully connected to the %1 database located on the %2 sever. Any previous database connectivity errors ...
  75. The mcu information is not available. The conference may not support this MCU type or the conference session may not be connected ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)