Hello,
Those lines are the guest processing connection sequence working. The
guest interaction proxy tries to deploy runtime components, then a guest agent connection, then VIX. In your screenshot one of the methods did connect, and every step after it, from inventory to the VM snapshot, succeeded. The task only turns to warning or error when the whole sequence is exhausted.
To see which step fails, open the Guest Processing step in the job settings, select the guest OS credentials and click
Test Now. The tester walks the same connection methods against the selected VMs and shows the error behind each one.
KB3225 describes common issues with that.
I'd also suggest to check this registry key
InverseVssProtocolOrder on the backup server. It makes the job try VIX first and fall back to the network methods only when VIX fails. It applies to every job on that backup server. May be this is set.
If you believe there is still an issue please open a support case and attach all the logs.