vCenter Single Sign on Installation Fails (Could not contact lookup service)

[Samson81]

I am trying to install the first vCenter server in our organization and it keeps failing with the error "Could not contact Lookup Service.  Please check VM_ssoreg.log in system temporary folder for details".  I checked the system temporary folder and there is no such file that is created but there was one called vminst.log.  In the file I found the following but I am unable to figure out how to resolve the problem:

VMware VirtualCenter-build-1123961: 08/07/13 08:40:03 Please see vm_ssoreg.log in system temporary folder

VMware VirtualCenter-build-1123961: 08/07/13 08:40:03 SSO registration tool failed with return code 2

VMware VirtualCenter-build-1123961: 08/07/13 08:40:03 Getting Property UILevel = 5

VMware VirtualCenter-build-1123961: 08/07/13 08:40:03 Getting Property ProductName = VMware vCenter Server

I am trying to install on Server 2008R2 STD 64 BIT, and have done the following to try a debug the problem:

1.  Server is part of Active Directory and the FQDN can be successfully resolved using nslookup.

2.  Server time is correct.

3.  Manually added the machine name to the host file

4.  Tried install using 5.1 Update 1b

Any help would be greatly appreciated.

[admin]

Hi,

This is an problem with FQDN  string

This issue is resolved in VMware vCenter Server 5.1.0 U1a released on October 25, 2012.

For more information see the VMware vCenter Server 5.1.0a Release Notes.

KB : VMware KB: Installing or upgrading vCenter Server 5.1 fails with the error: Could not contact Lookup...

[Samson81]

I believe that I am installing VMware vCenter Server 5.1.0a, the file that I downloaded for the install is,  VMware-VIMSetup-all-5.1.0-1123966.iso

[admin]

Try this work around

check the vcenter ip address is listed for hosts file go to the vcenter machine location below c:\windows\System32\drivers\etc\hosts and add the vc ipadress there eg: 192.168.0.20 virtualcenter.domain.com virtualcenter reboot the vcenter machine after the change and this will fix the issue.

If still issue, try the latest update VMware-VIMSetup-all-5.1.0-1235309.iso

Download VMware vCloud Suite

[Samson81]

Thanks for the help, it looks like adding the name to the hosts file fixed this for me.

[Samson81]

It looks like the issue is still happening, so far none of the suggestion have worked.   When I get to the vCenter Single Sign One Information page I still get the error "Could not contact Lookup Service.  Please check VM_ssoreg.log in system temporary folder for details".  Can someone please help?

[admin]

Did you try the update latest update VMware-VIMSetup-all-5.1.0-1235309.iso

Download VMware vCloud Suite...?

[Samson81]

Yes I tried using VMware-VIMSetup-all-5.1.0-1235309.iso and it still fails,  and also added the host name and IP address to the windows host file.  This is a fresh install and not an upgrade, am I missing something here? Bellow is the log file

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 admin@mydomain.ca

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 admin@System-Domain

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 vCenterServer_2013.08.08_092702

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 https://dellserver5.mydomain.ca:7444/lookupservice/sdk

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 C:\TEMP\2\{A4400513-2688-45A9-8439-CA991F4E4106}

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 C:\TEMP\2\

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 DELLSERVER5.wml.ca

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 C:\ProgramData\VMware\VMware VirtualCenter\SSL\

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 Fetched hidden property values

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 Getting Property SUPPORTDIR = C:\TEMP\2\{A4400513-2688-45A9-8439-CA991F4E4106}

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 Util_GetShortPath

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 Long path: C:\TEMP\2\{A4400~1\SSOREG~1 and crossponding Short path: C:\TEMP\2\{A4400~1\SSOREG~1

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 Executing following command (logging without password):

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 C:\TEMP\2\{A4400513-2688-45A9-8439-CA991F4E4106}\jre\bin\java.exe -Dlog4j.configuration="file:C:\TEMP\2\{A4400~1\SSOREG~1\log4j.xml" -cp "C:\TEMP\2\{A4400~1\SSOREG~1\/*" -jar "C:\TEMP\2\{A4400~1\SSOREG~1\regtool.jar" validateLsConnection -c "C:\TEMP\2\{A4400513-2688-45A9-8439-CA991F4E4106}\certs" -d https://dellserver5.mydomain.ca:7444/lookupservice/sdk -u "admin@mydomain.ca"

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 Launching without console output capture.

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 Util_Launch::Wait: 1 Hide: 1

VMware VirtualCenter-build-1235232: 08/08/13 09:31:42 Found "C:\TEMP\2\{A4400513-2688-45A9-8439-CA991F4E4106}\jre\bin\java.exe"

VMware VirtualCenter-build-1235232: 08/08/13 09:31:45 Process returned 2

VMware VirtualCenter-build-1235232: 08/08/13 09:31:45 Util_Launch::done Res: 1

VMware VirtualCenter-build-1235232: 08/08/13 09:31:45 Return code is 2 (successful operation however may not                    necessarily need return code 0.

VMware VirtualCenter-build-1235232: 08/08/13 09:31:45 SSO Registration tool launched

VMware VirtualCenter-build-1235232: 08/08/13 09:31:45 SSO registration tool failed with return code 2

VMware VirtualCenter-build-1235232: 08/08/13 09:31:45 Please see vm_ssoreg.log in system temporary folder

VMware VirtualCenter-build-1235232: 08/08/13 09:31:45 SSO registration tool failed with return code 2

VMware VirtualCenter-build-1235232: 08/08/13 09:31:45 Getting Property UILevel = 5

VMware VirtualCenter-build-1235232: 08/08/13 09:31:45 Getting Property ProductName = VMware vCenter Server

VMware VirtualCenter-build-1235232: 08/08/13 09:31:47 Returning from VMValidateLsConnection

VMware VirtualCenter-build-1235232: 08/08/13 09:31:47 End Logging

[admin]

Here is the action plan I recommend: - Try installing SSO first and then use inventory Service, vCenter and then web client. - Donot install using basic mode.

[Samson81]

I tried just installing vCenter Single Sign on and got "Error 20010. Failed to configure LookupService"

[Samson81]

So I think that have found the problem, it seems that having a backslash "\" in the vCenter Single Sign On password may have caused the issue

[admin · Accepted solution]

yes, that might be the Issue. non-ASCII characters, semicolon (;), double quotation mark ("), single quotation mark ('), circumflex (^), and backslash (\). are not supported in SSO passwords.

[VSRawat]

Use (.) as a special character in SSO password and in place of vcenter FQDN try to use IP Address.

[stoeffel2002]

Hi all,

I'm trying to upgrade my vSphere 5.0 environment to latest version of 5.1 (VMware-VIMSetup-all-5.1.0-1364042.iso). I installed SSO successfully. Now I would install Inventory Service but it fails with the error "Could not contact Lookup Service. Please check VM_ssoreg.log in system temporary folder for details". I can't find this log file is temporary folder.

I tried everything to work around this issue but nothing helps.

1. Entry in hosts file

2. Server has fixed IP address and is member of Active Directory Domain

3. I can resolve FQDN using nslookup

4. I use only letters and a minus sign in my password.

5. Server time is correct

Any help would be greatly appreciated.

Christoph

[MaheshBadge]

I was able to resolve this by doing a host entry and making sure DNS resolution is working.

Thanks

Mahesh

[mohsinabdul2312]

My error while installing vCenter Server was

registration with sso lookup service failed.check VM_ssoreg.login system temporary folder

What i did..

I uninstalled inventory service, uninstalled webclient ,uninstalled inventory service.

Installed them back again. Every thing was okay there after.