Today a customer called me because they were unable to login to their VMware vCenter using domain accounts.
They saw the following error message:
A general system error occurred: Authorize Exception
I asked if they had made any changes and they had created two new Windows Server 2012 domain controllers and given them the IP adresses of their old Windows Server 2003 domain controllers.
I searched the VMware Knowledgebase and found the following article:
vCenter Server login fails with error: A general system error occurred: Authorize Exception.
Unfortunately de-joining the vCenter server from active directory and re-joining the vCenter server to active directory did not help.
My next troubleshooting step was to logon to the webclient using the admin@System-domain account:Â https://vcenter.domain.local:9443/vsphere-client/
Then Configuration (under Sign-On and Discovery):
I then clicked on the active directory connection, removed it and created a new connection.
Here is an example configuration:
This solved the issue and the customer was now again able to login using their domain accounts.
As always, if this helped you please leave a comment 🙂
Incoming search terms:
- a general system error occurred authorize exception
- vmware a general system error occurred authorize exception
- a general system error occurred: authorize exception
- vcenter authorize exception
- vsphere client authorize exception
- vsphere client a general system error occurred authorize exception
Had the same problem last week when the customer updated their Active Directory. I removed the AD connection and then added the same details again which solved the problem. Did you change the Primary and Secondary server URLs or did you reuse the old once?
Thank you for commenting magander!
I did not re-use the old information as this pointed to their (still available) Windows Server 2003 domain controllers.
Instead I inputted the information for their new Windows Server 2012 domain controllers.
The rest of the information I re-used.
This helped me too! Having the same issue, replaced old DCs with new Server 2012 and resetting them in the Web client fixed the issue. Thanks!
Thank you for taking time to comment Justis 🙂
Thanks for this, worked a treat for me 🙂