Validate that each troubleshooting step below is true for your environment. Each step will provide instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.
- If the VMware SSO Server is restarted and the database resides on the same server, SSO may start before the database is available. If this is the issue, manually restart the service after the database is online. If manually restarting the service is not an option, move the database to a different server. Alternatively, in Windows 2008 and later, you can set the service to be a delayed startup service.
- Validate the network connection to the database server. If there is an intermittent or missing connectivity, log in may fail. To validate the connectivity, ping the database server from the vCenter SSO server. For more information, see Testing network connectivity with the ping command (1003486).
- Validate that the database login and passwords have not expired or have not been changed. To see the current database login details which SSO uses, run this command:
SSOInstallPath\utils\ssocli manage-secrets -a listallkeys
This command prompts you for the primary node password.
- Navigate to the SSOInstallPath\Logs directory and view the imsTrace.log, imsSystem.log and config.txt files for further troubleshooting information.
Note: If your problem still exists after trying the steps in this article:
-
-
File a support request with VMware Support and note this Knowledge Base article ID (2034517) in the problem description. For more information, see How to Submit a Support Request.