When you perform a Java upgrade on your machine, this can cause temporary issues with the DataSync Agent. The main issue is the path that the DataSync Agent uses for Java is no longer valid. When the DataSync Agent runs, it is actually running two processes. One for the Java Service Wrapper that allows the Agent to run as a service and another for the actual Agent Java application itself.
When the Agent runs these processes, it will use the system level "java" command to execute this. If the path of this is no longer valid, then the command may not work properly and the Agent will run into issues and not start properly.
The following are suggested troubleshooting techniques for the issues upon upgrading the Java version in your Windows machine:
Validate that Java is installed and callable
Open a command prompt and execute the following command:
java -version
The version of Java installed should appear:
C:\Users\example>java -version java version "1.8.0_181" Java(TM) SE Runtime Environment (build 1.8.0_181_b12) Java Hotspot(TM) 64-Bit Server VM (build 25.181-b12, mixed mode)
If not, validate that java is correctly installed and accessible within this environment.
Validate that the installed version matches the path
Open a command prompt and execute the following command:
where java
NOTE: This should output the same version as the previous step.
The location where Java is located at should appear:
C:\Users\example>where java C:\ProgramData\Oracle\Java\javapath\java.exe C:\Program Files\Java\jdk1.8.0_181\java.exe
You should be able to find these java.exe files within your environment and validate that they exists (or link to another). If these do not exist or do not point to the right path, validate that Java is installed and callable or validate that the Environment Variables show the right PATH value.
Validate that the Environment Variables show the right PATH value
On the Windows taskbar, search Edit the system environment variables. Then, under Advanced tab, click Environment Variables.
Validate that the Variables for the user and the System Variables both have a Path variable where the Value contains the correct path to where the Java bin folder is installed (i.e. C:\Program Files\Java\jdk1.8.0_181\bin). If not, change the Value to the path relative to the correct folder.
Restart the system
If all of the above suggestions are validated and no changes are needed, reboot the environment. Sometimes during the Java upgrades, the environment requires a restart.
Force a specific path
As a temporary measure, follow these steps in order to force the Agent to use a specific path for Java rather than the system path for Java:
WARNING: Since you are forcing a Java path, you may run into errors on future Java upgrades.
Run the following command as administrator to remove the previous service if it existed:
uninstallService.bat
Verify that the Perspectium DataSync Agent Service is removed.
Open the wrapper.conf file within conf folder of the DataSync Agent.
Locate the line for wrapper.conf=java (should be around line 11).
Determine the full path to your java executable, for example:
C:\Program Files\Java\jre1.8.0_181\bin\java.exe
Replace the wrapper.conf=java with the escaped \ version of above, for example:
wrapper.conf=C:\\Program Files\\Java\\jre1.8.0_181\\bin\\java.exe
Run the following command for the Agent as administrator:
installService.bat
Verify that the Service appears after this and that when you look at the properties the Path to Executable is showing:
C:\Program Files\Java\jre1.8.0_181\bin\java.exe" -classpath ...........
Start the Service.
This is replacing the java call that the Service is performing with the full path of the java call. If this still does not resolve your issue please contact Perspectium Support.