Issue Description
A common issue for the Orient Windows service not starting is often redundant .jar files. They will have the exact names, and just show different versions at the end of the file name.
Cause
This issue occurs when Java updates, but the old .jar files are not deleted as they should be during the Java update.
Resolution
We can manually browse to these files paths and remove any duplicate .jar files on the Chronicall server.
Steps
- Navigate to the first of two .jar locations as shown below.
- Windows 32 Bit - C:\Program Files (x86)\Xima Software\Chronicall\tomcat\webapps\root\webinf\lib
- Windows 64 Bit - C:\Program Files\Chronicall\tomcat\webapps\root\webinf\lib
- Linux - /var/lib/Xima\ Software/Chronicall/tomcat/webapps/root/webinf/lib
- Search for file names that match exactly, other than the version number.
- If you see any, delete the older duplicate file versions.
- In the example above, we would want to delete the "commons-beanutils-1.7.jar", as it is an exact copy of the below file, other than version number.
- Repeat this for any duplicate .jar files.
- Next, move on to the following file paths, and do the same in this directory.
- Windows 32 Bit - C:\Program Files (x86)\Xima Software\Chronicall\orientdb\lib
- Windows 64 Bit - C:\Program Files\Chronicall\orientdb\lib
- Linux - /var/lib/Xima\ Software/Chronicall/orientdb/lib
- Now restart the Orient service, and it will launch as normal.
