Chronicall Fails to Launch, But the Chronicall Services Are Running on the Server

When attempting to access Chronicall via the Desktop Client, Browserless app, or Web Interface, the following error message is shown:

There was an error loading Chronicall Desktop

java.io.FileNotFoundException: http://localhost:9080/desktop

Cause

There are a few common causes of this issue.

• Chronicall server hard drive is full.
• A corrupt or missing tomcat-users.xml, or a missing web.xml file.
• The custom Java paths have changed.
• settings.xml file is corrupt.

Resolution

Check HDD Space

1. Log into the Chronicall server.
2. Ensure the hard disk drive Chronicall is installed on is not full.
3. If you notice the hard disk is running out of storage, you can delete any old tomcat logs if they're taking up an excessive amount of room.

Tomcat-users.xml Corrupt (Does Not Exist in Chronicall 3.10 and Above)

1. Stop all Chronicall services.

   📘

   Note

   This will stop all logging, recording, and call routing. Multimedia customers will lose any calls in queue, or calls might get stuck in the queue.

2. If on Windows Server, look for any rogue Chronicall processes in Task Manager. If found, end the task.

3. Verify the Java path in the chronicallw folder.

4. Locate tomcat-users.xml at the following file path:

   • Windows: C:\Program Files (x86)\Xima Software\Chronicall\tomcat\conf\tomcat-users.xml
   • Linux: /var/lib/Xima Software/Chronicall/tomcat/conf/tomcat-users.xml

5. Open the file and verify the text is in the same format as shown:
   <?xml version='1.0' encoding='utf-8'?>
   <tomcat-users>
   </tomcat-users>

   • If not, reach out to Xima Support to receive a new tile.

6. Restart all Chronicall services.

Web.xml Corrupt

1. Stop all Chronicall/ACR services.

   📘

   Note

   This will stop all logging, recording, and call routing. Multimedia customers will lose any calls in queue, or calls might get stuck in the queue.

2. If on Windows Server, look for any rogue Chronicall/ACR processes in Task Manager. If found, end the task.

3. Verify the Java path in the chronicallw folder. You can refer to this article to verify the Java path is still valid.

4. Locate web.xml at the following file path and open the file:

   • Windows: C:\Program Files (x86)\Xima Software\Chronicall\tomcat\webapps\ROOT\WEB-INF
   • Linux: /var/lib/Xima Software/Chronicall/tomcat/webapps/ROOT/WEB-INF

5. Open the file and verify the text is in the same format as shown:

   

   • If the folder is missing the web.xml file, the file is blank, or it doesn't appear as above, reach out to Xima Support to receive a new file.

6. Restart all Chronicall services.

Settings.xml Corrupt

1. Navigate to the Chronicall directory (path above) to locate the settings.xml file.
2. Stop all Chronicall-related services (if you are not a Multimedia site) and move the settings.xml file to the desktop, so you have a copy of it in case anything goes wrong.
3. Rename the settings.bak file to settings.xml, after copying settings.bak to the desktop as well.
4. Start Chronicall services again and test Chronicall for functionality.

Settings.xml Missing or path.txt Incorrect (Linux)

1. Navigate to the /etc/chronicall directory in Linux.
2. You should see a settings.xml file in that directory.

   • If you don't, copy the settings file from the Chronicall/ACR directory and paste it here.

     

3. Open the path.txt file and verify the path inside is the actual path to Chronicall/ACR.
   • If it's not, change it to the correct path, then save the file.