masselwagen
Contributor
Contributor

Setup cannot create vCenter Server Directory Services instance

during upgrade from VC 3 to VC 4 i've got error message (see attach pic 1), after click on 'Yes' second message appear and then install process rollbackin'

what's wrong?

log's file don't make things clear

[2009-05-22 09:35:03] INFO JoinTool started

[2009-05-22 09:35:03] INFO Storage directory for LDAP instance: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS

[2009-05-22 09:35:03] INFO Operation Mode: initialize

[2009-05-22 09:35:03] SEVERE Failed to load certificate: : Failed to load certificate

[2009-05-22 09:35:03] SEVERE Execution error.

VMware VirtualCenter-build-162856: 05/22/09 09:12:33 --- CA exec: VMAdamInvokeJoinTool

VMware VirtualCenter-build-162856: 05/22/09 09:12:33 Jointool command: ["C:\Program Files\VMware\Infrastructure\jre\bin\javaw.exe" -jar "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jointool.jar" init --statusFile "C:\DOCUME~1\a-mic\LOCALS~1\Temp\2\status.txt" --recoverIfPossible --name VIM01.domain.com --vimURL https://VIM01.domain.com:443/sdk --webServiceURL https://VIM01.domain.com:8443/vws --ldapPort 389 --dsn "VMware VirtualCenter" --dbUser "" --dbPassword "***********"]

VMware VirtualCenter-build-162856: 05/22/09 09:12:33 Deleting

VMware VirtualCenter-build-162856: 05/22/09 09:12:33 Did not find file/directory: ""

VMware VirtualCenter-build-162856: 05/22/09 09:12:33 Already removed:

VMware VirtualCenter-build-162856: 05/22/09 09:12:33 Deleting C:\DOCUME1\a-mic\LOCALS1\Temp\2\status.txt

VMware VirtualCenter-build-162856: 05/22/09 09:12:33 Found "C:\DOCUME1\a-mic\LOCALS1\Temp\2\status.txt"

VMware VirtualCenter-build-162856: 05/22/09 09:12:33 Deleted file C:\DOCUME1\a-mic\LOCALS1\Temp\2\status.txt

VMware VirtualCenter-build-162856: 05/22/09 09:12:33 Found "C:\Program Files\VMware\Infrastructure\jre\bin\javaw.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:12:38 Process returned 255

VMware VirtualCenter-build-162856: 05/22/09 09:12:38 status.txt file size: 161

VMware VirtualCenter-build-162856: 05/22/09 09:12:38 linked mode operation failed with error [255]. Join Mode = [init] Join Error ID = [28038]

VMware VirtualCenter-build-162856: 05/22/09 09:12:38 Posting user message 28042

VMware VirtualCenter-build-162856: 05/22/09 09:35:03 MsiProcessMessage returned: 6

VMware VirtualCenter-build-162856: 05/22/09 09:35:03 PerformJoinOperation() -- HandleJoinToolResults returned <1603>

VMware VirtualCenter-build-162856: 05/22/09 09:35:03 Found "C:\Program Files\VMware\Infrastructure\jre\bin\javaw.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:35:03 Process returned 255

VMware VirtualCenter-build-162856: 05/22/09 09:35:03 Jointool invoked with --force option

-----------------

Failed to load certificate:

com.vmware.vim.common.ssl.CertificateLoadException: Failed to load certificate

-----------------

Execution error.

0 Kudos
56 Replies
masselwagen
Contributor
Contributor

hmm... it looks like troubles was with manually generated certificate. problem solved by replacing it with default SSL certificate

0 Kudos
masselwagen
Contributor
Contributor

Smiley Happy

0 Kudos
jreininger
Enthusiast
Enthusiast

I am getting the same errors in a lab envirotment.

In this case I was doing a fresh install of the vShepre VC software, it was not an upgrade.

and, the VC server is being install under workstation on a 2k3 sp1 vm (installing sp2 now, not really sure what to look for you w/ this software)

and, I had a my old AD DC on workstation, then P2V'd w/ coldclone iso boot CD to my ESX 3.5 U4 host

I did this because I could not install vSphere4 VC server on a DC (in my test lab I was OK w/ VC 2.5U4 doing that)..

Update.. OK I was lazy.. Once SP2 installed I got a different error that said 'hey your a member of a domain, but we cant find a DC.. Updated NIC card DNS settings to point to the DC that I P2V'd to my host..

MORAL of story, even in a 'test / home lab' dont be lazy or in a hurry and make sure your DNS is setup correctly . You cant count on broadcasts for name resolutions. I am guessing it must have needed access to the SRV records of the DC (??) or because the VM I was setting up the VC was set for DHCP and name requests were going to the default gateway frist it just didnt work. I was assuming it would just broadcast out for the DCs mac/address. But the error was unclear w/o SP2 being installed..

Hope this helps somebody that was also in a hurry to play w/ the new software..

Thanks..

my error logs:

-


file = jointool-0.log

2009-05-22 09:23:42 INFO JoinTool started

2009-05-22 09:23:42 INFO Storage directory for LDAP instance: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS

2009-05-22 09:23:42 INFO Operation Mode: initialize

2009-05-22 09:23:42 INFO Creating directory services instance VMwareVCMSDS

2009-05-22 09:23:42 INFO LDAP port = 389

2009-05-22 09:23:42 INFO Base DN = dc=virtualcenter,dc=vmware,dc=int

2009-05-22 09:23:42 INFO Storage dir = C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS

2009-05-22 09:24:02 INFO Creation complete

2009-05-22 09:24:02 INFO Resetting VC LDAP service SSL port

2009-05-22 09:24:03 INFO Service 'VMwareVCMSDS' is running

2009-05-22 09:24:05 INFO STOP_SERVICE of 'VMwareVCMSDS' successful

2009-05-22 09:24:10 INFO START_SERVICE of 'VMwareVCMSDS' successful

2009-05-22 09:24:10 INFO Importing "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\ldif\vc_schema.ldf". Host: 127.0.0.1; Port: 389

2009-05-22 09:24:25 INFO Importing LDIF on 127.0.0.1 failed with Action: LDIF Import

Action: Process execution

Problem: Import LDIF failed: 8251. Output: Connecting to "127.0.0.1"

Logging in as current user using SSPI

SSPI "bind as current user" returned 'Local Error'

No log files were written. In order to generate a log file, please

specify the log file path via the -j option

Possibly pure IPV6 machine.

Attempting to import LDIF to ::1

2009-05-22 09:24:25 INFO Importing "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\ldif\vc_schema.ldf". Host: ::1; Port: 389

2009-05-22 09:24:25 SEVERE Operation "Create standalone instance VMwareVCMSDS" failed: : Action: Create Standalone Instance

Action: Creation of standalone instance

Action: LDIF Import

Action: Process execution

Problem: Import LDIF failed: 8224. Output: Connecting to "::1"

The connection cannot be established

The error code is 8224

No log files were written. In order to generate a log file, please

specify the log file path via the -j option.

2009-05-22 09:24:25 SEVERE Recovering from failed Operation "Create standalone instance VMwareVCMSDS"

2009-05-22 09:24:25 INFO Removing directory services instance VMwareVCMSDS

2009-05-22 09:24:27 INFO Removal complete

2009-05-22 09:24:27 SEVERE Recovery successful

2009-05-22 09:24:27 SEVERE Execution error.

2009-05-22 09:24:41 INFO JoinTool started

2009-05-22 09:24:41 INFO Storage directory for LDAP instance: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS

2009-05-22 09:24:41 INFO Operation Mode: initialize

2009-05-22 09:24:41 INFO Creating directory services instance VMwareVCMSDS

2009-05-22 09:24:41 INFO LDAP port = 389

2009-05-22 09:24:41 INFO Base DN = dc=virtualcenter,dc=vmware,dc=int

2009-05-22 09:24:41 INFO Storage dir = C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS

2009-05-22 09:24:50 INFO Creation complete

2009-05-22 09:24:50 INFO Resetting VC LDAP service SSL port

2009-05-22 09:24:50 INFO Service 'VMwareVCMSDS' is running

2009-05-22 09:24:52 INFO STOP_SERVICE of 'VMwareVCMSDS' successful

2009-05-22 09:24:54 INFO START_SERVICE of 'VMwareVCMSDS' successful

2009-05-22 09:24:54 INFO Importing "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\ldif\vc_schema.ldf". Host: 127.0.0.1; Port: 389

2009-05-22 09:25:09 INFO Importing LDIF on 127.0.0.1 failed with Action: LDIF Import

Action: Process execution

Problem: Import LDIF failed: 8251. Output: Connecting to "127.0.0.1"

Logging in as current user using SSPI

SSPI "bind as current user" returned 'Local Error'

No log files were written. In order to generate a log file, please

specify the log file path via the -j option.

Possibly pure IPV6 machine.

Attempting to import LDIF to ::1

2009-05-22 09:25:09 INFO Importing "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\ldif\vc_schema.ldf". Host: ::1; Port: 389

2009-05-22 09:25:09 SEVERE Operation "Create standalone instance VMwareVCMSDS" failed: : Action: Create Standalone Instance

Action: Creation of standalone instance

Action: LDIF Import

Action: Process execution

Problem: Import LDIF failed: 8224. Output: Connecting to "::1"

The connection cannot be established

The error code is 8224

No log files were written. In order to generate a log file, please

specify the log file path via the -j option.

2009-05-22 09:25:09 SEVERE Recovering from failed Operation "Create standalone instance VMwareVCMSDS"

2009-05-22 09:25:09 INFO Removing directory services instance VMwareVCMSDS

2009-05-22 09:25:11 INFO Removal complete

2009-05-22 09:25:11 SEVERE Recovery successful

2009-05-22 09:25:11 SEVERE Execution error.

-


file = vminst.txt

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 --- CA exec: VMCheckPendingReboots

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 Checking for pending reboots...

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 checking for pending reboots under Microsoft\Updates key...

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 checking for pending reboots under &lt;SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired&gt; ...

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 registry entry with data 1 not found

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 --- CA exec: VMSetVCSInstallDir

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 Getting Property VCS_FOUND =

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 ERROR: Setup failed to detect VirtualCenter Server installation on the computer

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 --- CA exec: VMCheckSPLevelForWinXP

VMware VirtualCenter-build-162856: 05/22/09 09:02:38 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:39 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:39 --- CA exec: VMResetRegSecurity

VMware VirtualCenter-build-162856: 05/22/09 09:02:39 Reseting security for HKLM\SOFTWARE\VMware, Inc.

VMware VirtualCenter-build-162856: 05/22/09 09:02:39 Reseting security for HKLM\SOFTWARE\VMware, Inc.\VMware VirtualCenter

VMware VirtualCenter-build-162856: 05/22/09 09:02:39 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:39 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:39 Saving installer window caption

VMware VirtualCenter-build-162856: 05/22/09 09:02:39 Getting Property ProductName = VMware vCenter Server

VMware VirtualCenter-build-162856: 05/22/09 09:02:39 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:39 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:39 --- CA exec: VMCheckRunningClients

VMware VirtualCenter-build-162856: 05/22/09 09:02:39 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:40 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:40 --- CA exec: VMInstallMSVCRTRedist

VMware VirtualCenter-build-162856: 05/22/09 09:02:40 Microsoft VC 8.0 SP1 redist (x86) not found to be installed

VMware VirtualCenter-build-162856: 05/22/09 09:02:40 Getting Property SETUPEXEDIR = C:\Documents and Settings\administrator.mydomain\Desktop\VMware-VIMSetup-all-4.0.0-162902\vpx

VMware VirtualCenter-build-162856: 05/22/09 09:02:40 Found "C:\Documents and Settings\administrator.mydomain\Desktop\VMware-VIMSetup-all-4.0.0-162902\vpx\..\redist\vcredist\vcredist_x86.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:02:40 Attempting to launch "C:\Documents and Settings\administrator.mydomain\Desktop\VMware-VIMSetup-all-4.0.0-162902\vpx\..\redist\vcredist\vcredist_x86.exe" /Q

VMware VirtualCenter-build-162856: 05/22/09 09:02:48 Process returned 0

VMware VirtualCenter-build-162856: 05/22/09 09:02:48 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 --- CA exec: VMSyncTempFolder

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Util_GetTempPath: C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Getting Property TempFolder = C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 TempFolder: C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 --- CA exec: VMSetVCServerIP

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 The dns name of the localhost is VC01

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 given host is VC01

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 IP address of the given host is 192.168.1.28

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Setting property VC_SERVER_IP = 192.168.1.28

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 --- CA exec: VMSetComputerFQDN

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Checking domain membership...

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Using ComputerNameDnsFullyQualified

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 ComputerNameDnsFullyQualified=http://VC01.mydomain.org

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Setting property USE_FQDN = 1

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 FQDN http://VC01.mydomain.org

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Setting property COMPUTER_FQDN = VC01.mydomain.org

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 --- CA exec: VMRestoreProxyXMLAttrib

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Getting Property VPX_COMMON_DATA = C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Error updating attributes for C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\proxy.xml file

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 --- CA exec: VMCheckMsde

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Setting property MSDE_INSTALLED =

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Getting Property MSDE_INSTANCE = SQLEXP_VIM

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 Cannot open the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server: 2

VMware VirtualCenter-build-162856: 05/22/09 09:02:49 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:50 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:02:50 --- CA exec: VMListODBCDsns

VMware VirtualCenter-build-162856: 05/22/09 09:02:50 No ODBC DSN created on the machine.

VMware VirtualCenter-build-162856: 05/22/09 09:02:50 Getting Property UILevel = 5

VMware VirtualCenter-build-162856: 05/22/09 09:02:50 MsiUtil_GetTextString successful.

VMware VirtualCenter-build-162856: 05/22/09 09:02:50 Setting property DB_DSN = (Please create a 32 bit system DSN)

VMware VirtualCenter-build-162856: 05/22/09 09:02:50 Setting property DB_DSN_COUNT = 0

VMware VirtualCenter-build-162856: 05/22/09 09:02:50 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:04 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:04 --- CA exec: VMValidateLicenseKey

VMware VirtualCenter-build-162856: 05/22/09 09:03:04 Setting property SerialOK =

VMware VirtualCenter-build-162856: 05/22/09 09:03:04 -


IsValidLicense-----

VMware VirtualCenter-build-162856: 05/22/09 09:03:04 Serial Number is empty, so going in evaluation mode...

VMware VirtualCenter-build-162856: 05/22/09 09:03:04 Setting property License_LinkedModeCapable = 1

VMware VirtualCenter-build-162856: 05/22/09 09:03:04 Setting property SerialOK = 1

VMware VirtualCenter-build-162856: 05/22/09 09:03:04 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 --- CA exec: VMCheckDbInstance

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Getting Property MSDE_INSTALLED =

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Getting Property DB_SERVER_TYPE = Bundled

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Getting Property MSDE_INSTANCE = SQLEXP_VIM

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Getting Property DB_NAME = VIM_VCDB

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Getting Property VCI_DB_NAME =

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Getting Property SUITETYPE =

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Getting Property InstallDir_Changed =

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Setting property DB_DRIVER_TYPE = MSSQL

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Getting Property ComputerName = VC01

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Setting property CreateDbOK = 1

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Setting property VCI_FORMAT_DB =

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 Setting property FORMAT_DB = 1

VMware VirtualCenter-build-162856: 05/22/09 09:03:06 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:15 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:15 --- CA exec: VMCheckINSTALLDIR

VMware VirtualCenter-build-162856: 05/22/09 09:03:15 Setting property InstallDirOK =

VMware VirtualCenter-build-162856: 05/22/09 09:03:15 Getting Property INSTALLDIR = C:\Program Files\VMware\Infrastructure\

VMware VirtualCenter-build-162856: 05/22/09 09:03:15 Did not find file/directory: "C:\Program Files\VMware\Infrastructure\"

VMware VirtualCenter-build-162856: 05/22/09 09:03:15 Getting Property VersionNT64 =

VMware VirtualCenter-build-162856: 05/22/09 09:03:15 Getting Property DB_DRIVER_TYPE = MSSQL

VMware VirtualCenter-build-162856: 05/22/09 09:03:15 Getting Property ProgramFiles64Folder =

VMware VirtualCenter-build-162856: 05/22/09 09:03:15 Setting property InstallDirOK = 1

VMware VirtualCenter-build-162856: 05/22/09 09:03:15 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:36 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:36 --- CA exec: VMAdamCheckPrereqs

VMware VirtualCenter-build-162856: 05/22/09 09:03:36 Setting property AdamPrereqsOK =

VMware VirtualCenter-build-162856: 05/22/09 09:03:36 major.minor=http://5.2, szCSDVersion=Service Pack 1, wSuiteMask=0x00000110

VMware VirtualCenter-build-162856: 05/22/09 09:03:36 Server install

VMware VirtualCenter-build-162856: 05/22/09 09:03:36 ComputerNameDnsHostname=VC01

VMware VirtualCenter-build-162856: 05/22/09 09:03:36 Full DNS Computer name = VC01

VMware VirtualCenter-build-162856: 05/22/09 09:03:36 localhost resolves to 127.0.0.1

VMware VirtualCenter-build-162856: 05/22/09 09:03:36 Checking domain membership...

VMware VirtualCenter-build-162856: 05/22/09 09:03:36 Domain member - correctly joined (\)

VMware VirtualCenter-build-162856: 05/22/09 09:03:36 Setting property AdamPrereqsOK = 1

VMware VirtualCenter-build-162856: 05/22/09 09:03:36 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 --- CA exec: VMValidateVCServerPorts

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Setting property UPDATE_FLAG = 0

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Setting property PortSettingsOK =

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property VCS_HTTPS_PORT_OLD =

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property VCS_HTTPS_PORT = 443

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Min 1, Max 65535, Actual 443

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 port 443 is OK!

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Setting property UPDATE_FLAG = 1

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property VCS_HTTP_PORT_OLD =

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property VCS_HTTP_PORT = 80

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Min 1, Max 65535, Actual 80

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 port 80 is OK!

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Setting property UPDATE_FLAG = 1

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property VCS_HEARTBEAT_PORT_OLD =

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property VCS_HEARTBEAT_PORT = 902

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Min 1, Max 65535, Actual 902

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 port 902 is OK!

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Setting property UPDATE_FLAG = 1

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property TC_HTTP_PORT_OLD =

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property TC_HTTP_PORT = 8080

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Min 1, Max 65535, Actual 8080

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 port 8080 is OK!

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property TC_HTTPS_PORT_OLD =

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property TC_HTTPS_PORT = 8443

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Min 1, Max 65535, Actual 8443

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 port 8443 is OK!

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property VCS_ADAM_LDAP_PORT_OLD =

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property VCS_ADAM_LDAP_PORT = 389

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Min 1025, Max 65535, Actual 389

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 port 389 is OK!

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property VCS_ADAM_SSL_PORT_OLD =

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Getting Property VCS_ADAM_SSL_PORT = 636

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Min 1025, Max 65535, Actual 636

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 port 636 is OK!

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 Setting property PortSettingsOK = 1

VMware VirtualCenter-build-162856: 05/22/09 09:03:38 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:39 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:39 --- CA exec: VMCheckDotNET

VMware VirtualCenter-build-162856: 05/22/09 09:03:39 Getting Property VersionNT = 502

VMware VirtualCenter-build-162856: 05/22/09 09:03:39 Setting property DotNetInstalled =

VMware VirtualCenter-build-162856: 05/22/09 09:03:39 Getting Property SETUPEXEDIR = C:\Documents and Settings\administratormydomainDesktop\VMware-VIMSetup-all-4.0.0-162902\vpx

VMware VirtualCenter-build-162856: 05/22/09 09:03:39 Found "C:\Documents and Settings\administrator.mydomainDesktop\VMware-VIMSetup-all-4.0.0-162902\vpx\..\redist\dotnet\dotnetfx30SP1setup.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:03:39 Setting property DOTNETSETUP_FILEPATH = C:\Documents and Settings\administrator.mydomainDesktop\VMware-VIMSetup-all-4.0.0-162902\vpx\..\redist\dotnet\dotnetfx30SP1setup.exe

VMware VirtualCenter-build-162856: 05/22/09 09:03:39 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:40 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:03:40 --- CA exec: VMInstallDotNet

VMware VirtualCenter-build-162856: 05/22/09 09:03:40 Getting Property VersionNT = 502

VMware VirtualCenter-build-162856: 05/22/09 09:03:40 Getting Property DOTNETSETUP_FILEPATH = C:\Documents and Settings\administrator.mydomainDesktop\VMware-VIMSetup-all-4.0.0-162902\vpx\..\redist\dotnet\dotnetfx30SP1setup.exe

VMware VirtualCenter-build-162856: 05/22/09 09:03:40 Found "C:\Documents and Settings\administrator.mydomainDesktop\VMware-VIMSetup-all-4.0.0-162902\vpx\..\redist\dotnet\dotnetfx30SP1setup.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:03:40 Attempting to launch "C:\Documents and Settings\administrator.mydomainDesktop\VMware-VIMSetup-all-4.0.0-162902\vpx\..\redist\dotnet\dotnetfx30SP1setup.exe" /passive /norestart

VMware VirtualCenter-build-162856: 05/22/09 09:11:57 Process returned 3010

VMware VirtualCenter-build-162856: 05/22/09 09:11:57 The installer reported that a reboot is required.

VMware VirtualCenter-build-162856: 05/22/09 09:11:57 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:11:57 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:11:57 --- CA exec: VMInstallMsde

VMware VirtualCenter-build-162856: 05/22/09 09:11:57 Getting Property SourceDir = C:\Documents and Settings\administrator.mydomainDesktop\VMware-VIMSetup-all-4.0.0-162902\vpx\

VMware VirtualCenter-build-162856: 05/22/09 09:11:57 Getting Property TempFolder = C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\

VMware VirtualCenter-build-162856: 05/22/09 09:11:57 Getting Property MSDE_INSTANCE = SQLEXP_VIM

VMware VirtualCenter-build-162856: 05/22/09 09:11:57 Getting Property VersionNT64 =

VMware VirtualCenter-build-162856: 05/22/09 09:11:57 Found "C:\Documents and Settings\administratormydomainDesktop\VMware-VIMSetup-all-4.0.0-162902\vpx\..\redist\SQLEXPR\x86\SQLEXPR32.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:11:57 Attempting to launch "C:\Documents and Settings\administratormydomainDesktop\VMware-VIMSetup-all-4.0.0-162902\vpx\..\redist\SQLEXPR\x86\SQLEXPR32.exe" /qb ADDLOCAL="ALL" /L*v "C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\vim-sqlsrvr-msi.log" INSTANCENAME=SQLEXP_VIM REBOOT=REALLYSUPPRESS DISABLENETWORKPROTOCOLS=0 SQLBROWSERAUTOSTART=1

VMware VirtualCenter-build-162856: 05/22/09 09:18:12 Process returned 0

VMware VirtualCenter-build-162856: 05/22/09 09:18:12 Setting property SQL_DB_TYPE = SQL Native Client

VMware VirtualCenter-build-162856: 05/22/09 09:18:12 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 --- CA exec: VMCheckSPLevelForWinXP

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 --- CA exec: VMCheckRunningClients

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 --- CA exec: VMSyncTempFolder

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 Util_GetTempPath: C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 Getting Property TempFolder = C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 TempFolder: C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 --- func: MsiUtil_SetTargetPath()

VMware VirtualCenter-build-162856: 05/22/09 09:18:47 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 --- CA exec: VMSetVCServerIP

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 The dns name of the localhost is VC01

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 given host is VC01

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 IP address of the given host is 192.168.1.28

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 Setting property VC_SERVER_IP = 192.168.1.28

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 --- CA exec: VMAdamValidateServerState

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 DomainNameFlat = mydomain

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 DomainNameDns = mydomain.org

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 DomainForestName = mydomain.org

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 MachineRole = DsRole_RoleMemberServer

VMware VirtualCenter-build-162856: 05/22/09 09:18:48 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 --- CA exec: VMBackupProxyXml

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 Getting Property VPX_COMMON_DATA = C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 Setting property PROXY_BACKUP_TIME = 4a16b449

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 Did not find file/directory: "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\proxy.xml"

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 Cannot copy non-existent file: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\proxy.xml

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 --- CA exec: VMDeleteDirectoriesImmediate

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 Getting Property VIM_DELETE_DIRS = C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 Failed to find any child files or directories for C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS, (3)

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 Failed to remove directory, error 3

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 failed deleting direcotry C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS

VMware VirtualCenter-build-162856: 05/22/09 09:18:49 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:19:17 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:19:17 --- CA exec: VMDeleteProxyXml

VMware VirtualCenter-build-162856: 05/22/09 09:19:17 Getting Property CustomActionData = C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\

VMware VirtualCenter-build-162856: 05/22/09 09:19:17 Deleting C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\proxy.xml

VMware VirtualCenter-build-162856: 05/22/09 09:19:17 Did not find file/directory: "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\proxy.xml"

VMware VirtualCenter-build-162856: 05/22/09 09:19:17 Already removed: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\proxy.xml

VMware VirtualCenter-build-162856: 05/22/09 09:19:17 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 --- CA exec: VMControlService

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Getting Property CustomActionData = vctomcat;0

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Srvc_StopService

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 OpenSrvcManager

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 OpenSrvc

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 OpenSrvc::ERROR_SERVICE_DOES_NOT_EXIST The specified service does not exist Error: 1060

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Srvc_StopService

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Srvc_IsService

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 OpenSrvcManager

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 OpenSrvc

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 OpenSrvc::ERROR_SERVICE_DOES_NOT_EXIST The specified service does not exist Error: 1060

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Srvc_IsService::Invalid parameter service handle

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Srvc_IsService::done Service does NOT EXIST

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Srvc_StopService:: vctomcat service NOT STOPPED

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 --- CA exec: VMControlService

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Getting Property CustomActionData = vpxd;0

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Srvc_StopService

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 OpenSrvcManager

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 OpenSrvc

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 OpenSrvc::ERROR_SERVICE_DOES_NOT_EXIST The specified service does not exist Error: 1060

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Srvc_StopService

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Srvc_IsService

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 OpenSrvcManager

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 OpenSrvc

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 OpenSrvc::ERROR_SERVICE_DOES_NOT_EXIST The specified service does not exist Error: 1060

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Srvc_IsService::Invalid parameter service handle

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Srvc_IsService::done Service does NOT EXIST

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Srvc_StopService:: vpxd service NOT STOPPED

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 --- CA exec: VMAdamInstall

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Getting Property CustomActionData = 502;;C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\{6B1A1F1B-0D64-412B-BD38-ED252FB37F98};C:\WINDOWS\system32\;;C:\WINDOWS\ADAM\

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 setupApp = C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\{6B1A1F1B-0D64-412B-BD38-ED252FB37F98}\ADAMSP1_x86_English.exe

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Found "C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\{6B1A1F1B-0D64-412B-BD38-ED252FB37F98}\ADAMSP1_x86_English.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:19:18 Attempting to launch "C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\{6B1A1F1B-0D64-412B-BD38-ED252FB37F98}\ADAMSP1_x86_English.exe" /q /norestart

VMware VirtualCenter-build-162856: 05/22/09 09:20:35 Process returned 0

VMware VirtualCenter-build-162856: 05/22/09 09:20:35 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:21:58 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:21:58 --- CA exec: VMSetIndexHtmlPage

VMware VirtualCenter-build-162856: 05/22/09 09:21:58 Getting Property CustomActionData = C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\docRoot\;index1.html

VMware VirtualCenter-build-162856: 05/22/09 09:21:58 Found "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\docRoot\index1.html"

VMware VirtualCenter-build-162856: 05/22/09 09:21:58 Found "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\docRoot"

VMware VirtualCenter-build-162856: 05/22/09 09:21:58 Copying 'C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\docRoot\index1.html' to 'C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\docRoot\index.html'

VMware VirtualCenter-build-162856: 05/22/09 09:21:58 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:23:35 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:23:35 --- CA exec: VMGenerateSSLKeys

VMware VirtualCenter-build-162856: 05/22/09 09:23:35 Getting Property CustomActionData = C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\{6B1A1F1B-0D64-412B-BD38-ED252FB37F98};C:\Program Files\VMware\Infrastructure\VirtualCenter Server\;C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\;VC01.mydomain.org

VMware VirtualCenter-build-162856: 05/22/09 09:23:35 Did not find file/directory: "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\rui.crt"

VMware VirtualCenter-build-162856: 05/22/09 09:23:35 No SSL keys found, generating new keys.

VMware VirtualCenter-build-162856: 05/22/09 09:23:35 Found "C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\{6B1A1F1B-0D64-412B-BD38-ED252FB37F98}\openssl.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:23:35 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server"

VMware VirtualCenter-build-162856: 05/22/09 09:23:35 Copying 'C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\{6B1A1F1B-0D64-412B-BD38-ED252FB37F98}\openssl.exe' to 'C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe'

VMware VirtualCenter-build-162856: 05/22/09 09:23:35 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:23:35 Attempting to launch "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe" genrsa -out "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cakey.pem"

VMware VirtualCenter-build-162856: 05/22/09 09:23:36 Process returned 0

VMware VirtualCenter-build-162856: 05/22/09 09:23:36 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:23:36 Attempting to launch "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe" req -x509 -new -batch -config "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cacert.cfg" -days 3650 -key "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cakey.pem" -out "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cacert.pem"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Process returned 0

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Attempting to launch "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe" genrsa -out "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\rui.key"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Process returned 0

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Attempting to launch "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe" req -new -batch -key "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\rui.key" -out "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\req.pem" -config "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\server.cfg"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Process returned 0

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Attempting to launch "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe" x509 -req -in "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\req.pem" -CA "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cacert.pem" -CAkey "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cakey.pem" -extfile "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\server.cfg" -extensions x509 -set_serial 1876278717 -days 3650 -out "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\rui.crt"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Process returned 0

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Process returned 0

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Deleting C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Deleted file C:\Program Files\VMware\Infrastructure\VirtualCenter Server\openssl.exe

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Deleting C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cacert.cfg

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Found "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cacert.cfg"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Deleted file C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cacert.cfg

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Deleting C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\server.cfg

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Found "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\server.cfg"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Deleted file C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\server.cfg

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Deleting C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cakey.pem

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Found "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cakey.pem"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Deleted file C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cakey.pem

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Deleting C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cacert.pem

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Found "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cacert.pem"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Deleted file C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\cacert.pem

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Deleting C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\req.pem

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Found "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\req.pem"

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 Deleted file C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\req.pem

VMware VirtualCenter-build-162856: 05/22/09 09:23:37 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 --- CA exec: VMWriteDbInfo

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 --- CA exec: VMAdamUpdateJoinToolScript

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Getting Property CustomActionData = C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\{6B1A1F1B-0D64-412B-BD38-ED252FB37F98};C:\Program Files\VMware\Infrastructure\VirtualCenter Server\;C:\Program Files\VMware\Infrastructure\jre\

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Found "C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\{6B1A1F1B-0D64-412B-BD38-ED252FB37F98}\jointool.bat"

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server"

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Copying 'C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\{6B1A1F1B-0D64-412B-BD38-ED252FB37F98}\jointool.bat' to 'C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jointool.bat'

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jointool.bat"

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Replacing "@@JAVA_EXE@@" with ""C:\Program Files\VMware\Infrastructure\jre\bin\javaw.exe"" in file "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jointool.bat"

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jointool.bat"

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Replacing "@@JOINTOOL_JAR@@" with ""C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jointool.jar"" in file "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jointool.bat"

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jointool.bat"

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Replacing "@@JWINAUTH_DLL@@" with ""C:\Program Files\VMware\Infrastructure\VirtualCenter Server\"" in file "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jointool.bat"

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 --- CA exec: VMAdamInvokeJoinTool

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Jointool command: --"C:\Program Files\VMware\Infrastructure\jre\bin\javaw.exe" -jar "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jointool.jar" init --statusFile "C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\status.txt" --name VC01.mydomain.org --vimURL https://VC01.mydomain.org:443/sdk --webServiceURL https://VC01.mydomain.org:8443/vws --ldapPort 389 --dsn "VMware VirtualCenter" --dbUser "" dbPassword "***********"

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Deleting

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Did not find file/directory: ""

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Already removed:

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Deleting C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\status.txt

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Did not find file/directory: "C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\status.txt"

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Already removed: C:\DOCUME1\ADMINI1.FOU\LOCALS~1\Temp\1\status.txt

VMware VirtualCenter-build-162856: 05/22/09 09:23:38 Found "C:\Program Files\VMware\Infrastructure\jre\bin\javaw.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:24:27 Process returned 255

VMware VirtualCenter-build-162856: 05/22/09 09:24:27 status.txt file size: 609

VMware VirtualCenter-build-162856: 05/22/09 09:24:27 linked mode operation failed with error 255. Join Mode = init Join Error ID = 28038

VMware VirtualCenter-build-162856: 05/22/09 09:24:27 Posting user message 28042

VMware VirtualCenter-build-162856: 05/22/09 09:24:40 MsiProcessMessage returned: 6

VMware VirtualCenter-build-162856: 05/22/09 09:24:40 PerformJoinOperation() -- HandleJoinToolResults returned &lt;1603&gt;

VMware VirtualCenter-build-162856: 05/22/09 09:24:40 Found "C:\Program Files\VMware\Infrastructure\jre\bin\javaw.exe"

VMware VirtualCenter-build-162856: 05/22/09 09:25:11 Process returned 255

VMware VirtualCenter-build-162856: 05/22/09 09:25:11 Jointool invoked with --force option

VMware VirtualCenter-build-162856: 05/22/09 09:26:07 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:26:11 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:26:11 --- CA exec: VMRollbackProxyXml

VMware VirtualCenter-build-162856: 05/22/09 09:26:11 Getting Property CustomActionData = C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\;4a16b449

VMware VirtualCenter-build-162856: 05/22/09 09:26:11 Found "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\proxy.xml"

VMware VirtualCenter-build-162856: 05/22/09 09:26:11 C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\proxy.xml file attributes changed successfully

VMware VirtualCenter-build-162856: 05/22/09 09:26:11 Did not find file/directory: "C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\proxy.xml.4a16b449"

VMware VirtualCenter-build-162856: 05/22/09 09:26:11 Cannot copy non-existent file: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\proxy.xml.4a16b449

VMware VirtualCenter-build-162856: 05/22/09 09:26:11 End Logging

VMware VirtualCenter-build-162856: 05/22/09 09:26:16 Begin Logging

VMware VirtualCenter-build-162856: 05/22/09 09:26:16 --- CA exec: VMCleanupRegistry

VMware VirtualCenter-build-162856: 05/22/09 09:26:16 Warning: Deleting a key that isn't empty: "HKEY_CURRENT_USER\VMW"

VMware VirtualCenter-build-162856: 05/22/09 09:26:16 Warning: Deleting a key that isn't empty: "\InstRTPaths"

VMware VirtualCenter-build-162856: 05/22/09 09:26:16 End Logging

VMware VCP 3.5 VMware VCP 4.0 VMware VCP 5.0
0 Kudos
Sotiris
Contributor
Contributor

I get the exact same errors as the screenshots you show. Can you explain how exactly you solved this problem?

0 Kudos
masselwagen
Contributor
Contributor

im my case when VI 3.5 was installed, I've generate SSL certificates for both VIM server and ESX hosts. so when error appear during upgrade, i've just replace my own genereted SSL certificates on VIM server (rui.key and rui.crt) with default, which was self-generated during VI3 installation (it was backed up before). after this procedure upgrade was successfull.

hope this will be helpful for you

0 Kudos
mtnbiker5
Contributor
Contributor

Thanks everyone for the insight. I too am having the same issue on a Server 2008 Enterprise (64 bit) box. This machine has never had vsphere loaded and I can't get by this error. If it is certificate related - does anyone have an idea on how to create the proper certs to allow th install to continue on?

0 Kudos
jbsengineer
Enthusiast
Enthusiast

I am having the same problem with a fresh install on 2008 (32-bit). Not sure how to resolve.

0 Kudos
mtnbiker5
Contributor
Contributor

I did find an error in the setup log at the point where it dies: The Windows component could not be configured because of an error: 87 "The parameter is incorrect." (Command line: "C:\Windows\system32\ocsetup.exe DirectoryServices-ADAM /passive /norestart")

I have forwarded this on to one of our account folks to see if someone can get us a quick answer, either a work around or a new installer (if the code is wrong). I will post back if I get it to work.

0 Kudos
degustator
Enthusiast
Enthusiast

I installed vCenter 4 on Windows Server 2008 R2 RC and found it a bit tricky. I received some errors which were very similar to those on screenshots. So I guess my workarounds would be also helpful for installing on Windows Server 2008. I recommend you should do the following prior to launching vCenter Server installation.

  1. Manually install the following Server Role using Server Manager: "Active Direcroty Lightweight Directory Services (AD LDS)". No need to configure anything, just get it installed.

  2. Copy the LDAP Data Interchange Format Data Exchange (LDIFDE) tool binary ("ldifde.exe" file) from one of your domain controllers to "C:\Windows\ADAM".

Hope this helps.

0 Kudos
mtnbiker5
Contributor
Contributor

No Luck - We already had the Directory Services role installed (it actually placed ldifde.exe n the ADAM directory - I replaced it with the one from our DC since it was slightly newer) - but it bombed at the same spot.

0 Kudos
admin
Immortal
Immortal

Hi,

Can you check the following

1) The machine on which you are intalling vSphere 4.0 is not a Domain Controller

