Problem
This issue will occur when upgrading a Distributed Architecture (DA) eDP environment. If an error occurs related to the MySQLDataBackup, the installer will fail and do a small rollback procedure, making the system more unstable. The error message says something similar to "Failed to back up to MySQLDataBackup_1-23-2025-12.03.34
". If the installer is run a second time while in an unstable environment, a different error is seen closer to the beginning of the installation. This error says "Build failed: D:\CW\V102\b.bat check-primary-node
".
Error Message
Logs from the first failure in regards to MySQLBackup, the logs below appear in log D:\CW\Installer\log\<mm-dd-yyyy-hh.mm.ss>\cwinstall_mm-dd-yyyy-hh.mm.ss.log:
1-23-2025-12:03:34: Checking if MySQL is disabled
1-23-2025-12:03:34: MySQL is disabled.
1-23-2025-12:03:34: install cmd: cmd /C sc config MySQL start= demand
1-23-2025-12:03:35: install cmd: cmd /C sc start MySQL
1-23-2025-12:04:05: MySQL is started.
1-23-2025-12:04:05: MySQL pairing check.
1-23-2025-12:04:05: Stopping MySQL service.
1-23-2025-12:04:05: Stop sevice: MySQL
1-23-2025-12:04:18: Failed to back up to MySQLDataBackup_1-23-2025-12.03.34
Install log can be found at: D:\CW\Installer\log\1-23-2025-12.00.13\cwinstall_1-23-2025-12.00.13.log
1-23-2025-12:09:14:
1-23-2025-12:09:14: ********************************************
1-23-2025-12:09:14: * OnAbort...
1-23-2025-12:09:14: ********************************************
1-23-2025-12:09:14:
1-23-2025-12:09:14: ********************************************
1-23-2025-12:09:14: * Roll back FontCache service
1-23-2025-12:09:14: ********************************************
1-23-2025-12:09:14: Roll back service FontCache startup type to 3
1-23-2025-12:09:14: Roll back D:\CW\V102\config\templates\tomcat\server.keystore
Once the above failure has occurred. Subsequent upgrade attempts will fail, showing the errors in the log files shown below:
The logs below appear in log D:\CW\Installer\log\<mm-dd-yyyy-hh.mm.ss>\cwinstall_mm-dd-yyyy-hh.mm.ss.log
Build return error code 1: D:\CW\V102\b.bat check-primary-node > "D:\CW\Installer\log\1-23-2025-12.16.47\cwinstall_b_check-primary-node_1-23-2025-12.17.03.log" 2>&1
1-23-2025-12:17:04: check log file: D:\CW\Installer\log\1-23-2025-12.16.47\cwinstall_b_check-primary-node_1-23-2025-12.17.03.log for BUILD SUCCESSFUL
1-23-2025-12:17:04: FileGrep return error code: -4
1-23-2025-12:17:04: install cmd: cmd /C more +100 "D:\CW\Installer\log\1-23-2025-12.16.47\cwinstall_b_check-primary-node_1-23-2025-12.17.03.log" > D:\CW\Installer\log\1-23-2025-12.16.47\tempfile.txt
1-23-2025-12:17:04: Build failed: D:\CW\V102\b.bat check-primary-node > "D:\CW\Installer\log\1-23-2025-12.16.47\cwinstall_b_check-primary-node_1-23-2025-12.17.03.log" 2>&1
Install log can be found at: D:\CW\Installer\log\1-23-2025-12.16.47\cwinstall_1-23-2025-12.16.47.log
1-23-2025-12:19:00:
1-23-2025-12:19:00: ********************************************
1-23-2025-12:19:00: * OnAbort...
1-23-2025-12:19:00: ********************************************
1-23-2025-12:19:00:
1-23-2025-12:19:00: ********************************************
1-23-2025-12:19:00: * Roll back FontCache service
1-23-2025-12:19:00: ********************************************
1-23-2025-12:19:00: Roll back service FontCache startup type to 3
The above error tells you to then look at the log file called D:\CW\Installer\log\1-23-2025-12.16.47\cwinstall_b_check-primary-node_1-23-2025-12.17.03.log. Here is what is in that log file:
Build location is set to =
Build environment is set to =
JAVA32HOME = C:\jdk-8u412-windows-x32\jdk1.8.0_412
======== target = check-primary-node
'"C:\jdk-8u412-windows-x64\jdk1.8.0_412\bin\java"' is not recognized as an internal or external command,
operable program or batch file.
ANT COMMAND DONE
The same log file may also show the following:
check-primary-node:
[java] Checking if this node is the cluster master...
[java] appender logFilePath====D:/CW/V102\logs/default_output.log
[java] 2025-01-21 16:08:27,043 WARN [STDERR] (main:[]) Exception in thread "main" java.lang.RuntimeException: Failed to get the boot information, check database or network connection.
BUILD FAILED
D:\CW\V102\build.xml:545: Java returned: 1
Total time: 10 seconds
ANT COMMAND DONE
Cause
The issue in relation to MySQLDataBackup failing is still under investigation. The second problem occurs because the installer has already installed the newer java and removed the older java binaries and because the upgrade did not complete the older version of eDiscovery Platform (eDP) is pointing to an older version of java that no longer exists.
Solution
Workaround for the MySQLDataBackup failure:
1. Uninstall the local MySQL that is not being used and should be disabled.
2. Remove the D:\MySQL folder
3. Remove the D:\MySQLData folder
4. Remove the D:\mysqltemp folder if it exists
5. Restart the server.
Solution 1 for the second issue related to java:
Reinstall the older C:\jdk-8u412-windows-x32\jdk1.8.0_412 java back onto the server
Solution 2 for the second issue related to java:
See steps 6 and 7 from https://isearch.veritas.com/internal-search/en_US/article.100038911.html specifically for updating the config.pl file to point to the newer java installed.
Once the Workaround and one of the solutions above have been done, try the upgrade again. If a custom upgrade, keep MySQL checked so the installer will reinstall it.