Agent Offline error, but agent is not offline. (4034600)

BEHAVIOR

Backups fail with and a warning that a snapshot was skipped because the agent was offline in the Core UI.  You may encounter coincidental issues as described in A call to a remote server timed out.

CONDITIONS

This article describes a specific scenario in which the following conditions were true.  It is likely that the issue described below could occur under different but similar conditions, including other versions of AppAssure.

1. The Core server is installed with Windows Server 2012 R2.
2. The Core server is utilizing two or more Broadcom NICs in a team.
3. Team is created with BACS v16.3.4
4. Repository resides on internally attached disks.

In some scenarios NIC teaming may cause environmental performance degradation that is not noticed under normal operation.  This behavior may seem to be abnormal and easily dismissed as an AppAssure application problem.  However, investigation shows that the additional load that AppAssure places on the computer's resources merely exposes the condition that may otherwise go unnoticed.

Review and perform actions described in KB article A call to a remote server timed out.