That vSphere SSO upgrade error - 1630

[stanj]

so, i thought the upgrade from 5.1 to 5.5 would be easy since we are not using Active Directory or HA, or DRS,,

Simple setup with one ESXi Server and 10 VMs.

I downloaded the 5.5 install pkg.

Tried the simple install first. i

It fails at the SSO install and rolls back.

I read many of the posting in the forum and have tried the suggestions including the mod to the registry for the IP.

Tried the Maual Install of SSO,,same thing..below is part of the log file..

Property(S): ProductToBeRegistered = 1

MSI (c) (70:FC) [08:25:32:031]: Back from server. Return value: 1603

MSI (c) (70:FC) [08:25:32:031]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (c) (70:FC) [08:25:32:031]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'.

Action ended 8:25:32: ExecuteAction. Return value 3.

MSI (c) (70:FC) [08:25:32:031]: Doing action: FatalError

Action 8:25:32: FatalError.

Action start 8:25:32: FatalError.

Action 8:25:32: FatalError. Dialog created

MSI (c) (70:CC) [08:25:34:558]: Doing action: ShowMsiLog

Action 8:25:34: ShowMsiLog.

Action start 8:25:34: ShowMsiLog.

MSI (c) (70:5C) [08:25:34:573]: Invoking remote custom action. DLL: C:\Users\ADMINI~1\AppData\Local\Temp\1\MSI7E0F.tmp, Entrypoint: WixShellExec

MSI (c) (70:C4) [08:25:34:573]: Cloaking enabled.

MSI (c) (70:C4) [08:25:34:573]: Attempting to enable all disabled privileges before calling Install on Server

MSI (c) (70:C4) [08:25:34:573]: Connected to service for CA interface.

I also see there is a new vSPhere 5.5.0a version available.

Suggestions are it may solve the issue?

any ideas/comments

thanks

[raog]

Fixed as per 5.5.a release notes:

https://www.vmware.com/support/vsphere5/doc/vsphere-vcenter-server-550a-release-notes.html

Regards

Girish

[john23]

I would recommend better try with 5.5a build.  Workaround may or may not solve the issues

[stanj]

I checked the release notes and the 1603 error shown is not similar to the one I am, seeing (as shown in lines from the log in my posting).

I had to revert back to 5.1.

At me point, will try the5.5 upgrade again.  Worst case is to build a new vcenter since this is a small dev environment.

[john23]

5.1 SSO has lot of workaround (lot of kbs) ...If you can built 5.5 new setup with existing db may help.. this is my personal prospective...