I've seen similar behavior before, but cannot remember the KB I used to resolve; however, the recommended solution was a reboot of connection servers and vCenter. Not sure this is the same issue and I noticed you mentioned you rebooted vCenter and bounced services, but wasn't sure if you rebooted your connection servers.
↧
