Lync Server 2010

  1. The role-based access control (RBAC) role '{0}' cannot contain '{1}', because '{1}' is not a Lync Server cmdlet. Only Lync ...
  2. The roles in the topology and the installed roles do not match. Run Bootstrapper to update the roles installed on this computer. ...
  3. The Routing Data Sync Agent has completed a sync cycle with: %1], Succeeded: %2], Duration: %3], ModifiedBatchCount: %4], ...
  4. The script used when user has not published routing data was not found in the configuration or failed to load. Name='%1' ...
  5. The server %1 is configured as the default federation route but it is not a known configured server. Ignore this warning ...
  6. The server %1 is configured as the next hop for the static route %2 but that server has not been configured. Check the 'Topology' ...
  7. The server '%1:%2' is the new next hop on the Access Edge Server. Number of outgoing connections: %3. Maximum incoming connections ...
  8. The server certificate store for holding partner certificates is full. The number of certificates written to the store (%1) ...
  9. The server configuration validation mechanism detected some potential problems. The server might not behave as expected. ...
  10. The server configuration validation mechanism detected some serious problems. %1 errors and %2 warnings were detected. ERRORS: ...
  11. The server failed to import a shared session key due to invalid signature in a referrer identity digest. In the past %1 minutes, ...
  12. The server has returned RPC Access Denied responses. %1 RPC Access Denied responses were sent due to connecting clients not ...
  13. The server must be restarted before installation can continue. To continue the installation after the server has restarted, ...
  14. The Server received conferencing requests destined for another Pool. Target Pool: %1. Cause: Incorrect routing configuration. ...
  15. The server was configured to use a Clearinghouse %1]. Discovery of federation partners is not supported when using a Clearinghouse. ...
  16. The service cannot start because the global configuration settings are missing. Cause: The Lync Server 2010, Response Group ...
  17. The service cannot start because the pool configuration is not valid. Cause: The Lync Server 2010, Response Group Service ...
  18. The service could not be started - error accessing perfcounters. AV MCU does not have the right permissions. Make sure to ...
  19. The service could not start. Exception: %1 Cause: Internal error. Resolution: Try to restart the service. Check NT event ...
  20. The service definition for this process is removed from topology configuration. The service will be running using the old ...
  21. The service established connection to the back end SQL Server. Database connection string : %1 Cause: N/A Resolution: N/A ...
  22. The service failed to connect to the SQL backend. The service failed to connect to the SQL backend because of the following ...
  23. The service failed to execute a stored procedure due to a connection failure. Insertion of this message will be retried. ...
  24. The service failed to execute a stored procedure. This message will not be inserted into the database but will be logged ...
  25. The service failed to get conference lock. This message will be retried. Stored procedure Name: %1 SQL Native Error: %2 Resolution: ...
  26. The service failed to get dialog lock. This message will be retried. Stored procedure Name: %1 SQL Native Error: %2 Resolution: ...
  27. The service failed to get session lock. This message will be retried. Stored procedure Name: %1 SQL Native Error: %2 Resolution: ...
  28. The service failed to log a message because it contains a bad time stamp. Stored procedure Name: %1 Cause: A message in the ...
  29. The service failed to log a message because it contains bad time stamp. Stored procedure Name: %1 Cause: This can happen ...
  30. The service failed to log a message because it received a string data which is bigger than what the corresponding column ...
  31. The service failed to open an MSMQ transaction. Error Code: %1!_HRX! Cause: The MSMQ service may be down. Resolution: Check ...
  32. The service failed to open an MSMQ transaction. Error Code: %1!_HRX! Cause: This could happen if the MSMQ service or domain ...
  33. The service failed to open log file. The service will stop. Error Code: %1!_HRX! Cause: This may be caused if there is a ...
  34. The service failed to purge records from the database or files on data compliance folder SQL Native Error: %1 Error Code: ...
  35. The service failed to read a message from MSMQ. Error Code: %1!_HRX! Cause: The MSMQ service may be down. Resolution: Check ...
  36. The service failed to read a message from MSMQ. Error Code: %1!_HRX! Cause: This could happen if the MSMQ service is down. ...
  37. The service failed to register its main communication end point. Exception: %1 Cause: Networking problems with the Front ...
  38. The service failed to register its media communication end point. Exception: %1 Cause: Networking problems with the Front ...
  39. The service failed to start. Error Code: %1!_HRX! Cause: Application Error Resolution: Check the previous event log entries ...
  40. The service failed to submit a stored procedure for execution. Stored procedure Name: %1 Error Code: %2!_HRX! Cause: There ...
  41. The service failed to submit a stored procedure for execution. Stored procedure Name: %1 Error Code: %2!_HRX! Cause: This ...
  42. The service failed to validate a buffer it read from MSMQ. Length of some of the components of this message is not of expected ...
  43. The service failed to validate a buffer it read from MSMQ. The failed CDR message will be dropped. Stored procedure Name: ...
  44. The service failed to validate a buffer it read from MSMQ. The total message size is not equal to the sum of the different ...
  45. The service failed to validate a buffer it read from MSMQ. This message will be dropped. Stored procedure Name: %1 Error ...
  46. The service failed to validate a buffer it read from MSMQ. Total length of this message exceeds its expected size. This message ...
  47. The service failed to write an error to the error log file. Cause: The log file may not have enough space left for writing, ...
  48. The service failed to write an error to the error log file. The service will stop. Error Code: %1!_HRX! Cause: The log file ...
  49. The service failed to write an error to the log file. Cause: This may be caused if the Log file does not have sufficient ...
  50. The service failed to write an error to the log file. The service will stop. Error Code: %1!_HRX! Cause: This may be caused ...
  51. The service found a non empty log file while starting up. It will continue to append to this file should any new error occur. ...
  52. The service is shutting down due to an internal error. Error Code: %1!_HRX! (%2!_HRM!) Cause: Check the previous entries ...
  53. The service must be restarted in order to change the TLS connection limits for the Access Edge Server. Cause: Changing the ...
  54. The service pool is at capacity. Pool: '%1', Potential License Users: '%2' Cause: The service pool is at capacity. Resolution: ...
  55. The service principal name {0} was not found on the Kerberos account {1}. Kerberos authentication may not work correctly. ...
  56. The service read an unknown message type from MSMQ . This message will be dropped. Message type: %1 Cause: This may be caused ...
  57. The service started. Listen address for client connections: %1, Listen address for Web Conferencing Server connections: %2 ...
  58. The service successfully purged diagnostics records from the database Number of Progress Reports purged:%1 Number of Error ...
  59. The service successfully purged records from the database Number of File transfer or Remote assistance records purged:%1 ...
  60. The service successfully purged records from the database Number of Messages purged:%1 Number of Sessions purged:%2 Number ...
  61. The service with the cluster fully qualified domain name (FQDN) "{0}", cluster ID "{1}", cluster site ID "{2}", service ID ...
  62. The set of Conferencing Announcement Service counters for purposes like performance analysis, modeling, capacity planning. ...
  63. The setting to allow the routing of all domains to the internal network cannot be enabled when the server is configured to ...
  64. The Setup Wizard allows you to change the way ProductName features are installed on your computer or to remove it from your ...
  65. The Setup Wizard will complete the installation of ProductName on your computer. Click Install to continue or Cancel to exit ...
  66. The SIP listening address for ACP MCU service is not supplied. Cause: The listening address specified for incoming SIP connections ...
  67. The SIP listening address is not valid. Cause: The listening address specified for incoming SIP connections is not valid. ...
  68. The SIP listening port has changed. A restart is required for the change to take effect. New SIP listening port: %1 Cause: ...
  69. The SIP listening port is not valid. Cause: The listening port specified for incoming SIP connections is not valid. Resolution: ...
  70. The SIP listening port is not valid. Cause: The listening port specified for incoming SIP connections is not valid. Resolution: ...
  71. The SipEnabled value that was specified for a user is invalid. This typically means that the given SipEnabled couldn't be ...
  72. The site with ID "{0}" does not have a NetworkRegionID configured. When EnableBandwidthPolicyCheck is set to true, every ...
  73. The source installation package for the product 2 is out of sync with the client package. Try the installation again using ...
  74. The specified language is not supported to play text-to-speech messages. For the full list of supported languages, see Help. ...
  75. The specified time range and interval exceeded the maximum number of samples ({0}). The time range used for the query was ...