Failover process has encountered an error Pool %1 could not be successfully failed over to pool %2 Cause: Possible issue with local or shared backup database. Resolution: Please consult server event logs to identify the problem. Run the failover process again after fixing any reported issue.
Failed updating the Conference Auto Attendant configuration. Conferencing on this Pool can continue, but Conference Auto ...
Failed when trying to access or modify registry on machine {0}. Please ensure that you have permissions to modify the registry ...
Failed while retrying the naming context %1. The source of the replication is %2. Resolution: We will retry again later. ...
Failover Central Management services from pool "{0}" using the Invoke-CsManagementServerFailover cmdlet before performing ...
Failover process has encountered an error Pool %1 could not be successfully failed over to pool %2 Cause: Possible issue ...
Fatal error reported for a routing service. Routing Group: %1. Error Code: %2 Cause: This error is unexpected. Please examine ...
fatal|error|warn|info|verbose|noise): least severe log level to search on. For example, if 'warn' is specified search will ...
Federation is the ability to establish communications between your organization and one or more external organizations, including ...
File transfer experienced a timeout. Microsoft Lync Server 2013, File Transfer Agent will continuously attempt to transfer ...