2) Are there any ADAM instances running ( Win2k8 (x64 comes with ADAM installed by default) ,using LDAP ports 389 and service is stopped while installing vSphere

  • If this is the case see RNbq. The vCenter Server installer cannot detect service ports if the services are not running

When you install vCenter Server and accept the default ports, if
those ports are being used by services that are not running, the
installer cannot validate the ports and the installation fails. An
error message might appear, depending on which port is in use.

This problem does not affect IIS services. IIS services are correctly validated, regardless of whether the services are running.
Workaround: Verify which ports are being used for services that are
not running before beginning the installation and avoid using those
ports.

3) Make sure that your computer/VM is properly added to a domain and properly registerd to DNS.

-Ranga

0 Kudos
TechNut
Contributor
Contributor

It can also happen if you use the Compressed folders function of NTFS. It bombs out in exactly the same place. I had that happen to me. Once I made the folders non-compressed, it worked.

0 Kudos
Sotiris
Contributor
Contributor

I confirm that Degustator workaround worked for me. No need to install an LDS instance, Vcenter installer will do that. if another instance is running then there will be a conflict with the opened ports during installation (if using the default LDAP ports).

The "ldifde.exe" file was copied from one domain controller in "C:\Windows\ADAM" to the Vcenter server corresponding folder.

