Error when installing SSO 5.5 on the new Machine

I tried to install VMware vCenter Single Sign-On VMware-VIMSetup-all 5.5.0 - 5.5.0 - 1312299.iso, and like others, I have a problem. I want to install on a VM Windows Server Datacenter 2008 R2 SP1 64 bit new.

The first time I ran the installer, I display Single Sign-On prerequisite vCenter and realized that my network on the new machine settings were a bit off. So I canceled the installation program, fixed my network, started the Setup program again and this time I got the message "DNS resolution is effective."

Then I continued my way. I select "vCenter Single Sign-On for your first server vCenter Server", it starts to install, the State can "configure SSO components... "and then it shows" restoration of action: ", then"vCenter Single Sign-On the Setup Wizard ended prematurely because of an error. "All attempts to install later resulted in the same thing.

I've seen some solutions proposed elsewhere, and I've tried:

  • Rename C:\ProgramData\VMware\CIS to CIS.old
  • Run (VMware-VIMSetup-all-5.5.0-1312299.iso)\Single Sign-On\prerequisites\VMware-python.msi (tried right click menu: repair and also uninstall then install))
  • In 'HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc. \VMware Infrastructure', there is no SSOServer

I have attached vim-sso-msi and vminst.log of %TEMP%. I also found a vminst.log of a directory longer % TEMP %; I joined who as vminst - Temp.log too, in the case where it is useful.

Looking at newspapers, in vim-sso-MSI is towards the end:

MSI (c) (28:DC) [14:08:39:385]: Note: 1: 1708

MSI (c) (28:DC) [14:08:39:385]: product: vCenter Single Sign-On - Installation failed.

MSI (c) (28:DC) [14:08:39:385]: Windows Installer installed the product. Product name: vCenter Single Sign-On. Product version: 5.5.0.297. Product language: 1033. Manufacturer: VMware, Inc. installation success or error status: 1603.

It's the mid:

MSI (s) (38:A0) [14:07:41:006]: op of execution: ActionStart (Name = BootstrapAll),

Action 14:07:41: BootstrapAll.

MSI (s) (38:A0) [14:07:41:022]: op of execution: CustomActionSchedule(Action=BootstrapAll,ActionType=11265,Source=BinaryData,Target=***,CustomActionData=***)

MSI (s) (38:88) [14:07:41:037]: call for a custom action to distance. DLL: C:\Windows\Installer\MSI2A01.tmp, point of entry: VmSetupExecuteBootstrap

MSI (s) (C 38: 5) [14:07:41:037]: generation random cookie.

MSI (s) (C 38: 5) [14:07:41:053]: created server custom with PID 1724 (0x6BC) Action.

MSI (s) (38:FC) [14:07:41:178]: running as a service.

MSI (s) (38:FC) [14:07:41:193]: Hello, I am your server custom action high 64-bit.

Action 14:07:41: PostInstallScripts. Configuration of SSO components...

PostInstallScripts: PostInstallScripts

PostInstallScripts: PostInstallScripts

CustomAction BootstrapAll returned error code 1603 (note this is perhaps not 100% accurate if translation happened inside the bin to sand)

Action ended 14:08: InstallFinalize. Return value 3.

Vminst - Temp.log, I see this, but I don't know if it's relevant:

VMware Single Sign-on-build-1302472: 25/09/13 14:08 LDAP-Utils: VmSetupMakeLdapsConnection

VMware Single Sign-on-build-1302472: 25/09/13 14:08 ldap_sslinit attempt...

VMware Single Sign-on-build-1302472: 25/09/13 14:08 ldap_connect attempt...

VMware Single Sign-on-build-1302472: 25/09/13 14:08 ldap_bind_s attempt...

VMware Single Sign-on-build-1302472: 25/09/13 14:08 impossible to establish the LDAPS connection. Error: 1326

VMware Single Sign-on-build-1302472: 25/09/13 14:08 VmSetupUpdateVmdirCert error: 1603

VMware Single Sign-on-build-1302472: 25/09/13 14:08 VmSetupVmdirCert error: 1603

Folder is C:\Users\Administrator.MCI\AppData\Local\Temp\2

I got vminst - C:\Users\Administrator.MCI\AppData\Local\Temp Temp.log

Does anyone have any ideas on what I can try, or any other information that might help?

So I think that I just found out the real reason, it was a failure. In the above-mentioned documentation, they say that; "" "^-are not valid characters in a password. But they missed a character: space. I was using a space character in my password.

I tried on the setup of a bunch of times. When one of the invalid characters above is used, Setup will continue anyway. And then launching a 1326 in this another log file that I mentioned. Using a space does the same thing. And it's not as if they are not checking the password at all. If you do not meet the complexity requirements in their documentation, then you get this notice:

I don't know why they accept invalid characters in the installation program. And I don't know why they missed listing the space character as a character not valid in their documentation. It is an ASCII character, after all (0x20).

I tried a few other passwords a long time ago, but I think that was before found this documentation, so I used one of the other characters that are not valid. Or maybe I used another invalid character who is undocumented. If the space is not documented as an invalid character, so who knows how many other invalid characters are?

And so I say to all those who believe that they have the same problem I did:

First of all, make sure that it is the same problem. Check that you have found an error code 1326 in the other file vminst.log, located in a directory above %TEMP%. If you can't find a 1326, then you probably have a different problem.

Then, try other passwords. Do not use the documented invalid characters. And keep in mind that there may be other invalid characters without papers.

The password doesn't have to be the same as the password for the local Windows administrator account. Just, it cannot contain invalid characters without papers.

Tags: VMware

Similar Questions

Maybe you are looking for