This article covers various issues you may encounter running a new installation or update to the Chronicall software.
Chronicall processes and services can take some time to shut down during an update, and older versions of Chronicall (3.9.4 and earlier) can hit issues with Windows not recognizing Java has been updated.
Determine Issue Source. Below are the most common causes of installation or update issues.
Serial Key Error
Click on the bell on your Chronicall screen. Check for a serial key error, and if there is one, follow these steps to troubleshoot it.
Services Stopped Error
It may take some time for Chronicall related services and processes to shut down. Below is a screenshot of the Recording Library taking some time to shut down. Give it some time then select Retry.
If Retry still doesn't work manually shut down the related Chronicall services. If it continues to hang in manual shut down of services, manually kill all Chronicall related processes, and try shutting down the services again and it will be successful.
End the update and rerun the update as an Administrator in Windows, or with Root access for Linux.
For Windows, if you get an error saying that the postgres folder (in the Chronicall directory) needs permissions adjusted for everyone, it is recommended that you disable User Account Control, and then restart the server and continue.
Java Not Detected
This is a legacy troubleshooting step, as Chronicall 3.9.5 and higher have both 32-bit and 64-bit Java built in. If you get an error that Java needs to be updated, verify you have updated to the most recent 32 bit Java offline installation.
If you are also using 64 bit Java to use higher allocated memory (RAM) for Chronicall, follow this article to verify all 64 bit Java paths have been updated.