Failed to get a connection to a domain controller %1 in domain %2 that User Replicator intended to synchronize. The error that occurred was %3 (%4). The source of the replication is %5. Cause: The most common cause of this error is that the domain controller is down. Resolution: The domain controller User Replicator is attempting to connect to is intended to be enabled for Lync Server, then determine why the account User Replicator is running under cannot access the domain controller. Otherwise, this error can be ignored.
Failed to execute the stored procedure DbSetMultipleConfigValue on the back-end. The global user settings were not updated ...
Failed to find a matching Regular Expression to deduce base URL. This may indicate a possible configuration problem. Cause: ...
Failed to find Web Conferencing Server specified by client Over the past %1 minutes Lync Server has disconnected client(s) ...
Failed to flush data to backup store. Cause: This may indicate a problem with connectivity to local or backup database or ...
Failed to get a connection to a domain controller %1 in domain %2 that User Replicator intended to synchronize. The error ...
Failed to get a connection to a domain controller in domain %1 that User Replicator intended to synchronize. This prevents ...
Failed to get a connection to a domain controller in domain %1 that User Replicator intended to synchronize. This prevents ...
Failed to get data privacy boundary for naming context %1. The error that occurred was %2 (%3). Source of replication is: ...
Failed to get information from the kernel mode driver. Driver Name: %1 Error code: %2 Cause: Driver is not responding in ...