Lync Server 2010

  1. Unable to use the certificate configured for the internal edge of the Access Edge Server. Error %1 (%2). Cause: The certificate ...
  2. Unable to use the default outgoing certificate. Error %1 (%2). Cause: The certificate may have been deleted or may be invalid, ...
  3. Unable to validate xml Over the past %1 minutes Lync Server has received invalid xml %2 times. Xml data: %3 Exception: %4 ...
  4. Unable to write registry value under a key. The LS A/V Edge Server service will stop. Key Path: %1 Value Name: %2 Value Type: ...
  5. Unavailable authorization authority causing errors. There were %2 failures because the authority was unavailable in the last ...
  6. Unexpected authentication challenge responses (401/407) received from a non-server source. Over the past %1 minutes, %2 challenge ...
  7. Unexpected error occurred in the Bandwidth Policy Service (Core). Exception: %1 Cause: An unexpected error has occurred. ...
  8. Unexpected error occurred in the LS Audio/Video Authentication service. Exception: %1 Cause: An unexpected error has occurred. ...
  9. Unexpected error occurred in the LS Bandwidth Policy Service (Authentication). Exception: %1 Cause: An unexpected error has ...
  10. Unexpected error occurred in the Mediation Server. Mediation Server stopped listening for incoming connections on gateway ...
  11. Unexpected error occurred in the Mediation Server. Mediation Server stopped listening for incoming connections on proxy side. ...
  12. Unexpected exception is thrown while handling Certificates Changed event. Message=%1 Exception: %2 Stack Trace: %3 Cause: ...
  13. Unexpected exception is thrown while handling Policy Map Changed event. Message=%1 Exception: %2 Stack Trace: %3 Cause: Event ...
  14. Unexpected exception is thrown while handling Provisioning Service Setting Changed event. Message=%1 Exception: %2 Stack ...
  15. Unexpected exception is thrown while handling Service Assignments Changed event. Message=%1 Exception: %2 Stack Trace: %3 ...
  16. Unexpected exception is thrown while handling Topology Changed event. Message=%1 Exception: %2 Stack Trace: %3 Cause: Event ...
  17. Unexpected exception is thrown while provisioning a contact. TenantId: '%1', ObjectId: '%2' Message=%3 Exception: %4 Stack ...
  18. Unexpected exception is thrown while provisioning a tenant. TenantId: '%1' Message=%2 Exception: %3 Stack Trace: %4 Cause: ...
  19. Unexpected exception is thrown while provisioning a user. TenantId: '%1', ObjectId: '%2' Message=%3 Exception: %4 Stack Trace: ...
  20. Unexpected exception is thrown while running the provisioning thread. Message=%1 Exception: %2 Stack Trace: %3 Cause: Unexpected ...
  21. Unexpected exception is thrown while running the publishing thread. Message=%1 Exception: %2 Stack Trace: %3 Cause: Unexpected ...
  22. Unexpected exception is thrown while running the sync thread. Message=%1 Exception: %2 Stack Trace: %3 Cause: Unexpected ...
  23. Unexpected exception is thrown while updating publish status. TenantId: '%1', ObjectId: '%2' Message=%3 Exception: %4 Stack ...
  24. Unexpected exception occurred in the Translation Service. Message: %1 Stack: %2 Cause: An exception occurred during the processing ...
  25. Unexpected exception occurred while processing a request. This event will only be reported every 15 minutes even if more ...
  26. Unexpected exception occurred while processing a response. This event will only be reported every 15 minutes even if more ...
  27. Unexpected exception. Message=%1 Exception: %2 Stack Trace: %3 Cause: Unexpected exception. Resolution: Notify your organization's ...
  28. Unhandled exception occurred in the Response Group Service Configuration Tool. The operation could not complete successfully. ...
  29. Unhandled exception occurred when the service was running on a thread pool thread used by the platform. Unhandled exception: ...
  30. Unhandled exception was thrown. The process %1 throw an unhandled exception:%2. Stack: %3. Inner exception: %4. Cause: This ...
  31. Unknown Server Name in incoming HTTPS certificate. Server FQDN: %1 Issuer: %2 Cause: A connection attempt from an unknown ...
  32. Unsupported target class type. TenantId: '%1', Source: '%2', Target:'%3' Message=%4 Target Class type of %5 is not expected ...
  33. Update Lync Server 2010 with the changes defined in the topology by running local Setup on each server in the following list. ...
  34. Update the deployment configuration store location using Set-CsConfigurationStoreLocation or change the central management ...
  35. Updating session key failed. It will be retried after some time. Error %1 Cause: This could be due to low resource conditions. ...
  36. Upload schema failed. Try running the ldifde command directly for more details about the error. Verify that Active Directory ...
  37. Use of wildcard "*" for SIP domains is not supported in Lync Server 2010. To correct this problem, please use the Global ...
  38. Use of wildcard in "{0}" SIP domain is not supported in Lync Server 2010. To correct this problem, please use the Global ...
  39. Use Set-CsKerberosAccountPassword to correct the Kerberos configuration data of the computer. This may require transferring ...
  40. Use the task Add/Edit/Remove to configure or change your version 2007 or 2007 R2 Edge configuration, and then click Next ...
  41. Use this wizard to make Office Communications Server 2007 or 2007 R2 components available to the Lync Server 2010 deployment. ...
  42. User %1 provided a routing document with errors. Default call handling was applied instead. %2 Problems with this user's ...
  43. User %1 provided a routing preamble that references an unknown built in script. Missing script name=%2 version=%3. Problems ...
  44. User '[2]' has previously initiated an install for product '[3]'. That user will need to run that install again before they ...
  45. User '[2]' has previously initiated an install for product '[3]'. That user will need to run that install again before they ...
  46. User authentication with NTLM protocol failed with error SEC_E_UNSUPPORTED_FUNCTION. This indicates a potential mismatch ...
  47. User authentication with NTLM protocol took longer than expected (more than 15 seconds). There were %2 instances of NTLM ...
  48. User entry update in Active Directory failed while moving user. (0) User: %1 Error: 2 Cause: Domain controller may be unreachable. ...
  49. User entry update in Active Directory failed while moving user. (4) User: %1 Error: 2 Cause: Domain controller may be unreachable. ...
  50. User failed to join the conference. %1 Cause: Administration issues. Resolution: Verify that Conferencing Attendant is installed ...
  51. User has a phone number that is associated with other user(s). %1 shares same phone number with following other users (up ...
  52. User is at an unsupported country/region. TenantId: '%1', ObjectId: '%2' User location: '%3' Cause: User is at an unsupported ...
  53. User is enabled for SIP and homed on w14 server, but required Cluster Policy or Deployment Locator is missing. Resolve the ...
  54. 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). ...
  55. User Replicator failed to put user data into the database for an unknown reason. The attempt will be retried. Stored procedure: ...
  56. User Replicator has completed initial synchronization of domain %1 (DN: %2) and the database. Future synchronization for ...
  57. User Replicator has started initial synchronization of domain %1 (DN: %2) and the database. Initial synchronization occurs ...
  58. User Service Pools status. Normal Pools: '%1' Standby Pools: '%2' Reserved for legacy tenant Pools: '%3' In Migration Mode:'%4' ...
  59. Utility for exporting, managing, and importing XML files containing homed resource data from a Microsoft Lync Server 2010 ...
  60. Validate that replication is complete. In Lync Server Management Shell, run the 'Get-CsManagementStoreReplicationStatus cmdlet'. ...
  61. Validating that conference directory with ID "{0}" is in a suitable state and checking for consistency between configuration ...
  62. Value is not valid external access prefix. Must be no longer than 4 characters long and can contain only digits, # or a *. ...
  63. Value may only begin with a letter or underscore and can only contain letters, digits, underscores, hyphens, and periods. ...
  64. Value may only begin with a letter, underscore, or colon and can only contain letters, digits, underscores, colons, hyphens, ...
  65. Verify that the account used to run this cmdlet has sufficient permissions to update the management connection in Active ...
  66. Verify that the Central Management Store is accessible and that the account used to run this cmdlet has sufficient permissions ...
  67. Verify that the Central Management Store is accessible and that the account used to run this cmdlet has sufficient permissions ...
  68. Verify that the Central Management Store is accessible and that the account used to run this cmdlet has sufficient permissions ...
  69. Verify that the Central Management Store is accessible and that the account used to run this cmdlet has sufficient permissions ...
  70. Verify that the connection path points to the Central Management Store, or that the document type can be written to the local ...
  71. Verify that the connection string points to a valid configuration database or replica, and that your account has sufficient ...
  72. Verify that the Lync Server 2010, Core Components are correctly installed and that the "{0}" interface is registered on the ...
  73. Verify that your user account has administrative privileges, and that you selected "Run as administrator" when you started ...
  74. Verify the computer account exists and has the correct configuration in Active Directory, and run Enable-CsTopology to restore ...
  75. Version of service "{0}" does not match current allowable version "{1}". Run the cmdlet again with the ProxyPool parameter. ...