Buongiorno,
dopo perdita da parte di VCSA 5.1 col NAS (per problemi al NAS), e dopo correzione degli errori al file system, il vCenter non è più funzionante, anzi lo "START" è grayed-out.
Tentando di ripristinare la situazione lanciando "Setup Wizard" (configure with default settings), la configurazioe del databse va a buon fine, mentre ricevo l'errore in oggetto per SSO. Ho cercato invano una soluzione, provato diversi workaround, ma nulla... Qualche idea?
Questo è l'errore completo di SSO:
Failed to execute '/usr/sbin/vpxd_servicecfg sso write embedded embedded CENSORED CENSORED':
VC_CFG_RESULT=721(Error: An unexpected error has ocurred during database operation. Please double check the database configuration)
Grazie.
Due to a NAS issue and the VCSA 5.1 consequent connection lost, vCenter is not working properly, indeed the "START" button is grayed-out.
To try solving the issue i launched "Setup Wizard" (configure with default settings), the DataBase configuration is ok, but i get the following error on SSO configuration:
Failed to execute '/usr/sbin/vpxd_servicecfg sso write embedded embedded CENSORED CENSORED':
VC_CFG_RESULT=721(Error: An unexpected error has ocurred during database operation. Please double check the database configuration)
I searched for and tried many workaround, but with no one i had success. Can you help me?
Thank you.
Primary problem here is FQDN under the IP settings
Check NTP on ESXi host correct
https://tinkertry.com/vcenter-server-appliance-5-5-in-a-home-lab-without-sso-errors
Hi and thanks for the link.
The ESX host is configured with the correct NTP server, VCSA is configured to "Synchronize guest time with host", i checked that both has the same date and time
Using WinSCP on VCSA I edited etc/hosts file as described, but launching the wizard i still get the same error during SSO configuration.
5.1 is very old now, only 6.5 and later are supported - not saying you must upgrade or that doing so would resolve your issue, but something to consider more generally...
Yes you are definitely right
I re-deployed from scratch VCSA 5.1 to solve the issue.