Lync Server 2013

  1. Access Edge Server external edge FQDN cannot be located in the certificate configured for its external edge. External FQDN: ...
  2. Access Edge Server internal edge FQDN cannot be located in the certificate configured for its internal edge. Internal FQDN: ...
  3. Access to the Lync Server Control Panel is controlled by a group membership in universal group "CSAdministrator". Add designated ...
  4. Access to the Session Tickets web service failed. Web-based clients will fail joining and PowerPoint presentations will not ...
  5. According to the configuration option you have chosen, the FQDNs and IPs for all three Edge services should be the same. ...
  6. According to the configuration option you have chosen, the FQDNs and IPs for all three Edge services should be the same. ...
  7. According to the configuration option you have chosen, the FQDNs and IPs for all three Edge services should be the same. ...
  8. According to the configuration option you have chosen, the ports for all three Edge services should be the same. You have ...
  9. Account credentials for Kerberos authentication are not properly configured. Account domain: %1, user name: %2, password ...
  10. Account credentials for Kerberos authentication could not be added. Account domain: %1, user name: %2, exception details: ...
  11. ACP Synthetic Transaction failed because ACP MCU dial out did not succeed in expected time. Please check if the phone number ...
  12. ACP Synthetic Transaction failed because ACP MCU failed to bootstrap or could not be allocated. Timed out after waiting for ...
  13. ACP Synthetic Transaction failed because bridge uri was not found in the conference roster. This indicates a bridging failure. ...
  14. ACP Synthetic Transaction failed because dial out user endpoint provided does not have a phone number assigned. Please make ...
  15. ACP Synthetic Transaction failed because the conferencing policy assigned to the organizer does not allow anonymous users ...
  16. Active Directory indicates that user is homed on a different server but user data exists on this server as well. Active Directory ...
  17. Active Directory indicates that user is homed on a different server but user data exists on this server as well. Active Directory ...
  18. Active Directory operation failed on "{0}". The credential supplied for "{1}" on "{2}" operation is invalid. Error Code: ...
  19. Active Directory operation failed on "{0}". The credential supplied on "{1}" operation is invalid. Failed to retrieve current ...
  20. Active Directory operation failed on "{0}". There are too many entries that exceed the limit of the virtual list view. "{1} ...
  21. Active Directory operation failed on "{0}". There are too many entries that exceed the limit of the virtual list view. "{1}" ...
  22. Active Directory operation failed on "{0}". This error could have been caused by user input or because the Active Directory ...
  23. Active Directory operation failed on "{0}". This error could have been caused by user input or because the Active Directory ...
  24. Active Directory operation failed while verifying validity of service account password Active Directory operation failed ...
  25. Active Directory universal groups are not ready at this time. Either prepare the forest first, or wait for replication to ...
  26. ActiveX isn't enabled in your browser. Please enable ActiveX and refresh the page. How? You can still join the meeting but ...
  27. Add or remove computers in current topology in XDS Database and assign permissions for computers in Active Directory. Are ...
  28. AddConference request failed, Reason validation failed: Failed to retrieve meeting policy from CCCP request, Origin of request: ...
  29. Adding permissions to local group '[Property_RTCComponentLocalGroup]' on Centralized Logging Service performance counters ...
  30. Adding permissions to local group '[Property_RTCComponentLocalGroup]' on URL Property_ListeningURL_XmppGw_SubscribersListener] ...
  31. Adding permissions to local group '[Property_RTCLocalReadOnlyAdministrators]' on Lync Server 15 (Technical Preview) event ...
  32. Adding permissions to local group '[Property_RTCLocalReadOnlyAdministrators]' on PROPERTY_SERVICENAME_DATAPROCESSSERVICE] ...
  33. Adding permissions to local group '[Property_RTCServerLocalGroup]' on Centralized Logging Service performance counters registry ...
  34. Adding permissions to local group '[Property_RTCServerLocalGroup]' on Client Version Filter performance counters registry ...
  35. Adding permissions to local group '[Property_RTCServerLocalGroup]' on Enterprise Services performance counters registry key ...
  36. Adding permissions to local group '[Property_RTCServerLocalGroup]' on Intelligent IM Filter performance counters registry ...
  37. Adding permissions to local group '[Property_RTCServerLocalGroup]' on Routing Applications performance counters registry ...
  38. Adding permissions to local group on Monitoring Server performance counters registry key. Group:'[Property_RTCComponentLocalGroup]' ...
  39. Additional services will be added to all registrar, director, and access proxy roles every time this command is run. Are ...
  40. Address book (AB) entries are populated successfully during UR initial cycle for domain %1 (DN: %2). Number of objects examined ...
  41. Address Book Request web service could not be started. Exception information : %1. Cause: Startup errors. Resolution: Check ...
  42. Address Book Request web service encountered an exception %1 Cause: Unexpected exception occurred while processing a HTTP ...
  43. Address Book Server has encountered an unexpected exception. Exception: %1 Exception Type: %2 %3 Cause: Internal Error Resolution: ...
  44. Address Book Server is unable to access the output location. No output files will be generated. Path: %1 Exception: %2 Cause: ...
  45. Address Book Server is unable to generate its output files as the output location configured is invalid. Cause: Either configuration ...
  46. Address Book Server settings have been changed. Run Time: %1 (%2) Generate Output Files: %3 Use Normalization Rules: %4 syncnow ...
  47. Address Book Server was unable to perform its heartbeat function against the back-end database after 3 attempts. SQL Connection ...
  48. Address Book Server was unable to set the time for the next synchronization pass in the SQL back-end data base. SQL Connection ...
  49. Address Book web service encountered an exception. %1 Cause: Unexpected exception occurred while accessing Central Management ...
  50. Address Book Web Service failed to initialize Exception: %1 Cause: Unexpected exception occurred during initialization. Resolution: ...
  51. Adds Active Directory access control entries (ACEs) required to host Lync Server services in a domain. Are you sure you want ...
  52. Adds Active Directory schema extensions to support Lync Server 2013 deployments in an Active Directory forest. Are you sure ...
  53. Adds Active Directory schema extensions to support Lync Server 2013 service deployments in an Active Directory forest. Are ...
  54. Adds Active Directory service information and assigns permissions to global resources within the topology. Are you sure you ...
  55. Adds global Active Directory containers, universal groups, and access control entries (ACEs) required to host Lync Server ...
  56. ADPagedReader results cannot be enumerated twice. As the results are iterated over, memory is made available for the next ...
  57. After successfully running the Power Shell Scripts ExchUCUtil.ps1 and Get-UCPool.ps1 on your Exchange 2007 Server, the Lync ...
  58. After you complete the wizard, you need to enter server configuration information, such as IP addresses, fully qualified ...
  59. After you make changes to the fully qualified domain name (FQDN) or listening ports, you must run local Setup on all servers ...
  60. Aggregation script failed to register with the server within 30 seconds. Cause: Server is low on resources. Resolution: Ensure ...
  61. All authentication security packages are disabled, so a message containing authentication information was dropped. Cause: ...
  62. All computers in an Enterprise pool must have fully qualified domain names (FQDNs) that are different from the Enterprise ...
  63. All conference directory IDs are removed. To do so, in Lync Server Management Shell, run the Remove-CsConferenceDirectory ...
  64. All configuration data was loaded, but some bad data was detected and will not be used. Cause: Review preceding event log ...
  65. All domains defined in Lync Server 2013 must be same as domains defined in "{0}" / "{1}" before you can continue merging ...
  66. All domains defined in Lync Server 2013 must be same as domains defined in "{0}" / "{1}" before you can continue merging ...
  67. All Front End pools are currently assigned to an existing Archiving Server or a Front End pool that has not been defined ...
  68. All Front End pools are currently assigned to an existing Monitoring Server or a Front End pool has not been defined yet. ...
  69. All Gateways are marked as Down Or Unavailable. Cause: All Gateways are unresponsive and consequently unable to route calls ...
  70. All policies of type "{0}" are not migrated. Run the Import-CsLegacyConfiguration cmdlet to migrate all policies. For details ...
  71. All pools and computers that are defined in the topology are currently active. If they are not, please remove inactive computers ...
  72. All the SQL Server stores in this topology are collocated with the services that depends on them. This wizard can only be ...
  73. All User service pools are in standby mode. Verify the Provisioning service configuration on the Central Management Server. ...
  74. Allow: Allows the client to log on to the pool. If you apply this setting, you must add block rules to prevent invalid client ...
  75. Allow: Allows the client to log on to the pool. If you apply this setting, you must add block rules to prevent invalid client ...