Hi,
I'm facing this error everytime on my vCenter 6.7:
I tried restarting the service, but everytime I logon again on vCenter it continues to show up.
Any advice?
This is Known Issues
Check if the following VMware KB article helps: VMware Knowledge Base
VMware vSphere Update Manager 6.7 Release Notes
Please consider marking this answer "correct" or "helpful" if you think your question have been answered correctly.
Did you provide the correct credentials to VUM to connect to vCenter (administrator@vsphere.local)?? Is this the vCSA or Windows installed??
Yes, the VUM works normally if I just restart the service.
It is vCSA.
This is the same vCenter after restarting the service:
This is Known Issues
Check if the following VMware KB article helps: VMware Knowledge Base
VMware vSphere Update Manager 6.7 Release Notes
Please consider marking this answer "correct" or "helpful" if you think your question have been answered correctly.
Thanks Diego!
Upgraded my VCSA 6.7 to 6.7d and still VUM is showing the same error, despite claiming it was fixed in 6.7c.
Anyone else experiencing the same?
Restart Update Manager does'nt work
Still Same Error
We have had this error for quite some time now. Of course we can upgrade vCenter, but for VUM only wasn't worth it. The KBs are wrong. The fixes don't work. We've tried it all. This thread should not be labeled as "Solved", but rather "Solved for some."
I'm sorry, but "SOLVED" is not valid.
It is the decision of the original poster to mark answers as correct or not, as their issue was resolved they chose to mark an answer.
Feel free to start your own thread or provide additional info so others may help you with an alternate solution.
Alright, makes sense. That "solved" pertained to this being the final solution, but in his particular case it was. Thanks.
The below solution helped me fix the issue
C:\Program Files\VMware\vCenter Server\bin\ service-control --stop vsphere-ui
service-control --start vsphere-ui
Credits to :
https://noesberger.info/authentication-failed-update-manager-server-could-not-be-contacted/
Thank you!