For some weird reason the customization specification wizard in VirtualCenter 2.5 fails when entering the administrator password. The error: An internal error occurred, and the wizard is unable to store the administrator password securely.
After reinstalling VirtualCenter the error still occurs. I googled the error and stumbled upon this VMware KB but this did not solve my problem…. I’m lost, anyone?
Markus Gehm says
Hi Duncan,
try to set a blank Admin password in the Template or VM you want to clone,
then it should work ๐
Duncan Epping says
It’s even before cloning or rolling out the template. it occurs when creating a customization specifation. so when you do -> edit -> customization specification -> new.
I tried a blank password, a complex etc… none works. I tried different accounts… no luck at all.
Markus Gehm says
Oh, sorry had a similar issue with the guest customisation wizard and there the password was it. I will try tomorrow on our system if the same error occures ๐
Clint Eschberger says
When you re-installed the VC and re-installed did you create a new customization or import the old one? I have seen where the import as issues with the admin password.
Duncan Epping says
I created a new one because it was a clean install at first, so i’ve never been able to create one.
Markus Gehm says
Ok tried at our VC and I have no Problems.
AC57846 says
I had the same issue after I replaced the default SSL certificates with new ones generated by my CA.
I suspect that the credentials in the customisation spec are encrypted using the SSL key & therefore cannot be decrypted using my new key.
I haven’t yet tried creating a new spec.
Al.
gert van gorp says
Hi,
Same issue here with Vcenter 4.0 Update 1.
We have 2 accounts (administrator and userx who are member of the local administrators group and have admin rights in VC.
When logged on with the administrator no problem, when logged on whit userx the error pops up
Created a new account userY and it works for this user. Looks like userX had profile problems
Greetings
Gert
Vijay says
we had also the same issue, running on VCenter 5.0 U2.