VM in VirtualCenter is in "invalid" state after VCB backup

[pearlyshells]

We have ESX3.5upd4 servers and VirtualCenter2.5Up4. We also use VizionCore's vRangerPro that utilizes VCB. Last night, vRangerPro performed its scheduled backup on a VM. However, something happened and the VC Events logs show that vRangerpro logged into the VM and performed several snapshots. the last entry shows that it created a 3rd snapshot and removed it and then VC lost communication with the VM. Now, I know that vRangerPro works in conjunction with VCB and our Backup Admin believes that the issue is not so much a vRangerPro problem but one with VCB. Regardless, i thought someone might have seen this with VCB or have an idea how to solve it. So, I hope I can get some help. Thanks

[galibai]

Not sure - Can you remove the VM from the VC and add it back ?

Thanks

[pearlyshells]

In fact, when I removed the Invalid VM from the inventory and recreated it ....all was well. Thanks very much. It appears the real problem was caused by vRangerPro backup. It created a snapshot but failed to release it.