Quantcast
Channel: VMware Communities: Message List - vSphere Upgrade & Install
Viewing all articles
Browse latest Browse all 11859

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

$
0
0

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


Viewing all articles
Browse latest Browse all 11859

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>