Lync Server 2013

  1. Unknown Server Name in incoming HTTPS certificate. Server FQDN: %1 Issuer: %2 Cause: A connection attempt from an unknown ...
  2. Update Conflict occurred for {0}. File is opened with read/write access by some other process. Current Retry Count= {1}, ...
  3. Update pool assignment overwrite rules in service. Please use Get-csProvisionPoolAssignmentOverwriteRules -asXml to get more ...
  4. Update the deployment configuration store location using Set-CsConfigurationStoreLocation or change the central management ...
  5. Updates to settings associated with the service '{0}' are not allowed since its associated registrar '{1}' is in failed over ...
  6. Updating session key failed. It will be retried after some time. Error %1 Cause: This could be due to low resource conditions. ...
  7. Upload schema failed. Try running the ldifde command directly for more details about the error. Verify that Active Directory ...
  8. Use of wildcard "*" for SIP domains is not supported in Lync Server 2013. To correct this problem, please use the Global ...
  9. Use of wildcard in "{0}" SIP domain is not supported in Lync Server 2013. To correct this problem, please use the Global ...
  10. Use Set-CsKerberosAccountPassword to correct the Kerberos configuration data of the computer. This may require transferring ...
  11. Use the task Add/Edit/Remove to configure or change your Office Communications Server 2007 R2 Edge configuration, and then ...
  12. Used for Address Book downloads, Address Book Web Query service, client updates, meeting content, device updates, group expansion, ...
  13. User %1 provided a routing document with errors. Default call handling was applied instead. %2 Problems with this user's ...
  14. User %1 provided a routing preamble that references an unknown built in script. Missing script name=%2 version=%3. Problems ...
  15. User '[2]' has previously initiated an install for product '[3]'. That user will need to run that install again before they ...
  16. User '[2]' has previously initiated an install for product '[3]'. That user will need to run that install again before they ...
  17. User authentication with NTLM protocol failed with error SEC_E_UNSUPPORTED_FUNCTION. This indicates a potential mismatch ...
  18. User authentication with NTLM protocol took longer than expected (more than 15 seconds). There were %2 instances of NTLM ...
  19. User entry update in Active Directory failed while moving user. (0) User: %1 Error: 2 Cause: Domain controller may be unreachable. ...
  20. User entry update in Active Directory failed while moving user. (4) User: %1 Error: 2 Cause: Domain controller may be unreachable. ...
  21. User failed to join the conference. %1 Cause: Administration issues. Resolution: Verify that Conferencing Attendant is installed ...
  22. User has a phone number that is associated with other user(s). %1 shares same phone number with following other users (up ...
  23. User is at an unsupported country/region. TenantId: '%1', ObjectId: '%2' User location: '%3' Cause: User is at an unsupported ...
  24. User is enabled for SIP and homed on w14 server, but required Cluster Policy or Deployment Locator is missing. Resolve the ...
  25. User principal name (UPN) is not set for user "{0}". You must set a UPN for the user to use role-based access control (RBAC). ...
  26. User Replicator connected to domain controller %1 in domain %2 (DN: %3) to perform synchronization The source of the replication ...
  27. User Replicator failed to put Active directory objects data into the database for an unknown reason. The attempt will be ...
  28. User Replicator has completed initial synchronization of domain %1 (DN: %2) and the database. Future synchronization for ...
  29. User Replicator has started initial synchronization of domain %1 (DN: %2) and the database. Initial synchronization occurs ...
  30. User Service Pools status. Normal Pools: '%1' Standby Pools: '%2' Reserved for legacy tenant Pools: '%3' In Migration Mode:'%4' ...
  31. User was found in migrating mode. Because you used the Force option, unified contact store mode was set to disabled for the ...
  32. User was found in ucs mode and was rolled back but an error occurred while replicating the data. Run the cmdlet again to ...
  33. User was found in unified contact store mode. Contact list was successfully rolled back and any future migration attempts ...
  34. User was not found in unified contact store mode. An attempt to hold off future migrations for a preconfigured time failed ...
  35. User was not in unified contact store mode. Unified contact store mode was set to disabled for the user and any future migration ...
  36. User's voicemail URI is not specified. Please verify and ensure that the user is not UM enabled and enterprise voicemail ...
  37. Users are not indexed in the database that should be. Expected indexed user count: %1 Actual indexed user count: %2 Cause: ...
  38. Users who don't have these settings can't schedule meetings with dial-in conferencing. Click "yes" to turn off dial-in conferencing ...
  39. Users who have already been migrated to the Unified Contact Store (UCS) or who are about to be migrated to the Unified Contact ...
  40. Using the mirroring endpoint with name "{0}" and port {1} on database server "{2}". If the computer running this SQL Server ...
  41. Validate that replication is complete. In Lync Server Management Shell, run the Get-CsManagementStoreReplicationStatus cmdlet. ...
  42. Validating that conference directory with ID "{0}" is in a suitable state and checking for consistency between configuration ...
  43. Value is not valid external access prefix. Must be no longer than 4 characters long and can contain only digits, # or a *. ...
  44. Value may only begin with a letter or underscore and can only contain letters, digits, underscores, hyphens, and periods. ...
  45. Value may only begin with a letter, underscore, or colon and can only contain letters, digits, underscores, colons, hyphens, ...
  46. Value of registry key parameter {0} under {1} in {2} does not exist or is not valid. Only supported values are {3}, {4} or ...
  47. Verify that the account used to run this cmdlet has sufficient permissions to update the management connection in Active ...
  48. Verify that the Central Management Store is accessible and that the account used to run this cmdlet has sufficient permissions ...
  49. Verify that the Central Management Store is accessible and that the account used to run this cmdlet has sufficient permissions ...
  50. Verify that the Central Management Store is accessible and that the account used to run this cmdlet has sufficient permissions ...
  51. Verify that the Central Management Store is accessible and that the account used to run this cmdlet has sufficient permissions ...
  52. Verify that the connection path points to the Central Management Store, or that the document type can be written to the local ...
  53. Verify that the connection string points to a valid configuration database or replica, and that your account has sufficient ...
  54. Verify that the Lync Server 2013, Core Components are correctly installed and that the "{0}" interface is registered on the ...
  55. Verify that the Lync Server Backup Service is running on source pool '{0}' or run the cmdlet with the -Force parameter to ...
  56. Verify that the SQL Server instances are available and that the accounts running the primary and mirror SQL Server instances ...
  57. Verify that your user account has administrative privileges, and that you selected "Run as administrator" when you started ...
  58. Verify the computer account exists and has the correct configuration in Active Directory, and run Enable-CsTopology to restore ...
  59. Version of service "{0}" does not match current allowable version "{1}". Run the cmdlet again with the ProxyPool parameter. ...
  60. Voice quality is determined by the Differentiated Services Code Point (DSCP) value that you select (that is, 0-63). The default ...
  61. Voice, video, and presenting features aren't working because Desktop Experience isn't turned on. To turn it on, go to Windows ...
  62. Waiting on a response from the replica machine %1. Microsoft Lync Server 2013, File Transfer Agent will continue to wait ...
  63. Warning: It is possible to lose data when you use backup files to move the Central Management Server. Use backup files only ...
  64. Warning: Not all of the sites in the topology have been configured for call admission control. If call admission control ...
  65. Warning: Pairing two pools in the same site is not recommended for disaster recovery purposes. If the site fails, both pools ...
  66. Warning: Pool '{0}' is currently hosting the call admission control (CAC) component for site '{1}'. Assign CAC to a different ...
  67. Warning: Target Central Management Server Pool does not have a mirror set while the original pool has mirroring enabled. ...
  68. Warning: The Archiving settings for the following Survivable Branch Appliances will be updated with the new setting: {0}. ...
  69. Warning: The archiving settings for the following Survivable Branch Appliances will not be updated with the new setting because ...
  70. Warning: The associated Front End Server or pool is not associated with a Monitoring Server. We recommend that Survivable ...
  71. Warning: The associated Front End Server or pool is not associated with an Archiving Server. We recommend that Survivable ...
  72. Warning: The associated Front End Server or pool uses Archiving Server '{0}'. We recommend that Survivable Branch Appliances ...
  73. Warning: The associated Front End Server or pool uses Monitoring Server '{0}'. We recommend that Survivable Branch Appliances ...
  74. Warning: The cmdlet is not being run from a computer in the pool '{0}', which is where the Central Management service will ...
  75. WARNING: The monitoring reports will overwrite existing reports already deployed in the specified SQL Server Reporting Services ...