I am trying to do a clean install of vRA 7.0 with the Wizard and selcting the simple install with external DB. DB is created during installation.
The Installation fail after a while running the database part with an error message:
<IAAS Servername> (SQL Server: <SQL Servername>) Database Failed |
Command Result
Message:
Error configuring vRealize Automation Server. For more information, refer to vCAC-Config.log after collecting the IaaS logs.
Description:
Output:
Downloading installer...
Execution time:00:02.625
Download succeeded.
Installing vCAC Server Custom Setup files on the disk
Executing:"C:\Users\<Username>\AppData\Local\Temp\VMware\vCAC\\vCAC-Server-Setup.exe" /s /w /V"/qn ADDLOCAL=Database INSTALLDIR=\"C:\Program Files (x86)\VMware\vCAC\\Server\" /Lvoicewarmup! \"C:\Program Files (x86)\VMware\vCAC\InstallLogs\Server-Setup.log""
vCAC Server Custom Setup Installation Succeeded, ExitCode:0
Execution time:00:17.231
Configuring vCAC IaaS core components:
- Database
Executing:"C:\Program Files (x86)\VMware\vCAC\Server\ConfigTool\\vCAC-Config.exe" /S "/P:C:\Users\<username>\AppData\Local\Temp\VMware\vCAC\\ConfigToolProperties.vCAC-Server-Database-ConfigTool.xml" "/L:C:\Program Files (x86)\VMware\vCAC\InstallLogs\vCAC-Config.log"
vCAC-Server-Custom-Database-ConfigTool Installation Failed, ExitCode:5500
Error configuring vRealize Automation Server. For more information, refer to vCAC-Config.log after collecting the IaaS logs.
Execution time:00:09.129
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
vCAC-Config.log:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2016-01-11 12 01 38 222 :================= Logging started at 2016-01-11 12 01 38 206 ==================
2016-01-11 12 01 38 222 :Product version: 7.0.0.5833.
Info : 2016-01-11 12 01 38 269 :Initialized configuration property for feature Database. Node read DATABASE_INSTANCE.
Initialized configuration property for feature Database. Node read DATABASE_NAME.
Initialized configuration property for feature Database. Node read DATA_PROTECTED.
Initialized configuration property for feature Database. Node read DATABASE_DATA_PATH.
Initialized configuration property for feature Database. Node read DATABASE_LOG_PATH.
Initialized configuration property for feature Database. Node read WINDOWS_AUTHEN_DATABASE_INSTALL_FLAG.
Initialized configuration property for feature Database. Node read DATABASE_INSTALL_SQL_USER.
Initialized configuration property for feature Database. Node read DATABASE_INSTALL_SQL_USER_PASSWORD.
Initialized configuration property for feature Database. Node read PRECREATED_DATABASE_FLAG.
Initialized configuration property for feature Database. Node read CREATE_MSSQL_AZMAN_STORE_FLAG.
Initialized configuration property for feature Database. Node read DATABASE_USE_ENCRYPTION.
Info : 2016-01-11 12 01 38 379 :Executing C:\Windows\Microsoft.NET\Framework\v4.0.30319\MsBuild.exe "C:\Program Files (x86)\VMware\vCAC\Server\Database\DeployVMPS.xml" /t:BuildDB /p:UsePreCreatedDatabase="False" /p:DBServer="<SQL Servername>";DBName="<DB name>" /p:DBUser="" /p:DBPassword=******
Info : 2016-01-11 12 01 38 677 :Microsoft (R) Build Engine version 4.0.30319.34209
Info : 2016-01-11 12 01 38 677 :[Microsoft .NET Framework, version 4.0.30319.34209]
Info : 2016-01-11 12 01 38 677 :Copyright (C) Microsoft Corporation. All rights reserved.
Info : 2016-01-11 12 01 39 147 :Build started 11.01.2016 12:01:39.
Info : 2016-01-11 12 01 39 633 :smileysilly:roject "C:\Program Files (x86)\VMware\vCAC\Server\Database\DeployVMPS.xml" on node 1 (BuildDB target(s)).
Info : 2016-01-11 12 01 39 633 :BuildDB:
Info : 2016-01-11 12 01 39 633 : ##BuildDB Creating and populating database
Info : 2016-01-11 12 01 39 648 : sqlcmd -S <SQL Servername> -i CreateDatabase.sql -v DBName="<DB name>" DBDir="\." LogDir="\." -b
Info : 2016-01-11 12 01 45 025 : Creating Database '<DB Name>'.
Info : 2016-01-11 12 01 45 025 : Using default SQL database data and log directory
Info : 2016-01-11 12 01 45 025 : Setting database compatibility level to SQL 2008.
Info : 2016-01-11 12 01 45 025 : Disabling full text search.
Info : 2016-01-11 12 01 45 025 : Setting database settings.
Info : 2016-01-11 12 01 45 119 : Executed CreateDatabase.sql.
Info : 2016-01-11 12 01 45 151 : sqlcmd -S <SQL Servername> -d "<DB Name>" -i VMPSOpsUser.sql -v ServiceUser="<Username>" UseWindowsAuthentication="True"
Info : 2016-01-11 12 01 45 480 : Executed VMPSOpsUser.sql.
Info : 2016-01-11 12 01 45 825 :Project "C:\Program Files (x86)\VMware\vCAC\Server\Database\DeployVMPS.xml" (1) is building "C:\Program Files (x86)\VMware\vCAC\Server\Database\Liquibase.xml" (2) on node 1 (RunLiquibase target(s)).
Info : 2016-01-11 12 01 45 825 :RunLiquibase:
Info : 2016-01-11 12 01 45 825 : "\bin\java.exe" -Djsse.enableCBCProtection=false -Djava.library.path="C:\Program Files (x86)\VMware\vCAC\Server\Database" -cp "liquibase.jar;jtds-1.3.1.jar" liquibase.integration.commandline.Main --driver=net.sourceforge.jtds.jdbc.Driver --url=jdbc:jtds:sqlserver://<SQL Servername>/"<DB Name>";ssl=request releaseLocks
Info : 2016-01-11 12 01 45 840 : The system cannot find the path specified.
Info : 2016-01-11 12 01 45 840 :C:\Program Files (x86)\VMware\vCAC\Server\Database\Liquibase.xml(28,5): error MSB3073: The command ""\bin\java.exe" -Djsse.enableCBCProtection=false -Djava.library.path="C:\Program Files (x86)\VMware\vCAC\Server\Database" -cp "liquibase.jar;jtds-1.3.1.jar" liquibase.integration.commandline.Main --driver=net.sourceforge.jtds.jdbc.Driver --url=jdbc:jtds:sqlserver://<SQL Servername>/"<DB Name>";ssl=request releaseLocks" exited with code 3.
Info : 2016-01-11 12 01 45 856 :Done Building Project "C:\Program Files (x86)\VMware\vCAC\Server\Database\Liquibase.xml" (RunLiquibase target(s)) -- FAILED.
Info : 2016-01-11 12 01 45 887 :Done Building Project "C:\Program Files (x86)\VMware\vCAC\Server\Database\DeployVMPS.xml" (BuildDB target(s)) -- FAILED.
Info : 2016-01-11 12 01 45 887 :Build FAILED.
Info : 2016-01-11 12 01 45 887 :"C:\Program Files (x86)\VMware\vCAC\Server\Database\DeployVMPS.xml" (BuildDB target) (1) ->
Info : 2016-01-11 12 01 45 887 :"C:\Program Files (x86)\VMware\vCAC\Server\Database\Liquibase.xml" (RunLiquibase target) (2) ->
Info : 2016-01-11 12 01 45 887 :(RunLiquibase target) ->
Info : 2016-01-11 12 01 45 887 : C:\Program Files (x86)\VMware\vCAC\Server\Database\Liquibase.xml(28,5): error MSB3073: The command ""\bin\java.exe" -Djsse.enableCBCProtection=false -Djava.library.path="C:\Program Files (x86)\VMware\vCAC\Server\Database" -cp "liquibase.jar;jtds-1.3.1.jar" liquibase.integration.commandline.Main --driver=net.sourceforge.jtds.jdbc.Driver --url=jdbc:jtds:sqlserver://<SQL Servername>/"<DB Name>";ssl=request releaseLocks" exited with code 3.
Info : 2016-01-11 12 01 45 981 : 0 Warning(s)
Info : 2016-01-11 12 01 45 981 : 1 Error(s)
Info : 2016-01-11 12 01 45 981 :Time Elapsed 00:00:06.74
the key is here:
------------
Info : 2016-01-11 12 01 45 840 : The system cannot find the path specified.
Info : 2016-01-11 12 01 45 840 :C:\Program Files (x86)\VMware\vCAC\Server\Database\Liquibase.xml(28,5): error MSB3073: The command ""\bin\java.exe" -Djsse.enableCBCProtection=false -Djava.library.path="C:\Program Files (x86)\VMware\vCAC\Server\Database" -cp "liquibase.jar;jtds-1.3.1.jar" liquibase.integration.commandline.Main --driver=net.sourceforge.jtds.jdbc.Driver --url=jdbc:jtds:sqlserver://<SQL Servername>/"<DB Name>";ssl=request releaseLocks" exited with code 3.
------------
meaning, Java is not correctly installed/configured or not accessible for the user doing the install.
You need:
64 bit JRE (and not x86) installed on the Windows machine, and properly added to JAVA_HOME of the computer, so that each user (or at least, the user which ins running the installer) to be able to run java.
A restart of the windows machine may be required after you've installed java
The wizard is supposedly handling all that, but something's amiss in your case.
the key is here:
------------
Info : 2016-01-11 12 01 45 840 : The system cannot find the path specified.
Info : 2016-01-11 12 01 45 840 :C:\Program Files (x86)\VMware\vCAC\Server\Database\Liquibase.xml(28,5): error MSB3073: The command ""\bin\java.exe" -Djsse.enableCBCProtection=false -Djava.library.path="C:\Program Files (x86)\VMware\vCAC\Server\Database" -cp "liquibase.jar;jtds-1.3.1.jar" liquibase.integration.commandline.Main --driver=net.sourceforge.jtds.jdbc.Driver --url=jdbc:jtds:sqlserver://<SQL Servername>/"<DB Name>";ssl=request releaseLocks" exited with code 3.
------------
meaning, Java is not correctly installed/configured or not accessible for the user doing the install.
You need:
64 bit JRE (and not x86) installed on the Windows machine, and properly added to JAVA_HOME of the computer, so that each user (or at least, the user which ins running the installer) to be able to run java.
A restart of the windows machine may be required after you've installed java
The wizard is supposedly handling all that, but something's amiss in your case.
Gut feel and no more is to take a look at the account under which the vRA Management Agent is running. Make sure it is local admin, and also make sure that it has appropriate permissions on the SQL server. Sysadmin is required for installation.
Grant
The issue I found was with the SQL Server Configuration.
Check in the SQL Server Configuration and make sure TCP/IP is enabled. Rollback to snapshot and retry all iaas.
I spent hours trying the java issue, and that wasn't the problem.
Ouch. Yeah, I've seen that a lot. Glad you got it sorted.
Grant
Thanks for the respons guys,
I fixed this with several webex sessions with VMware support.
The issue was related to the installation not able to run "\bin\java.exe"
After testing with scripts and some manual tasks we discovered that the automatic configuration/fix in the simple install did not handle everything correctly.
We did a manual Java installation and manual reboot of the IAAS server. That seem to fix this issue for me.
Yeah I found the automated install and checks, do NOT go an check everything that is needed.
I had the same issues in my logs stating the Java Errors, but what was odd, and after installing different java versions, changing paths, it wasn't the java at all, even though my logs looks exactly like yours. But glad it got fixed.
I had exactly the same error message in my installation log file. For me the problem was installing Java JRE 1.8 but after trying it with JRE 1.7 it succeeded.