1 person found this helpful
Seems like the VIN integration is not working for you, for some reason.
hence you don't see the Application group
The most common problem with that error is due to DNS resolution. check that your vCenter can be accessed by both IP and hostname from vc ops (both VMs)
I was able to resolve fqdns all around...that is from the VIN to the vCenter...also just for fun I logged in to our vCops vms (UI and analytics) and also was able to resolve all fqdns from all vms.
the full connection from vcops to both VIN and VC is what's important here.
any other errors above/below those few lines you have posted?
Went back to review and found the very last entry in the VinAdapter.log is the one posted above...no subsequent entries...I am about ready to scrap this whole mess and start fresh I think! Just found I have additiona VIN issues...seems VIN is no longer able to authenticate to most of the vms in our environment...so I am not sure how this lack of connectivity between vCops and most of the vms relate.
I did find out we have S&S support until the end of September so opened a case for the authenticaton issue between VIN and our vms...I will also add this to the request when I speak wit the TSE.