VMware SSO on W2K8 an 29114 error

VMware SSO on W2K8 an 29114 error

Regarding VMware KB 2035454 IPv6 can lead to an error 29114 while installing VMware SSO. A database connection could not be established. They suggest to use the FQDN of the host, what I did. But it still failed.

In my installation Windows 2008 R2 Standard is used.

Looking into the "install.log" file under "c:\program files\vmware\infrastructure\ssoserver\utlils\log" I found a message that the reverse lookup of the IPv6 address of the vCenter and database host could not be resolved. I checked DNS and found a IPv6 address for that host. That was returned to the DNS query performed by the installtion. So it failed.

You need not only to disable IPv6 at the interface level but also all components of it. Check Microsoft KB 929852 (http://support.microsoft.com/kb/929852/en-us) on how to do that:

You need to create a 23 Bit DWOR value under "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters" called "DisabledComponents".

Depending on the value of that key, you can achieve the following:

0  to enable all IPv6 components

  • 0xffffffff   to  disable all IPv6 components except the IPv6 loopback interface.  This  value also configures Windows to prefer using IPv4 over IPv6.
  • 0x20  to prefer IPv4 over IPv6 by changing entries in the prefix policy table.
  • 0x10  to disable IPv6 on all nontunnel interfaces (both LAN and Point-to-Point Protocol [PPP] interfaces).
  • 0x01   to disable IPv6 on all tunnel interfaces.
  • 0x11  to disable all IPv6 interfaces except for the IPv6 loopback interface.

I used 0 to disable it completely and the installation worked.

Comments

we are havinv the same issue but this didnt work for us:smileyplain:

Yeah, you can find my resolution here:

http://communities.vmware.com/thread/432069

It turns out it was the freaking SQL Query script used to build the SSO DB. Smiley Happy

I was also getting a Connection Error, but it actually had nothing to do with the actual connection but rather the inability to use the DB but it spits out "connection error" likewise. 

Version history
Revision #:
1 of 1
Last update:
‎09-20-2012 05:53 AM
Updated by:
Immortal