A General System Error Occurred Authorize Exception
Contents |
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vCenter™ > VMware vCenter™ Server > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 1 2 Previous Next 15 Replies Latest reply: Jul 9, 2013 8:22 AM by ff0rtier Cannot login to VCENTER a general system error occurred timed waiting for vpxa to start using domain credentials, authorize exception manavsood Dec 14, 2012 4:04 AM Hi Guys,I am a general system error occurred authorize exception vcenter running vcenter version 5.1 and my esxi servers are also 5.1.Now, obviously the vcenter server is joined to the domain.As we are a general system error occurred authorize exception vmware upgrading the entire infrastructure, the old DC must be decommissioned and hence it is currently shut-down. All FSMO roles etc. have been transferred to the new DC and also the new DC is acting as
A General System Error Occurred Authorize Exception Vcenter Appliance
DNS/DHCP server for the entire network.We have got 50 PCs running in the network along with exchange server etc. and so far no signs of any glitches anywhere elseNow the issue I am having is that as soon as I shutdown the old DC, I can no longer access the VCENTER server using domain credentials. When I turn it on I can login fine.The error I receive when I can't a general system error occurred protocol error from vmx login - 1. A general system error occured: Authorize Exception or2. Access to VCENTER server was denied.3. Taking too long to respond.I followed the steps here http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015639 i.e. unjoined vcenter server from domain and rejoined to domain whilst having old DC shutdown as well as turned on but absolutely no luck.I can still log into VCENTER server using local admin login and password but teh issue is that my VEEAM backup is failing as well. It says "Task failed Error: Cannot complete login due to an incorrect user name or password." which is the whole reason I discovered this issue was related to VCENTER login via Vsphere client.Kindly help 46966Views Tags: none (add) serverContent tagged with server, issuesContent tagged with issues, loginContent tagged with login, domainContent tagged with domain, exceptionContent tagged with exception, controllerContent tagged with controller, vcenterContent tagged with vcenter, authorizeContent tagged with authorize This content has been marked as final. Show 15 replies 1. Re: Cannot login to VCENTER using domain credentials, authorize exception spravtek Dec 14, 2012 4:22 AM (in response to manavsood) Maybe this: http://adminotes.blogspot.be/2012/12/vsphere-general-system-error-occurred.htmlCan help you along ... Seems they had the same issue regarding an old DC...Though maybe you've tried all these things already. Like Show 1 Like (1) Actions 2. Re: Cannot
vmware, vSphere 5.1Jonathan Medd Experienced this issue a month or so back (ended up logging a call with VMware to get confirmation of what happened) and it occurred again today so figured it was worth posting about. If you receive the http://www.jonathanmedd.net/2013/09/vcenter-5-1-sso-a-general-system-error-occurred-authorize-exception.html following error when attempting to log into vCenter 5.1 with an AD account: A general system error occurred: Authorize Exception there are a number of potential issues. however most likely it is related to SSO and one of the Identity Sources. Some of the issues that weren't a problem for me (among many reported on the Interwebs), but I checked out first were: vCenter Server login fails with the error: A general a general system error occurred: Authorize Exception vSphere: A general system error occurred: Authorize Exception Unable to login to VMware vCenter with domain accounts: A general system error occurred: Authorize Exception Typically they involve issues with AD DCs being replaced, vCenter computer account problems or re-creating an Identity Source. In my case none of the above really applied and the Identity Source appeared to check out OK: A restart of the vCenter SSO service a general system brought things back to life. Looking into it a bit deeper and after filing an SR with VMware they pointed me at this KB having discovered many of the below in the ssoAdminServer.log file. Error connecting to the identity source……..No ManagedConnections available within configured blocking timeout……. The symptoms in the KB also tied in with some scenarios around vCenter aware backup failures which had occurred during this time. As per the KB a restart of the vCenter SSO service refreshes the LDAP Connection Pool. The engineer at the time informed me that it would be fixed in vSphere 5.5 and the KB now confirms this is the case, however no indication of whether it would be back-ported to 5.1. I haven't yet been foolhardy brave enough to attempt upgrading a production SSO deployment to vSphere 5.5 to confirm if the fix resolves the issue we have seen. Post navigation ← Storage vMotion Fails with VM Hardware Version 4 Automating the Pre-Requisites for vCAC 5.2 → One thought on “vCenter 5.1 SSO: A General System Error Occurred: Authorize Exception” PEYMAN says: June 7, 2015 at 7:46 am hi first of all u must install the vmware certificate on your computer. Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment