Some or all scheduled reports can seem to disappear from "Reports > Schedule Report" within Chronicall (as shown below) if there is a corrupt schedule.
This can be caused by a corrupt value in the report, a local hard drive issue in storing the data, packet loss when saving changes over poor network conditions, or an update that has a legacy value in one of the columns or formulas that is no longer valid. It is rare, but it can occur thus this article was created.
Once you remove the corrupt scheduled report, the other scheduled reports will show up as normal in the Chronicall / Avaya Call Reporting user interface.
You will want to identify which scheduled report is corrupt and remove it following the steps below.
Locate Scheduled Reports Directory
By default, you can find the scheduled reports at the paths below on the Chronicall server.
- C:\Program Files (x86)\Xima Software\Chronicall\tomcat\webapps\ROOT\resources\schedules
- C:\Program Files\Chronicall\tomcat\webapps\ROOT\resources\schedules
- C:\Program Files\Avaya Call Reporting\tomcat\webapps\ROOT\resources\schedules
- Linux - /var/lib/Xima\ Software/Chronicall/tomcat/webapps/ROOT/resources/schedules
Move Scheduled Reports
- Once the scheduled reports are located, you'll need to select all (ctrl+A) and cut (ctrl+X) to remove them from this folder and paste them (ctrl+V) to another location.
- I would recommend a new folder on your Desktop for easy access.
- If you notice any scheduled reports that have a size of 0kb, try moving that first and refreshing your Scheduled Reports, as that is likely the corrupt schedule.
- If not, continue onto the steps below.
Move Schedules Back
- Once the scheduled reports are removed from the original directory, you'll need to insert one schedule at a time back into this folder.
- If you have a large number of scheduled reports, you can do them in chunks of 5 or 10 at a time to narrow down which block of scheduled reports has a corrupt report.
- Each time you insert one of these schedules back into the folder be sure to close and reopen “Schedule Report” within Chronicall to be sure that it's there. If you see it once you click under Schedule Report, that confirms that the scheduled report that was just moved has no issues
- Do this for each individual schedule until all of the schedules disappear once again (Be sure to click “cancel” each time you insert a new schedule before you get back into “Schedule Report”).
- If you do it in larger blocks keep going until you find the block with the issue.
- You will need to remove that specific block of scheduled reports again and check that block one by one to identify the corrupt report.
- When all the schedules disappear from Chronicall you have found your corrupt file. Be sure to remove and delete this schedule, make note of the title, and recreate this corrupt schedule from scratch.
- With Linux, a service restart may be required to get Chronicall to recognize the change in Scheduled Reports.