Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
vCenter Server login fails with error: A general system error occurred: Authorize Exception (1015639)
Symptoms
- vCenter Server services are running, but a user that was previously able to log into vCenter Server no longer can
- A local admin account is able to log in, but domain users cannot
- You see this error:
A general system error occurred: Authorize Exception
Cause
Resolution
- Review the local Administrators group on the vCenter Server host and ensure that your domain administrator AD group was added.
Note: If the Security ID (SID) is displayed and not the group name, this usually indicates that vCenter Server has lost its link to the domain controller.
- Remove vCenter Server from the Active Directory domain and re-add it.
Note: Before unjoining the vCenter Server from the domain, ensure that the local admin user has administrator rights to the vCenter Server, as this will remove all domain rights. You may also want to document all domain rights so you can re-apply them after you rejoin the domain. As a best practice, take a backup of the vCenter Server database prior to unjoining the domain.
- vCenter Server permissions are removed for domain users when vCenter Server is removed from the domain and re-added. To prevent this, follow these steps:
- Stop the vCenter Server service in Windows and set the Startup type to
Disabled. - Remove the vCenter Server from the domain.
- Reboot vCenter Server, and verify that the vCenter Server service is stopped.
- Add vCenter Server back into the domain.
- Restart vCenter Server and start the vCenter Server service.
- Set the Startup type of the vCenter Server service to
Automatic, and start the service.
- Stop the vCenter Server service in Windows and set the Startup type to
vCenter Server now accepts the domain user account credentials, and users are able to log in.
Note: Additionally, verify and ensure that the Identity Source is correct. For more information, see Configuring a vCenter Single Sign On Identity Source using LDAP with SSL (LDAPS) (2041378).
Additional Information
See Also
- After making a change or restarting Single Sign On server system, vCenter Server 5.1.x fails to start
- Configuring a vCenter Single Sign On Identity Source using LDAP with SSL (LDAPS)
Update History
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