Thanks D.

0 Kudos
rbos3
Enthusiast
Enthusiast

Hi guys, I followed up all advices like installing the LDS role, copying the ldifde.exe file to the ADAM folder on the vCenter Server VM but still no luck.

I even created a new VM, deleted the old one, added it to domain and tried again but no luck.

At first I thought it had to do with our remote SQL server / SQL authentication but exactly the same error appears when using a local SQL Express installation.

A copy of the jointool-0.log:

Recovering from failed Operation "Create standalone instance VMwareVCMSDS"

Removing directory services instance VMwareVCMSDS

Removal complete

Recovery successful

Execution error.

JoinTool started

Storage directory for LDAP instance: C:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS

Operation Mode: initialize

Creating directory services instance VMwareVCMSDS

LDAP port = 389

Base DN = dc=virtualcenter,dc=vmware,dc=int

Storage dir = C:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS

Creation complete

Resetting VC LDAP service SSL port

Service 'VMwareVCMSDS' is shutdown

Importing "C:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\ldif\vc_schema.ldf". Host: 127.0.0.1; Port: 389

Importing LDIF on 127.0.0.1 failed with Action: LDIF Import

Action: Process execution

Problem: Import LDIF failed: 8224. Output:

.

Possibly pure IPV6 machine.

Attempting to import LDIF to ::1

