Several problems can cause vCenter Single Sign-On to fail at start up or during initialization.

vCenter Single Sign-On fails either at start up or during initialization.

Startup or initialization failures occur in the following situations.

If your database server is on the same machine as vCenter Single Sign-On, in some cases restarting your machine might cause vCenter Single Sign-On to start before the database server is initialized.

If you use an external database server, it is possible that the database is not accessible.

If you use an external database server, the database server login password might have expired or been changed and not updated in vCenter Single Sign-On. Database log-in accounts do not expire using the embedded Microsoft SQL Server Express Database.

If vCenter Single Sign-On starts before the database server is initialized, manually restart vCenter Single Sign-On.

The database server must be accessible using the IP address or FQDN that you used when you installed vCenter Single Sign-On.

a

Find the properties file at SingleSignOn_Server\webapps\lookupservice\WEB-INF\classes\config.properties and confirm that the IP address or FQDN is correct.

b

Make any needed changes.

If your Single Sign-On uses an external Microsoft SQL Server database, and you use the dynamic port option, and you have a firewall between Single Sign-On and the external database, you must open a firewall port for the SQL Browser Service. The SQL Server Browser Service serves incoming requests for SQL Server connection by providing information about installed instances of SQL Server. The SQL Browser Service usually uses UDP port 1434. You must also add the SQL Server instance that you want to access through the firewall.

Verify that the database that vCenter Single Sign-On is configured for use.

a

At a command line, type SingleSignOn_server\utils\ssocli manage-secrets -a listallkeys

b

When prompted, type the master password.

c

To update the configuration, type ssocli configure-riat -a configure-db.