SSO 5.5 upgrade fails

[theissenbuettel]

I wanted to update our vCenter Server in the test lab to 5.5 and it's failing at the very beginning, at SSO upgrade. The update starts and after a short while it begins to rollback actions.

After digging into the logs, the only thing i found is one error inside the vminst.log, inside the "Import tool" block:

VMware Single Sign-On-build-1302472: 09/23/13 11:26:30 Entering VmSetupImportLookupServiceData
VMware Single Sign-On-build-1302472: 09/23/13 11:26:30 Entering function: VmSetupGetFQDNOrIP
VMware Single Sign-On-build-1302472: 09/23/13 11:26:30 Entering function: VmSetupGetFQDNOrIPFromRegistry
VMware Single Sign-On-build-1302472: 09/23/13 11:26:30 Leaving VmSetupGetFQDNOrIPFromRegistry, Error: 0
VMware Single Sign-On-build-1302472: 09/23/13 11:26:30 Leaving VmSetupGetFQDNOrIP, Error: 0
VMware Single Sign-On-build-1302472: 09/23/13 11:26:30 Launching ssolscli from C:\Users\THEISS~1\AppData\Local\Temp\\exported_sso.properties
endpointUrl is created:https://FQDN:7444/sso-adminserver/sdk
endpointUrl is created:https://FQDN:7444/ims/STSService?wsdl
endpointUrl is created:https://FQDN:7444/sso-adminserver/sdk
endpointUrl is created:https://FQDN:443/sdk
endpointUrl is created:https://FQDN:12443/vmwb/logbrowser
endpointUrl is created:https://FQDN:12443/authentication/authtoken
endpointUrl is created:https://FQDN:9443/vsphere-client
Intializing registration provider...
Getting SSL certificates for https://:7444/lookupservice/sdk
Host name may not be null
Return code is: InvalidInput
-2

Seems there's some config value missing, regarding the FQDN for the lookupservice, but i'm grepping like wild inside %Program Files%\VMware\Infrastructure\SSOServer\ and its subfolders, but i don't find any line which could help.

[SJVMW]

Please upload the logs (vminst.log and vim-sso-mis.log.) from %Temp%.

What is the version of SSO: 5.1P01, 5.1U1a before the upgrade?

Thanks.

[theissenbuettel]

I cannot give you the exact version, but i upgraded the whole system to  5.1U1a recently.

The corresponding log files were attached. I had to search and replace some corporate Information, including domain names and host names. FQDN is the FQDN of the vCenter/SSO server, DOMAIN is the domain name and HOSTNAME is the host name of the vCenter/SSO server.

Thanks for your efforts so far.

[admin]

Could you please check the registry key at HKEY_LOCAL_MACHINE\Software\VMware, Inc.\VMware Infrastructure\SSOServer\FQDNIp, is it showing ip address or FQDN? Please attach a screenshot of registry key and SSO certificate if you can. To find the certificate, you can run http://<FQDN or ip, depend on the registry above>:7444/lookupservice/sdk

[dcolpitts · Accepted solution]

Did you see this article yet:  VMware KB: vSphere 5.5 Single Sign-On upgrade rolls back after importing Lookup Service data

Message was edited by: Dean Colpitts to fix a typo

[Precht]

dcolpitts,

Great find.  This makes me feel a lot better. I hope vmware gets it resolved soon.

[admin]

The KB has been updated with the resolution. Please check the latest KB and let us know if this solves your problem.

[Precht]

Unfortunately the KB resolution did not fix it.

I followed every single step. I'm not sure what's going on. I'd like to upgrade to 5.5, but I think VMware needs to re-evaluate the upgrade process.

[admin]

Could you please upload the SSL certificate, SSOServer FqdnIP registry screenshot as well as the latest retried log file (viminst.log and vim-sso-msi.log and viminst.err etc) under %temp% folder? In addition, assuming, you have renamed or removed the previous leftover CIS folder before the latest try, correct?

[theissenbuettel]

As for me the registry key HKEY_LOCAL_MACHINE\Software\VMware, Inc.\VMware Infrastructure\SSOServer\FQDNIp was empty. I populated the SubjectName of the SSL certificate and the update went flawless. I do have issues with the Web Client update for now, but i will check it myself or open another thread for that.

Thanks for your efforts.

[admin]

Good to know after you fill the registry key for FqdnIp (from empty value to FQDN value which matches the value at the SSL certificate), the update/upgrade went thru for you. Thanks for your patient with us. Please let us know any further help you need.

[Precht]

I was able to resolve my problem.

If you tried to install the upgrade and failed you will need to revert back to a state before the upgrade and try the upgrade progress following the KB.

Initially, my upgrade failed because my fqdnip was set to the IP address and it did not match the self signed SSL cert.  I followed the steps the KB and it kept failing.  So I decided to revert the SSO vm to a snapshot prior to the upgrade.  Before the upgrade I changed the fqdnip and tried the upgrade again and it worked.

Thanks for everyone's help.

[contres]

Updating the registry key, before starting the upgrade worked for me as well.