Importing "C:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\ldif\vc_schema.ldf". Host: ::1; Port: 389

Operation "Create standalone instance VMwareVCMSDS" failed: : Action: Create Standalone Instance

Action: Creation of standalone instance

Action: LDIF Import

Action: Process execution

Problem: Import LDIF failed: 8224. Output:

Recovering from failed Operation "Create standalone instance VMwareVCMSDS"

Removing directory services instance VMwareVCMSDS

Removal complete

Recovery successful

Execution error.

Hopefully any helpfull information will come out,

René Bos

--- If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks! Visit my blog at http://snowvm.com ---
0 Kudos
jonb157
Enthusiast
Enthusiast

I'm encountering the exact same problem. I've tried an upgrade, fresh install, nada. I've made sure no group policies are affecting the Virtual center server, DNS is configured properly. Not sure what else I can do here.

JoinTool started

Storage directory for LDAP instance: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS

Operation Mode: initialize

Creating directory services instance VMwareVCMSDS

LDAP port = 389

Base DN = dc=virtualcenter,dc=vmware,dc=int

Storage dir = C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS

Creation complete

Resetting VC LDAP service SSL port

Service 'VMwareVCMSDS' is shutdown

Importing "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\ldif\vc_schema.ldf". Host: 127.0.0.1; Port: 389

