After updating, Windows or Java the Chronicall services will not start. Shown below is a common error encountered. In Chronicall 3.9.5 and higher, Java is built in so if you are on a newer version of Chronicall, this article is no longer relevant.
"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 serivce 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. Download the newest version of Java. Click See all Java downloads and download window's offline 32 bit Java installation. Also, 64 bit if you have 64 bit Java installed.
Update Chronicall Settings
After running the installation go to C:\Program Files (x86)\Xima Software\Chronicall\tomcat\bin and run the chronicallw file as Administrator:
Check under the Java tab that it is checked to use the default Java path, click "apply" if necessary and "okay." If you are using 64 bit Java, you can manually navigate to the same path for 64 bit, usually shown as "C:\Program Files\Java\jre1.8.0_171\bin\server\jvm.dll".
It is also a good idea to check the Java path for Orient DB, Recording Library, and chroncialw Datagrid. Those file paths are below, and follow the same steps as above for the Chroncialw file.
Recording Library location
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 this, it is a manual process.
Navigate to C:\Program Files (x86)\Xima Software\Chronicall\settings.xml and open the document in notepad.
Start the Chronicall services.