There are two workarounds:
1. Remove host credentials for the ESX 4.1 host from vRanger so it does not use COS backup, but rather runs as a VDDK backup.
2. Disable ABM for the backup job of the VM receiving the error.