Importing LDIF on 127.0.0.1 failed with Action: LDIF Import

Action: Process execution

Problem: Import LDIF failed: 8224. Output: Connecting to "127.0.0.1"

The connection cannot be established

The error code is 8224

No log files were written. In order to generate a log file, please

specify the log file path via the -j option.

.

Possibly pure IPV6 machine.

Attempting to import LDIF to ::1

Importing "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\ldif\vc_schema.ldf". Host: ::1; Port: 389

Operation "Create standalone instance VMwareVCMSDS" failed: : Action: Create Standalone Instance

Action: Creation of standalone instance

Action: LDIF Import

Action: Process execution

Problem: Import LDIF failed: 8224. Output: Connecting to "::1"

The connection cannot be established

The error code is 8224

No log files were written. In order to generate a log file, please

specify the log file path via the -j option.

Recovering from failed Operation "Create standalone instance VMwareVCMSDS"

Removing directory services instance VMwareVCMSDS

Removal complete

Recovery successful

Execution error.

0 Kudos
admin
Immortal
Immortal

Are you installing vCenter on pure IPV6 mode?

In logs it says ::: "Problem: Import LDIF failed: 8224. Output:

.

Possibly pure IPV6 machine."

If it is a pure IPV6, that need to added to pure IPV6 domain before installing VC.

-R

0 Kudos
jonb157
Enthusiast
Enthusiast

not that I know of. When I got into my NIC properties, I'm not running IPv6 on the server. Does that mean I NEED to install IPv6? I never read anywhere that this was required for vSphere and vCenter...

0 Kudos
admin
Immortal
Immortal

No, no need to install IPV6. As ,i see an error message in log file related to IPV6 , Just want to check if your VM on which you are installing vCenter in pure IPV6.

Please confirm if this is your setup:

1) Windows 2008 x64

2) SQL Express

0 Kudos
jonb157
Enthusiast
Enthusiast

no Ipv6 on vCenter server nor on domain controller. I'm running Windows Server Standard 2003 w/sp2 and SQL 2005

0 Kudos