Lync Server 2013

  1. Failed %1 times when adding certificates to the server certificate store. Error %2. Resolution: Restart the server. If the ...
  2. Failed adding "{0}" permissions for "{1}" on "{2}". Access control list (ACL) might fail on UNIX file shares. Refer to the ...
  3. Failed applying User Replicator previously reported configuration change. Error: 1 Cause: Internal failure. Possible out ...
  4. Failed constructing and sending a message to the network. The failure may be due to network issues or invalid data from the ...
  5. Failed processing conference status requests. This error might delay the freeing up of PSTN meeting ids in conference directories ...
  6. Failed sending conference directory cleanup requests. This error will delay the freeing up of PSTN meeting ids in conference ...
  7. Failed sending conference status requests. This error might delay the freeing up of PSTN meeting ids in conference directories ...
  8. Failed starting a worker process. Process: '%1' Exit Code: %2!_HRX! (%3!_HRM!). Cause: This could happen due to low resource ...
  9. Failed starting the protocol stack. The service has to stop Error code is: 1 (%2). Cause: Check the previous entries in the ...
  10. Failed to achieve write quorum for some routing groups. Cause: This usually indicates that the Pool does not have enough ...
  11. Failed to add a domain to the list supported by SIP registrar in this Lync Server deployment. Domain: %1; Allow sub-domains: ...
  12. Failed to add a server to the known servers table. Server=[%1]. Site=[%2]. Role=[%3]. InstanceID=%4. Error=%5 (%6). Cause: ...
  13. Failed to clean up Central Management Store. The Central Management Service will not function as expected. Error Details: ...
  14. Failed to commit session data into the local Storage Service database. Error: %1 Cause: Storage Service or its dependent ...
  15. Failed to configure permissions for Kerberos account {0}. You may not have sufficient permissions to perform this operation. ...
  16. Failed to configure the roll back bit on exchange due to malformed response from Exchange. You can run the roll back cmdlet ...
  17. Failed to configure the roll back bit on Exchange. You can run the roll back cmdlet again to configure the roll back bit ...
  18. Failed to configure the roll back bit on Exchange. You can run the roll back cmdlet again to configure the roll back bit ...
  19. Failed to configure the roll back bit on Exchange. You can run the roll back cmdlet again to configure the roll back bit ...
  20. Failed to connect to back-end database. Lync Server will continuously attempt to reconnect to the back-end. While this condition ...
  21. Failed to connect to back-end database. Microsoft Lync Server 2013, File Transfer Agent will continuously attempt to reconnect ...
  22. Failed to connect to back-end database. Microsoft Lync Server 2013, Master Replicator Agent will continuously attempt to ...
  23. Failed to connect to back-end database. Microsoft Lync Server 2013, Replica Replicator Agent will continuously attempt to ...
  24. Failed to connect to back-end dynamic database. Lync Server will continuously attempt to reconnect to the back-end. When ...
  25. Failed to connect to LYSS database. Storage Service will continue to try to reconnect to the database. While this condition ...
  26. Failed to connect to Registrar. Stopping service. Check TLS certificate Issuer %1 SerialNumber %2, Registrar FQDN %3 Port ...
  27. Failed to connect to rtcprov database. Lync Online Provisioning Service will continue to try to reconnect to the database. ...
  28. Failed to create folder {0} in the mirror server {1}. Make sure that the account running the cmdlet has sufficient permission ...
  29. Failed to create Lync Server database. This could be due to lack of file system permissions for the SQL Server service account ...
  30. Failed to create the custom step because the constructor threw the following exception:"{0}". Verify that the application ...
  31. Failed to create topology watcher. This is usually due to SQL connection failure. Microsoft Lync Server 2013, File Transfer ...
  32. Failed to create topology watcher. This is usually due to SQL connection failure. Microsoft Lync Server 2013, Master Replicator ...
  33. Failed to deactivate machines from Fabric Pool Manager configuration. Machines: %1. Cause: Unable to connect to Fabric Pool ...
  34. Failed to enable user account control flags {0} and disable user account control flags {1} for account {2}. Kerberos authentication ...
  35. Failed to execute a stored procedure on the back-end. Component: %1 Stored Procedure: %2 Error: %3 Cause: Configuration issues, ...
  36. Failed to execute a stored procedure on the back-end. This has caused User Replicator to abort synchronization. Active Directory ...
  37. Failed to execute an sproc. This may indicate a possible configuration problem. Cause: Possible configuration problem. Resolution: ...
  38. Failed to execute CallNotificationEventsAddEvent sproc. Failed to execute CallNotificationEventsAddEvent store procedure. ...
  39. Failed to execute CallNotificationEventsGetEvents sproc. Failed to execute CallNotificationEventsGetEvents store procedure. ...
  40. Failed to execute stored procedure to ensure that routing group exists in the database. Routing Group: %1. Execution Error: ...
  41. Failed to execute the reconfigure command. Please ensure pending configuration changes are all resolved before installation ...
  42. Failed to execute the stored procedure DbSetMultipleConfigValue on the back-end. The global user settings were not updated ...
  43. Failed to find a matching Regular Expression to deduce base URL. This may indicate a possible configuration problem. Cause: ...
  44. Failed to find Web Conferencing Server specified by client Over the past %1 minutes Lync Server has disconnected client(s) ...
  45. Failed to flush data to backup store. Cause: This may indicate a problem with connectivity to local or backup database or ...
  46. Failed to get a connection to a domain controller %1 in domain %2 that User Replicator intended to synchronize. The error ...
  47. Failed to get a connection to a domain controller in domain %1 that User Replicator intended to synchronize. This prevents ...
  48. Failed to get a connection to a domain controller in domain %1 that User Replicator intended to synchronize. This prevents ...
  49. Failed to get data privacy boundary for naming context %1. The error that occurred was %2 (%3). Source of replication is: ...
  50. Failed to get information from the kernel mode driver. Driver Name: %1 Error code: %2 Cause: Driver is not responding in ...
  51. Failed to get pool state from local database. Execution Error: %1. Native Error: %2. Error Details: %3. Cause: This may indicate ...
  52. Failed to handle network interface changes. This can happen if no IP address is configured on the machine. Check whether ...
  53. Failed to initialize connection to the local configuration database. Microsoft Lync Server 2013, Replica Replicator Agent ...
  54. Failed to initialize Exchange Web Service Managed API (EWSMA). Storage Service requires EWSMA 15 to be installed and accessible ...
  55. Failed to initialize port(s) used by Storage Service. Storage Service requires to be able to listen for requests from other ...
  56. Failed to initialize the API subsystem. Cause: Review earlier events to determine the specific reason APIEM failed to initialize. ...
  57. Failed to initialize the focus adapter. Message:%1 Stacktrace: %2 Cause: Failed to initialize focus adapter Resolution: Check ...
  58. Failed to initialize the performance monitor counters. Performance counters will not be available. Exception: %1 Cause: Either ...
  59. Failed to initialize the replication service. This is usually due to incorrect configuration. Microsoft Lync Server 2013, ...
  60. Failed to initialize the replication web service. The listening port for %1 is set to %2. Configuration changes will not ...
  61. Failed to initialize the SIP manager Message: %1 Stack: %2 Cause: Failed to initialize the SIP manager Resolution: Look in ...
  62. Failed to initialize the SIP Manager Message: %1 Stack: %2 Resolution: Look in previous event logs for more information about ...
  63. Failed to initialize the transport layer. Message: %1 Cause: Failed to connect to Web Conferencing Edge Server. Resolution: ...
  64. Failed to initialize Windows Task Scheduler task for replication of certificates from the central management store to the ...
  65. Failed to insert QoE to back-end due to unexpected error. Component: %1 Error: %2 Cause: an unexpected condition has resulted ...
  66. Failed to launch Lync Server Client Version Filter application. Cause: Either the ClientVersionFilter.exe file is missing ...
  67. Failed to launch Lync Server Exchange Routing application. Cause: Either the ExumRouting.exe file is missing or it tried ...
  68. Failed to launch Lync Server Inbound Routing application. Cause: Either the InboundRouting.exe file is missing or it tried ...
  69. Failed to launch Lync Server Incoming Federation Application. Cause: Either the IncomingFederation.exe file is missing or ...
  70. Failed to launch Lync Server Intelligent Instant Message Filter application. Cause: Either the IIMFilter.exe file is missing ...
  71. Failed to launch Lync Server Inter Cluster Routing application. Cause: Either the InterClusterRouting.exe file is missing ...
  72. Failed to launch Lync Server Outbound Routing application. Cause: Either the OutboundRouting.exe file is missing or it tried ...
  73. Failed to launch Lync Server Outgoing Federation Application. Cause: Either the OutgoingFederation.exe file is missing or ...
  74. Failed to launch Lync Server Script-Only Applications Service process. Cause: Either the RTCSPL.EXE file is missing or it ...
  75. Failed to launch Lync Server Translation Service application. Cause: Either the TranslationService.exe file is missing or ...