Lync Server 2010

  1. The {0} operation has failed with message: "{1}". See the InnerException and FailureReason properties as well as the logs ...
  2. The {0} operation has failed with message: "{1}". See the InnerException property as well as the logs for additional information. ...
  3. There are "{0}" access numbers with region \"{1}"\. Use Set-CsDialinConferencingAccessNumber to specify the Regions property. ...
  4. There are already pre-existing hosting providers or public providers, you must delete them before choosing the default route ...
  5. There are no longer any discovered partners attempting to exceed the number of internal users they are allowed to contact. ...
  6. There are no more orbits available to park the call. Cause: All available orbits are in use. Resolution: Increase orbit ranges. ...
  7. There are no more valid conversation channels to park a call. Cause: Internal system error. Resolution: Please restart the ...
  8. There is a pending reliable provisional response in progress. The session allows at most one outstanding reliable provisional ...
  9. There is a problem processing your request at this time. Try again later or contact your support team to check the server ...
  10. There is a problem when processing your request and it cannot be executed. The required file not found, contact your support ...
  11. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact ...
  12. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. ...
  13. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact ...
  14. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. ...
  15. There is an existing translation rule with higher priority that is more generic than this one. This rule will not be executed. ...
  16. There is an existing translation rule with lower priority that is more specific than this one. That rule will not be executed ...
  17. There is more than one user corresponding to the same phone number. Duplicates: %1. Cause: Administration issues. Resolution: ...
  18. There is no Conference Auto Attendant configured for this cluster. Conferences hosted on this cluster may still use Conference ...
  19. There is no disk in drive 2]. Please insert one and click Retry, or click Cancel to go back to the previously selected volume. ...
  20. There is no disk in drive 2]. Please insert one and click Retry, or click Cancel to return to the browse dialog and select ...
  21. There is no InterNetworkRegionRoute defined between regions "{0}" and "{1}". When EnableBandwidthPolicyCheck is set to true, ...
  22. There is not enough disk space on the volume '[2]' to continue the install with recovery enabled. 3 KB are required, but ...
  23. There might a replay attack on a particular user. User %1 is attempting to send data that was in request sent by user %2 ...
  24. There was a failure attempting to insert a record into one of the tables. This message will not be inserted into the CDR ...
  25. There was a failure attempting to insert a record into one of the tables. This message will not be inserted into the database ...
  26. There was a permissions problem trying to access or create the organizational unit for the new contact. Make sure you are ...
  27. There was an error creating a temporary file that is needed to complete this installation.{ Folder: 3]. System error code: ...
  28. There was an error in loading music on hold media file. Exception: %1 Cause: Corrupt media file. Resolution: Verify the original ...
  29. There was an error initializing collaboration platform. %1 Cause: Conferencing Announcement Service has not been installed ...
  30. There was an error initializing collaboration platform. %1 Cause: Conferencing Attendant has not been installed properly ...
  31. There was an error storing some of the OCS specific attributes. Make sure the SIP URI and phone number (if any) are unique ...
  32. There was an error storing some of the OCS specific attributes. Make sure you are running this application on a machine that ...
  33. There was an error trying to delete the selected contact. Make sure you are running this application on a machine that has ...
  34. There was an error trying to update the Auto-Attendant configuration with the Authorization SIP URI. This URI is used to ...
  35. There was an error while trying to create the new contact object in Active Directory. Make sure the account you are using ...
  36. There was an error while trying to load the configuration data. Make sure you are using a computer that has the OCS management ...
  37. There was no response from a gateway to an OPTIONS request sent by the Mediation Server. The Gateway peer, %1, is not responding ...
  38. There was no response from the Proxy peer to an OPTIONS request sent by the Mediation Server service. The Proxy peer, %1, ...
  39. There were one hundred TLS negotiations failures with incoming connections with the following remote peer on the Mediation ...
  40. There were one hundred TLS negotiations failures with incoming connections with the following remote peer on the Mediation ...
  41. These routes will not be used. First route name: %1 Second route name: %2 Cause: These two routes contain identical name ...
  42. This Access Edge Server has been disabled for sending archiving warning header on outgoing messages it processes. This means ...
  43. This Access Edge Server has been enabled for sending archiving warning header on outgoing messages it processes. This header ...
  44. This application makes it possible for UM features like Play-on-phone, External Subscriber Access, and Auto-Attendant to ...
  45. This counter represents the number of MSMQ messages sent to the Monitoring Server per second since the server was started. ...
  46. This counter represents the number of QoE metrics reports rejected due to an invalid encoding or server processing errors. ...
  47. This counter represents the number of QoE metrics reports rejected per second due to invalid encoding or server processing ...
  48. This counter represents the total number of failures that occurred while sending reports to the external report consumer ...
  49. This counter represents the total number of message queue messages that could not be sent to the Monitoring Server and were ...
  50. This counter represents the total number of message queue/database transactions that failed since the server was started. ...
  51. This counter represents the total number of metrics reports accepted by external report consumer since the server was started. ...
  52. This counter represents the total number of MSMQ messages discarded because they were not of the expected type or version. ...
  53. This counter represents the total number of QoE metrics reports that failed validation checks and were therefore dropped. ...
  54. This counter represents the total number of reports that were dropped due to database insertion failure. The transaction ...
  55. This counter represents the total number of unexpected server errors occurring during QoE report processing since the server ...
  56. This counter represents total number of reports dropped due to exceeding the maximum configured memory storage allowed for ...
  57. This error is probably due to running {0} in deployment without {1}/{2} server roles. In this case these errors can be ignored ...
  58. This extension cannot be added by application directly. Please use ReliableProvisionalResponsePolicy property on endpoint. ...
  59. This feature frees up 1 on your hard drive. It has 2 of 3 subfeatures selected. The subfeatures free up 4 on your hard drive. ...
  60. This feature frees up 1 on your hard drive. It has 2 of 3 subfeatures selected. The subfeatures require 4 on your hard drive. ...
  61. This feature requires 1 on your hard drive. It has 2 of 3 subfeatures selected. The subfeatures free up 4 on your hard drive. ...
  62. This feature requires 1 on your hard drive. It has 2 of 3 subfeatures selected. The subfeatures require 4 on your hard drive. ...
  63. This field is mandatory because partner discovery is disabled. To enable partner discovery, click the Access Edge Configuration ...
  64. This field is mandatory for Default Route routing method. To change to DNS SRV routing, use Lync Server Management Shell. ...
  65. This Front End pool is used as a backup registrar for the following pools, and failover is enabled. Deletion will disable ...
  66. This hosting provider is enabled for shared address space and there are "{0}" (SIP enabled) users assigned to this hosting ...
  67. This installer database contains the logic and data required to install Microsoft Lync Server 2010, Administrative Tools. ...
  68. This installer database contains the logic and data required to install Microsoft Lync Server 2010, Bandwidth Policy Service. ...
  69. This installer database contains the logic and data required to install Microsoft Lync Server 2010, Conferencing Announcement ...
  70. This installer database contains the logic and data required to install Microsoft Lync Server 2010, Conferencing Attendant. ...
  71. This installer database contains the logic and data required to install Microsoft Lync Server 2010, Core Management Server. ...
  72. This installer database contains the logic and data required to install Microsoft Lync Server 2010, Web Components Server. ...
  73. This installer database contains the logic and data required to install Microsoft Lync Server 2010, Web Conferencing Server. ...
  74. This installer database contains the logic and data required to install Microsoft Lync Server 2010, WMI Backwards Compatibility. ...
  75. This instance of Match Making is now passive. Match Making could not activate in a timely manner. The FQDN of the new active ...