Lync Server 2010

  1. Invalid certificate selected for TLS connections. Issuer: %1 Serial Number: %2 Cause: Settings configured incorrectly. Resolution: ...
  2. Invalid certificate selected for TLS connections. Issuer: %1 Serial Number: %2 Subject Name: %3 Cause: The SN / SAN of the ...
  3. Invalid client update file "{0}". File type extension "{1}" is invalid. The file type extension must be one of the following: ...
  4. Invalid data in IIS configuration file. Setting name %1, exception details: %2. Resolution: Reinstall Web Components Server ...
  5. Invalid database access account(s) specified. Please ensure the specified database access accounts are valid domain or machine ...
  6. Invalid dependency between bandwidth policy profile {0} and inter-network site policy {1}. Cannot set a inter-network site ...
  7. Invalid dependency between bandwidth policy profile {0} and network region link {1}. Cannot set a network region link to ...
  8. Invalid dependency between bandwidth policy profile {0} and site {1}. Cannot set a site to depend on a nonexistent bandwidth ...
  9. Invalid dependency between network region link {0} and inter-network region route {1}. Cannot set a inter-network region ...
  10. Invalid dependency between network region {0} and inter-network region route {1}. Cannot set a inter-network region route ...
  11. Invalid dependency between network region {0} and network region link {1}. Cannot set a network region link to depend on ...
  12. Invalid dependency between network region {0} and site {1}. Cannot set a site to depend on a nonexistent network region, ...
  13. Invalid dependency between site {0} and inter-network site policy {1}. Cannot set a inter-network site policy to depend on ...
  14. Invalid dependency between site {0} and subnet {1}. Cannot set a subnet to depend on a nonexistent site, or remove a site ...
  15. Invalid federation next hop ServiceId "{0}" for SiteId "{1}". The configured federation next hop edge server is not federation ...
  16. Invalid federation next hop ServiceId "{0}" for SiteId "{1}". The configured federation next hop is not a valid service in ...
  17. Invalid federation next hop ServiceId "{0}" for SiteId "{1}". The configured federation next hop must be either a Director ...
  18. Invalid federation next hop ServiceId="{0}" for SiteId "{1}". The configured federation next hop director is not configured ...
  19. Invalid federation next hop ServiceId="{0}" for SiteId="{1}". The federation next hop Edge Server is configured to use a ...
  20. Invalid FQDN Filter. FQDN may either be an IP address or an FQDN. If an FQDN, it may begin with *. to match all subdomains. ...
  21. Invalid identity "{0}". An identity cannot end with a "/" slash mark. Remove the trailing "/" slash mark or provide a key ...
  22. Invalid incoming HTTPS certificate. Subject Name: %1 Issuer: %2 Cause: This can happen if the HTTPS certificate has expired, ...
  23. Invalid Instance. Verify that the object that was passed to Instance parameter is the correct type for this cmdlet and the ...
  24. Invalid Line URL detected for the user %1 (enabled for Pc-to-Pc Voice). Line URL for Pc-to-Pc voice enabled users must be ...
  25. Invalid Line URL detected for user %1 (enabled for Enterprise Voice). Line URL for Enterprise Voice Enabled Users must be ...
  26. Invalid Line URL detected for user %1 (enabled for PBX Integration) Line URL for PBX Integration Enabled Users must be specified ...
  27. Invalid Mediation Server listening address/port. Listening Address: %1 Listening Port: %2 Cause: Settings configured incorrectly. ...
  28. Invalid path for script-only application Path: %1 Cause: Incorrect path was entered in while configuring this application ...
  29. Invalid phone number format. Use a sequence of digits, which can be preceded by a plus symbol (+) or succeeded by an extension. ...
  30. Invalid Private Line URL detected for the user %1. Telephone data will not be replicated until this problem is fixed. Private ...
  31. Invalid Private Line URL detected for user %1 (not enabled for Enterprise Voice). Private Line URL may be specified only ...
  32. Invalid setting. Setting: %1 Property: %2 Cause: Settings configured incorrectly. Resolution: Configure the Mediation Server ...
  33. Invalid Telephone URL detected for the user %1. Telephone data will not be replicated until this problem is fixed. Resolution: ...
  34. Invalid Trunk Configuration Settings Error: %1 Cause: One or more Trunk Configuration Settings are invalid. Resolution: Use ...
  35. Invalid Vacant Number Settings Error: %1 Cause: One or more Vacant Number Settings are invalid. Resolution: Use the appropriate ...
  36. Invalid value for number range end (NumberRangeEnd). Value must match the following pattern: (tel:)?(\+)?[1-9]\d{0,17}(;ext=[1-9]\d{0-9})? ...
  37. Invalid value for number range start (NumberRangeStart). Value must match the following pattern: (tel:)?(\+)?[1-9]\d{0,17}(;ext=[1-9]\d{0-9})? ...
  38. is already enabled for Lync Server 2010. If you want to use the current object as a common area phone, either disable or ...
  39. is already enabled for Lync Server 2010. If you want to use the current object as an analog device, either disable or remove ...
  40. is configured with one or more of the user account control flags {1} disabled. Kerberos authentication may not work correctly. ...
  41. is configured with one or more of the user account control flags {1} enabled. Kerberos authentication may not work correctly. ...
  42. is not a fully qualified domain name (FQDN). Short domain names are not supported. For example, specify an FQDN like "{1}". ...
  43. is not a fully qualified domain name (FQDN). Short domain names are not supported. For example, specify an FQDN like "{1}". ...
  44. is not a Registrar pool. Run Get-CsPool to find available pools. Or, open Lync Server Control Panel, click Topology, and ...
  45. is not a Registrar pool. Run Get-CsPool to find available pools. Or, open Lync Server Control Panel, click Topology, and ...
  46. is not a trusted application pool. Run Get-CsTrustedApplicationPool to find available pools. Or, open Lync Server Control ...
  47. is not a trusted application pool. Run Get-CsTrustedApplicationPool to find available pools. Or, open Lync Server Control ...
  48. is not a universal security group. To use a group for a role-based access control (RBAC) role, the group must be a universal ...
  49. is not a universal security group. To use a group for a role-based access control (RBAC) role, the group must be a universal ...
  50. Issues start commands for all Lync Server services. Note: This wizard initiates service start-up without waiting for each ...
  51. It is not secure to allow users to have PIN length of less than five digits. Also, it is very easy for the users to get locked ...
  52. It was possible to create the new contact object in Active Directory; however, an error occurred that prevented the contact ...
  53. Line URI must contain a normalized, unique primary phone number when a user is enabled for dial-in conferencing, Enterprise ...
  54. Listener URL configured is incorrect The listener URL %1 specified for process %2 is invalid. Cause: Incorrect setup of the ...
  55. Listening port defines the IIS configuration on servers in the pool and Published port reflects the configuration of a load ...
  56. Local user %1 has sent a significant number of messages that have resulted in domain validation failures. There have been ...
  57. Location Information Service encountered an unexpected exception during Certificates change notification processing. Exception: ...
  58. Location Information Service encountered an unexpected exception during Initialization. Exception: %1 Cause: An unexpected ...
  59. Location Information Service encountered an unexpected exception during Location Information Settings change notification ...
  60. Location Information Service encountered an unexpected exception during Web Service Settings change notification processing. ...
  61. Location profile name: "{0}" does not have any normalization rules associated with it. Check location profile in the "{1}"/ ...
  62. Logging of all message bodies is enabled in the registry, which may be a privacy concern. The "%1" registry key is defined ...
  63. Lost connection to all Lync Web App locations. Cause: Service may be unavailable or Network connectivity may have been compromised. ...
  64. Lost connection to all Web Conferencing Edge Services. Cause: Service may be unavailable or Network connectivity may have ...
  65. Lost connection to the Web Conferencing Edge Server Edge Server Machine FQDN: %1 Cause: Service may be unavailable or Network ...
  66. Lost connection to the with Lync Web App Server Machine FQDN: %1 Server Type: %2 Cause: Service may be unavailable or Network ...
  67. Lost connectivity to global catalog. The LDAP session (id = %1) was disconnected from the global catalog %2. Attempting to ...
  68. LS A/V Edge Server definition was removed from the topology configuration. The service will continue to run; however, once ...
  69. LS A/V Edge Server failed to allocate a port. ClientID %1 Cause: Either all configured ports on the Audio/Video Edge Server ...
  70. LS A/V Edge Server failed to initialize shared secrets. Exception: %1 Cause: Either the authentication certificate is not ...
  71. LS A/V Edge Server failed to open a network endpoint. Protocol %1 Address %2 Port %3 Cause: Either an invalid configuration ...
  72. LS A/V Edge Server startup is pending because the configuration database is not yet available. Cause: There may be connectivity ...
  73. LS Audio/Video Authentication service configuration settings have been updated and automatically loaded by the service. Action: ...
  74. LS Audio/Video Authentication service could not be started. Exception: %1 Cause: Internal error. Resolution: Examine the ...
  75. LS Audio/Video Authentication service definition was removed from the topology configuration. The service will continue to ...