After updating Windows or Java, the Chronicall service will not start. Shown below is a common error encountered.
"Windows could not start the Chronicall on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1."
There was likely a Java path that was manually set earlier. When Java is updated, Chronicall would need the Java path update as well.
Go to java.com and download the newest version of Java. Click "See all Java downloads" and download the Window's Offline 32-bit Java installation. Also, 64-bit if you have 64-bit Java installed.
Update Chronicall Settings
After running the Java installation go to C:\Program Files (x86)\Xima Software\Chronicall\tomcat\bin and run the chronicallw.exe file as an Administrator
Check under the Java tab that the "Use default" Java path box is checked, click "Apply" if necessary and "OK." If you are using 64 bit Java, you can manually navigate to the same path for 64 bit, usually found at C:\Program Files\Java\<java version>\bin\server\jvm.dll.
It is also a good idea to check the Java paths for the Orient DB, Recording Library, and the chronicallw for the Datagrid. Those file paths are below, and follow the same steps as above from the chronicalllw file.
- Recording Library
- C:\Program Files (x86)\Xima Software\Chronicall\recording library\recordinglibraryw.exe
- C:\Program Files (x86)\Xima Software\Chronicall\orientdb\bin\chronicallcdrw.exe
- Below is the Postgres location, which has to be edited in Notepad. It does not have a w.exe file to edit the path, it is a manual process.
- Navigate to C:\Program Files (x86)\Xima Software\Chronicall\settings.xml and open the document in notepad.
Edit the Java 64 bit home under <setting key="java.64bit.home" value="C:\Program Files\Java\jre1.8.0_131"/> to reflect the Java folder, not the jvm file.
Restart Chronicall services after changes are finalized