Could not connect to a server in the pool. Failed to connect to a server in pool %1. Continue to retry. Cause: If the servers ...

Could not connect to a server in the pool.

Failed to connect to a server in pool %1. 
Continue to retry.
Cause: If the servers in the pool have been removed from the topology or are currently draining or is stopped, this behavior is expected; otherwise, a network issue may have prevented the connection.
Resolution:
If this behavior is unexpected, resolve the network issues between the two servers. Ensure that LS Bandwidth Policy Service (Core) is running on the servers in the pool.

Contact Object is not homed properly. Contact Object %1 is not homed properly. Error: 2. Cause: This could happen if the ... could be configured as a Director. You cannot home conference directories or users on a Director because it is not supported. ... Could not access update directory. Directory: %1 Cause: Expected directory does not exist. Resolution: Missing an expected ... Could not add an entry to the host authorization table. Attempt to add %1 to the host authorization table failed. Requests ... Could not connect to a server in the pool. Failed to connect to a server in pool %1. Continue to retry. Cause: If the servers ... Could not connect to Machine:"{0}"using WMI. This might be stale data in WMI data repository or Active Directory. Please ... Could not connect to server. Failed to connect to server FQDN %1 (%2:%3) Type %4 in pool %5. Continue to retry. Cause: If ... Could not create key: 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ... Could not create LookupUserWrapper. Cause: This is an unexpected error. If it happens even after following the resolution ...