A General System Error Ocurred
Contents |
occurred: Authorize Exception not helps. Symptoms (as from KB) vCenter Server services are running, but a user that was previously able to log into vCenter Server no longer can A http://adminotes.blogspot.com/2012/12/vsphere-general-system-error-occurred.html local admin account is able to log in, but domain users cannot You http://www.vclouds.nl/a-general-system-error-occurred-the-virtual-machine-could-not-start/ see this error:A general system error occurred: Authorize Exception Additionally Re-joining to domain don't help Your primary (and secondary) Domain Controllers which was used before were changed C:\Program Files\VMware\Infrastructure\SSOServer\webapps\ims\WEB-INF\classes\krb5.conf contains wrong kdc entries.NB: Don't try to edit this file. It's automatically generated. Cause Single-Sign-On service uses old DC name(s) when binds to a general Active Directory Resolution Install vSphere WebClient (don't forget that you should use admin@System-Domain username in order to connect it with SSO) Login to Web Client (https://vcenter.company.com:9443/vsphere-client/) using SSO admin account - admin@System-Domain On Administration page select Configuration menu under Sign-on and Discovery section Select the desired identity source (type - Active Directory), click Edit and write down (printscreen) all of the connection optionsWant to point out, a general system that in my case, changing server URLs has no effect - no changes was saved after OK was pressed, so... Remove old identity source and add a new one, with the same parameters, but with new server URLs Done Not important To be honest - it was the most interesting issue for last couple of month. Mostly because any other issue I faced was already solved by someone else, so any problem was solved by following the obvious scenario: Problem -> logs - > google -> solution. Now I have to switch on my imagination, because all solutions for "Authorize Exception" problem suggested to re-join to AD and/or fix AD/DNS problems. So we spent several hours fixing non-existing problems. Well, we knew that Domain Controllers were changed, but we forgot completely about SSO, and nobody knew/remember that SSO uses it's own configuration (based on MIT kreberos) in order to bind to AD. But even when the problem was located, I've spent next couple hours examining SSO logs and trying to find where AD discovery configuration can be changed. It's a pity, that it's not possible to configure by some CLI (at least I didn't find anything)
I was moving some VM’s from my Nexenta FC storage to my QNAP iSCSI storage to play around with the Nexenta VDEV pools. When I moved every VM I suddenly got this error: Checking all options, this drove me crazy for a little while… no shell or ssh was enabled on this host, and I did not feel like getting a screen and keyboard to check the vmkernel log… I totally forgot that a little while back I was playing around with swap file placement and placed the VM swap file on my ESX local storage. Since this disk and datastore is no longer available. The ESX host did not place it back to the default Virtual Machine directory. I changed this option to it’s default and all VM’s powered up again. Sometimes answers are so simple, and can mess up a beautiful day… Filed Under: VMware vSphere Tagged With: A general system error occurred, The virtual machine could not start About Marco BroekenMarco Broeken is Author of this blog and owner of vSpecialist Consulting and co-owner of XtraDesktop where he currently works as a Senior Virtualization Consultant. Marco has over 15 years experience in IT. Speak Your Mind Reactie annuleren Name * Email * Website Follow me on Twitter! The #vRockstar is happening this year! More info soon! Many thanks to our sponsors! :) https://t.co/bN758xgFPt https://t.co/2vhbDMXthP 21 september 2016 14:31Who got #vRockstar party pics from last year on their puter? let me know! 21 september 2016 10:35Verifying myself: I am mbroeken on Keybase.io. HUa8jNi0kmEcrPz2PAgF0Up8Hp4v_hXubH7j / https://t.co/tqbhNIOkNw 17 september 2016 22:33“@FrankDenneman: Looking forward to #vBeers tonight” +1 15 september 2016 10:41Soon more #vRockstar details will be unveiled.. https://t.co/XEJsV7SpqY 15 september 2016 10:41Used to buy @ProximalData AutoCache for $800 per ESXi host. @samsung has acquired the product, now it's is sold f