Lync Server 2010

  1. Aggregation script failed to register with the server within 30 seconds. Cause: Server is low on resources. Resolution: Ensure ...
  2. All authentication security packages are disabled, so a message containing authentication information was dropped. Cause: ...
  3. All computers in an Enterprise pool must have fully qualified domain names (FQDNs) that are different from the Enterprise ...
  4. All conference directory IDs are removed. To do so, in Lync Server Management Shell, run the remove-CsConferenceDirectory ...
  5. All configuration data was loaded, but some bad data was detected and will not be used. Cause: Review preceding event log ...
  6. All domains defined in Lync Server 2010 must be same as domains defined in "{0}" / "{1}" before you can continue merging ...
  7. All domains defined in Lync Server 2010 must be same as domains defined in "{0}" / "{1}" before you can continue merging ...
  8. All Front End pools are currently assigned to an existing Archiving Server or a Front End pool has not been defined yet. ...
  9. All Front End pools are currently assigned to an existing Monitoring Server or a Front End pool has not been defined yet. ...
  10. All Gateways are marked as Down Or Unavailable. Cause: All Gateways are unresponsive and consequently unable to route calls ...
  11. All policies of type "{0}" are not migrated. Run the Import-CsLegacyConfiguration cmdlet to migrate all policies. For details ...
  12. All pools and computers that are defined in the topology are currently active. If they are not, please remove inactive computers ...
  13. All the SQL stores in this topology are collocated with the services that depends on them. This wizard can only be used for ...
  14. All User service pools are in standby mode. Verify the Provisioning service configuration on the Central Management Server. ...
  15. Allow: Allows the client to log on to the pool. If you apply this setting, you must add block rules to prevent invalid client ...
  16. Allow: Allows the client to log on to the pool. If you apply this setting, you must add block rules to prevent invalid client ...
  17. Allows users to choose which program features will be installed and where they will be installed. Recommended for advanced ...
  18. An Active Directory compatibility entry was found for conference directory with ID "{0}", homed on the pool with distinguished ...
  19. An announcement with the same ID or name already exists. Create a new announcement with a unique ID or name and try again. ...
  20. An attempt to route to a gateway failed. Could not route to Gateway %1, the attempt failed with response code: %2 (CallID: ...
  21. An attempt to route to an Exchange UM server failed. The attempt failed with response code %1: %2. Request Target: %3], Call ...
  22. An attempt to send diagnostics information failed. Failure occurrences: %1, since %2. Failure Details: %3 Resolution: Check ...
  23. An attempt to use the following Exchange UM Server for a missed call notification succeeded: %1. Any previous errors have ...
  24. An attempt was made to add a user to a conference, but the conference has reached the maximum number of users permitted. ...
  25. An attempt was made to add a user to a conference, but the request was rejected because the user is already connected to ...
  26. An Enterprise Edition Front End Pool can contain as many as 10 computers for large scale deployments that require load balancing ...
  27. An error happened because the time zone of SQL Server Reporting Services (SSRS) is inconsistent with the time zone of the ...
  28. An error happened because the time zone of SQL Server Reporting Services (SSRS) is inconsistent with the time zone of the ...
  29. An error has occurred and the operation has been terminated. Please see the log to determine how to correct the failure and ...
  30. An error occurred because the time zone of SQL Server Reporting Services (SSRS) is inconsistent with the time zone of the ...
  31. An error occurred because the time zone of SQL Server Reporting Services (SSRS) is inconsistent with the time zone of the ...
  32. An error occurred during the installation of assembly '[6]'. One or more modules of the assembly could not be found. HRESULT: ...
  33. An error occurred during the installation of assembly '[6]'. Please refer to Help and Support for more information. HRESULT: ...
  34. An error occurred during the installation of assembly '[6]'. The assembly is not strongly named or is not signed with the ...
  35. An error occurred during the installation of assembly '[6]'. The signature or catalog could not be verified or is not valid. ...
  36. An error occurred when updating the file logging setting. Cause: The file logging setting is invalid. Resolution: Verify ...
  37. An error occurred when writing "{0}" to the configuration by calling Set-CSMonitoringServer. Verify network access, permission, ...
  38. An error occurred while applying security settings. 2 is not a valid user or group. This could be a problem with the package, ...
  39. An error occurred while attempting to connect to the following database. Server: '%1' Database: '%2' Error: '%3' Cause: There ...
  40. An error occurred while attempting to insert a report into the QoE Monitoring Server database. QoE Monitoring Server will ...
  41. An error occurred while attempting to insert a report into the QoE Monitoring Server database. Server: '%1' Database: '%2' ...
  42. An error occurred while attempting to send a message to the message queue. The message was dropped. Message queue path: '%1' ...
  43. An error occurred while reading from the message queue. Message queue path: '%1' Message queue error code: '%2' Cause: There ...
  44. An error occurred while reading from the message queue. Message queue path: '%1' Message queue error code: '%2' Cause: There ...
  45. An error occurred while writing installation information to disk. Check to make sure enough disk space is available, and ...
  46. An error was encountered when executing the stored procedure that logs errors to the back-end database. Execution Result: ...
  47. An exception caused the process to stop. Exception Details. %1 Cause: Check the eventlog description. Resolution: Examine ...
  48. An exception occurred during a regular expression replace operation. Rule name: %1 Rule pattern expression: %2 Rule translation ...
  49. An exception occurred during a regular expression replace operation. Rule name: %1 Rule pattern expression: %2 Rule translation ...
  50. An exception occurred during initialization of the Address Book Server. Exception: %1 Cause: Internal error. Resolution: ...
  51. An exception occurred during initialization of the Auto Update Server. Exception: %1 Cause: Internal error. Resolution: Examine ...
  52. An exception occurred during initialization of the Join Launcher Web Service. Exception Details. %1 Cause: Internal error. ...
  53. An exception occurred during initialization of the service. Exception: %1 Cause: Internal error. Resolution: Examine the ...
  54. An exception occurred during initialization of the Software Update Service. Exception: %1 Cause: Internal error. Resolution: ...
  55. An exception was detected that the platform was not expecting. This may be because of abnormal shutdown, lack of resources, ...
  56. An HTTP application request sent to a Service timed-out. Requests will be retried but if this error continues to occur functionality ...
  57. An installation for 2 is currently suspended. You must undo the changes made by that installation to continue. Do you want ...
  58. An installation package for the product 2 cannot be found. Try the installation again using a valid copy of the installation ...
  59. An invalid certificate was selected for TLS connections. Issuer: %1 Serial Number: %2 Cause: The selected certificate could ...
  60. An RPC call to deliver notifications to the target server failed. Target server: %1 Cause: Check if the target server specified ...
  61. An RPC call to deliver notifications to the target server failed. Target server: %1, Error Code: %2 Cause: The RPC server ...
  62. An unauthorized delegate operation was attempted. In the past %1 minutes the server received %2 unauthorized delegation operations. ...
  63. An unexpected error occurred when issuing an RPC request to the target server that is causing the service to fail. Target ...
  64. An unexpected error occurred when trying to fetch presence policies. This will be retried, but if this error continues to ...
  65. An unexpected error occurred when trying to open query. Verify that the file is valid and that you have permission to read ...
  66. An unexpected error occurred when trying to replicate conference directory data to the back-end. This will be retried, but ...
  67. An unexpected error occurred while processing a SIP message. Exception: '%1' Cause: An unexpected error occurred while the ...
  68. An unexpected exception occurred while loading configuration data and outbound calls may be affected. Exception: %1 Stack: ...
  69. An unhandled exception was encountered in %1 service. Exception Details. %2 Cause: Application error. Please look through ...
  70. An unhandled exception was encountered in Call Park Service. Exception: %1 Cause: Internal error in Call Park Service. Resolution: ...
  71. An unhandled exception was encountered in Certificate Provisioning Service. Message=%1 Cause: This is an unexpected error. ...
  72. An unhandled exception was encountered in Conferencing Announcement Service. Exception: %1 Cause: Internal error in Conferencing ...
  73. An unhandled exception was encountered in Conferencing Attendant. Exception: %1 Cause: Internal error in Conferencing Attendant. ...
  74. An unhandled exception was encountered in Response Group Service. Exception: %1 Cause: Internal error in Response Group Service. ...
  75. An unhandled exception was encountered in Routing Data Sync Agent. Message=%1 Cause: This is an unexpected error. Look through ...