Lync Server 2013

  1. The Persistent Chat Compliance adapter has unexpectedly stopped. Persistent Chat Compliance adapter is stopping due to error ...
  2. The Persistent Chat compliance database connection was lost. Microsoft Lync Server 2013, Persistent Chat Compliance lost ...
  3. The Persistent Chat Configuration cannot be null. Please set the configuration for the in-band settings on local endpoint ...
  4. The Persistent Chat contact for pool={0} and address={1} is either missing, disabled, or there is more than one contact with ...
  5. The Persistent Chat database connection was lost. Microsoft Lync Server 2013, Persistent Chat Compliance lost connection ...
  6. The Persistent Chat database connection was lost. The Lync Server 2013, Persistent Chat lost connection to the database using ...
  7. The Persistent Chat server can not establish or maintain MTLS connection to the Lync Server. Reason string: %1 Error code: ...
  8. The Persistent Chat Server is not able to connect to the Lync Server. Error code: %1 Cause: This problem is usually caused ...
  9. The Persistent Chat Server is not trusted by the Lync Server. Reason string: %1 Error code: %2 Cause: This problem is usually ...
  10. The PIC service is unavailable right now. Cause: The connection to PIC service is down. Resolution: 1. Check network connectivity ...
  11. The PIN has been set successfully. Communicate the new number to the user before closing this dialog box. If you do not, ...
  12. The Planning Tool will then generate an Administrator report for each site that will specify DNS settings, firewall settings, ...
  13. The Planning Tool Wizard finished successfully. You can now view your topology. At this time, you need to enter server configuration ...
  14. The policy "{0}" is currently assigned to one or more users. Assign a different policy to the users before removing this ...
  15. The pool DN that was specified for a user is invalid. This typically means that the given pool DN attribute could not be ...
  16. The pool FQDN (%1) specified by msRTCSIP-PrimaryUserAddress is different than the presence pool FQDN (%2) specified by Cluster ...
  17. The pool FQDN does not match any pool with Persistent Chat installed. If the Category or Chat Room you are trying to access ...
  18. The pool has been deleted, and the following file stores are redundant. Do you want to delete these file stores? Affected ...
  19. The pool is already attached to a database, but the data file location that you specified does not match that of the existing ...
  20. The pool is already attached to a database, but the transaction log location that you specified does not match that of the ...
  21. The pool this machine is part of is not in the list of internal servers. The server cannot start. Cause: This is a configuration ...
  22. The presence policy maintenance stored procedure failed. It will be retried, but if this error continues to occur, the Lync ...
  23. The presentation didn't start because the encryption policy settings don't match. Please contact your support team with this ...
  24. The presentation didn't start because there was a problem connecting to the server. If this continues, please contact your ...
  25. The previous update attempt was unsuccessful. Please try again. If the problem continues, please contact your support team. ...
  26. The primary and secondary domain controller cannot replicate simultaneously. Primary domain controller: '%1', Secondary domain ...
  27. The primary and secondary domain controller configuration in the Provisioning service is invalid. Cannot create valid checkpoint. ...
  28. The Primary domain controller and secondary domain controller are not in the same site. Primary Domain Controller: '%1', ...
  29. The private CDR message queue required by Monitoring Server is not configured correctly. Remove the message queue and try ...
  30. The private contact object is being removed. Conferencing Attendant may not function correctly. Cause: Administration issues. ...
  31. The private message queue required by Archiving Server is not configured correctly. Remove the message queue and try again. ...
  32. The private QoE message queue required by Monitoring Server is not configured correctly. Remove the message queue and try ...
  33. The process %1 received a valid certificate from the server. Any previous errors have been resolved. Certificate subject ...
  34. The process %1 received an invalid client certificate. Certificate SN: %2 Certificate issuer name: %3. Certificate error: ...
  35. The process was not able to stay connected to the Front End service. The Web Conferencing Compatibility Server failed to ...
  36. The properties for this item are not available for editing because the item represents a pool from a previous version of ...
  37. The public key for certificate "{0}" is using the "{1}" algorithm. Lync Server has only been validated to support public ...
  38. The Quality of Experience (QoE) External Consumer HTTP Report Provider is not using a client certificate for connections ...
  39. The Quality-Metric Agent cannot be contacted. Mediation server will keep trying; however additional failures will not be ...
  40. The Quality-Metric Agent cannot be contacted. The Quality metric reports are not sent. Exception: %1 QoE Agent: %2 GRUU: ...
  41. The Quality-Metric Agent cannot be contacted. The Quality metric reports are not sent. QoE Agent: %1 GRUU: %2 Cause: Either ...
  42. The Quality-Metric Agent returned invalid response. The Quality metric reports are not sent. Response Code: %1 Response Text: ...
  43. The Quality-Metric server cannot be contacted. Mediation server will keep trying; however additional failures will not be ...
  44. The Quality-Metric server cannot be contacted. The Quality metric reports are not sent to the server. QoE Agent: %1 QoE GRUU: ...
  45. The Quality-Metric server cannot be contacted. The Quality metric reports are not sent to the server. QoE Agent: %1 QoE GRUU: ...
  46. The Quality-Metric server returned invalid response. The Quality metric reports are not sent to the server. Response Code: ...
  47. The queue "{0}" ("{1}") is currently being used by active workflows or other queues. After deletion, these workflows will ...
  48. The queue has no agents serving it. Queue Name: %1 Queue Id: %2 Cause: Misconfigured queue. Resolution: Make sure there is ...
  49. The rate per second of aggregation requests that have experienced failures. The failures can be due to timeout or bad requests. ...
  50. The redistributable package for the Windows Media Format Runtime must be installed before you can deploy Microsoft Communications ...
  51. The RegistrationEnabled property is readonly and cannot be changed. This is most likely because SipEndpoint instances require ...
  52. The remote domain controller is unavailable Remote domain: %1 Exception:%2 Cause: A network issue or domain controller issue ...
  53. The remote share is experiencing very high latency. In order to preserve resources that may affect other services running ...
  54. The replication of certificates from the central management store to the local machine failed due to a problem assigning ...
  55. The replication of certificates from the central management store to the local machine failed due to a problem with certificate ...
  56. The replication of certificates from the central management store to the local machine failed due to a problem with encryption ...
  57. The replication of certificates from the central management store to the local machine failed due to an unexpected exception. ...
  58. The replication service host encountered an error. Microsoft Lync Server 2013, Replica Replicator Agent will continuously ...
  59. The request cannot be processed at this time. Try again later or contact your support team to check the server configuration. ...
  60. The request cannot be processed due to connecting Lync Server central management database failed. Server configuration error ...
  61. The request contains an invalid combination of Endpoint-URI, SIP-Instance, and Epid fields; each request must contain exactly ...
  62. The request DNS records number is different from the response from server. Tenant: '%1', Request DNS Change Number: '%2', ...
  63. The request is throttled because the server is busy or you have exceeded the maximum connections limit allowed for an administrator. ...
  64. The requested certificate was successfully submitted and automatically enrolled and stored in the local certificate store ...
  65. The Response Group could not be deployed due to an unexpected error. Verify that the SIP address and the telephone number ...
  66. The Response Group could not be saved because one or more settings are not valid. Please review the top of this web page ...
  67. The Response Group could not be updated due to an unexpected error. Verify that the telephone number of the workflow is unique. ...
  68. The response group templates help you to design a new workflow. Each template has a defined set of features. To create a ...
  69. The role (Sharer or Viewer) and Content type. It should be of the form Sharer/Viewer:{Desktop, Monitor1, Monitor2, Dual Monitor, ...
  70. The role-based access control (RBAC) role '{0}' cannot contain '{1}', because '{1}' is not a Lync Server cmdlet. Only Lync ...
  71. The roles in the topology and the installed roles do not match. Run Bootstrapper to update the roles installed on this computer. ...
  72. The roll back bit to unblock Exchange roll back was configured on Exchange, but because migration was in progress for the ...
  73. The Routing Data Sync Agent has completed a sync cycle with: %1], Succeeded: %2], Duration: %3], ModifiedBatchCount: %4], ...
  74. The RPS certificate for Microsoft Lync Online, Administration Center could not be loaded. RPS error code: %1 Cause: RPS certificate ...
  75. The SCOM Data Collector encountered some error. Error: %1 Cause: An internal error occurred. Resolution: Examine the error ...