Lync Server 2013

  1. Failed to start the Fabric Pool Manager. Cause: The Server failed to start the Fabric Pool Manager. This should not occur ...
  2. Failed to stop kernel mode driver component Driver Name: %1 Exception: %2 Cause: Driver is not responding in a timely fashion. ...
  3. Failed to suspend sync from blob store. Cause: This may indicate a problem with connectivity to local or backup database ...
  4. Failed to sync data for Routing group %1 from backup store. Cause: This may indicate a problem with connectivity to backup ...
  5. Failed to synchronize remote domain %1 due to missing data privacy boundary for local or remote domain. Source of replication ...
  6. Failed to update Mcu health in the backend. This will be retried but if this continues to occur conferencing functionality ...
  7. Failed to update pool state in backup database. Pool: %1. State: %2. Era: %3. Execution Error: %4. Native Error: %5. Error ...
  8. Failed to update pool state in local database. Pool: %1. State: %2. Era: %3. Execution Error: %4. Native Error: %5. Error ...
  9. Failed to update source pool during move. User: %1. Execution Error: %2. Native Error: %3. Error Details: %4. Cause: This ...
  10. Failed to update the Archiving purge settings in the Archiving database. Component: %1 Error: %2 Cause: Configuration issues ...
  11. Failed to update the auto attendant state for Exchange UM contact. Use Set-CsExUmContact cmdlet to fix the auto attendant ...
  12. Failed to update the Call Detail Recording (CDR) purge settings in the Call Detail Recording (CDR) database. Component: %1 ...
  13. Failed to update the list of domains in this forest to synchronize. The error that occurred was %1 (%2) User Replicator has ...
  14. Failed to update the list of domains in this forest to synchronize. This failure occurred because DsCrackNames failed to ...
  15. Failed to update the list of domains in this forest to synchronize. This failure occurred because DsGetDcName failed to provide ...
  16. Failed to update the list of domains in this forest to synchronize. User Replicator cannot synchronize any objects without ...
  17. Failed to update the list of domains in this forest to synchronize. User replicator cannot synchronize any objects without ...
  18. Failed to update the list of domains in this forest to synchronize. User Replicator doesn't have a list from a previous cycle, ...
  19. Failed to update the Network Configuration settings in the Quality of Experience (QoE) database. Component: %1 Error: %2 ...
  20. Failed to update the Quality of Experience (QoE) External Consumer settings. Component: %1 Error: %2 Cause: Configurations ...
  21. Failed to update the Quality of Experience (QoE) purge settings in the Quality of Experience (QoE) database. Component: %1 ...
  22. Failed to update the Topology configuration. The service will remain in the broken state until the corrected Topology has ...
  23. Failed to update the Web Conferencing Server capability settings. The service will remain in the broken state until the corrected ...
  24. Failed to update WS Federation Token Signing certificate. WS Federation metadata URI:%1, exception details: %2. Cause: The ...
  25. Failed to verify client cookie Over the past %1 minutes Lync Server has failed to validate cookie presented by the clients ...
  26. Failed update user data in local database during move. Execution Error: %1. Native Error: %2. Error Details: %3. Cause: This ...
  27. Failed updating the Conference Auto Attendant configuration. Conferencing on this Pool can continue, but Conference Auto ...
  28. Failed when trying to access or modify registry on machine {0}. Please ensure that you have permissions to modify the registry ...
  29. Failed while retrying the naming context %1. The source of the replication is %2. Resolution: We will retry again later. ...
  30. Failover Central Management services from pool "{0}" using the Invoke-CsManagementServerFailover cmdlet before performing ...
  31. Failover process has encountered an error Pool %1 could not be successfully failed over to pool %2 Cause: Possible issue ...
  32. Fatal error reported for a routing service. Routing Group: %1. Error Code: %2 Cause: This error is unexpected. Please examine ...
  33. fatal|error|warn|info|verbose|noise): least severe log level to search on. For example, if 'warn' is specified search will ...
  34. Federation is the ability to establish communications between your organization and one or more external organizations, including ...
  35. File transfer experienced a timeout. Microsoft Lync Server 2013, File Transfer Agent will continuously attempt to transfer ...
  36. File transfer failed for some replica machines. Microsoft Lync Server 2013, File Transfer Agent will continuously attempt ...
  37. File transfer failed for some replica machines. Microsoft Lync Server 2013, Master Replicator Agent will continuously attempt ...
  38. File transfer failed. Microsoft Lync Server 2013, File Transfer Agent will continuously attempt to transfer the files. Reason: ...
  39. File transfer failed. Microsoft Lync Server 2013, Replica Replicator Agent will continuously attempt to replicate with these ...
  40. Filtering of records is enabled in the Administrator Log. First URI=[%1]; Second URI=[%2]; First FQDN/IP=[%3]; Second FQDN/IP=[%4]; ...
  41. First run of User Replicator on a pristine Database failed. Local store could not be prepared for first time use. Cause: ...
  42. Fix the topology and wait for the backup service to fully synchronize configuration data between the primary and backup pool ...
  43. Flushed queue Items from the Storage Service DB have been left unattended to for some amount of time and require attention ...
  44. For a Standard Edition Front End pool, user information must be stored locally. SQL Server Express Edition will be installed ...
  45. For automatic configuration retrieval: Read access to the Central Management Database through membership in RTCUniversalServerAdmins ...
  46. For each branch site associated with this central site, enter a unique name, as well as the number of users located at the ...
  47. For Enterprise Edition Front End pools and Persistent Chat pools and for Monitoring Servers and Archiving Servers: All SQL ...
  48. For manual configuration installations, such as Edge computer initial setup, no access to the Central Management Database ...
  49. For more information about this problem, see the log file . For information about the most current version of the #(loc.UIProductName), ...
  50. For planning purposes, each branch site must have at least 25 users. Enter a number of users greater than or equal to 25. ...
  51. For the features that you plan to enable, we recommend that you use a hardware load balancer. Do you want to use a DNS load ...
  52. Force cannot be used with -UseSqlBackup. If an earlier move with -UseSqlBackup failed, please run the cmdlet from the original ...
  53. Found "{0}" with the contact distinguished name (DN) (that is, ContactDN) "{1}" by using WMI query. Added it to the dictionary ...
  54. Found %1 per user presence policies. The presence policy maintenance task failed as the count of per user presence policies ...
  55. Found a dependent registrar. This registrar will be used for retrieving information related to authenticated users. Registrar ...
  56. Found an instance of a Communicator Web Access data where the fully qualified domain name (FQDN) is null. This is an invalid ...
  57. Found an instance of Conferencing Announcement application that is installed on a computer where the fully qualified domain ...
  58. Found an instance of Conferencing Attendant application that is installed on a computer where the fully qualified domain ...
  59. Found an instance of pool with the fully qualified domain name (FQDN) "{0}" where the pool type is set to null. The pool ...
  60. Found an instance of Response Group application that is installed on a computer where the fully qualified domain name (FQDN) ...
  61. Found an instance of third-party application that is installed on a computer with the fully qualified domain name (FQDN) ...
  62. Found an instance of UCMA application that is installed on a computer where the fully qualified domain name (FQDN) is null. ...
  63. Found an instance of UCMA application that is installed on the computer "{0}" where the port type is null. This is an invalid ...
  64. Found multiple accounts in Active Directory that match the NT name {0}. Please use an account that is unique or an account ...
  65. Found temporarily locked out users The following users have been found to be temporarily locked:- %1 Cause: The affected ...
  66. Found user with invalid service tag. User: %1 Service Tag: %2 Cause: Please ensure that the topology is correct, and service ...
  67. Found users who are already or about to be permanently locked The following users are either permanently locked out, or about ...
  68. Front End encountered an error when consuming the Network Configuration Settings Change notification. Error code: %1 Cause: ...
  69. Front End encountered an error when consuming the Routing Group Configuration Change notification. Error code: %1 Cause: ...
  70. Fully qualified domain name (FQDN) '{0}' is already in use in this topology. To co-locate with this pool, select "Single ...
  71. GetAndPublish web service failed due to a problem with the request or the user Reason code for failure - %1]. Request Details ...
  72. GetAndPublish web service failed due to an internal error. This may impact user sign-in. Request Details - Entity: %1], Device ...
  73. GetAndPublish web service failed. This may impact user sign-in. Certificate could not be published in the database associated ...
  74. Give your Assigned Conference information and the dial-in phone numbers to people you want to invite to your conference. ...
  75. Global catalog connection not established for the specified LDAP session. When a global catalog connection is available, ...