The problem has a couple of different solutions.
1. Upgrade to vSphere 5.x (vSphere 5.x stores snapshots on the datastore that contains the disk rather then the datastore that contains the VMs .vmx file. With vSphere 5.x vRanger is able to find all the snapshots info it is looking for and the issue is not seen.)
2. If you need to continue to use vSphere 4.x you will need to place all or most of the disks on the same datastore to remove the 3 or more same named disks. Once this is done this issue will go away.