Known issues

From TempusServa wiki
Jump to navigation Jump to search

The following list describes wellknown issues in Tempus Serva.


Certain texts result in error when saving

When saving you get an error that looks like this

 Incorrect string value: '\xC2\x94s\xC3

Your database is in legacy format and needs updating

Special characters are not displayed correctly

You might be using an older version of the database that is not using UTF8. This can bo corrected by running this codeunit:

Media files sometimes dont display after a boot

Media files are stored temporaryly within the web application when requested. Depending of the speed of the underlying filesystem, they will not allways be available for the server right away.

  • Workaround: Reload the page (F5)
  • Resolution: Tweak the configuration parameter mediaFilterDelayMS
Upload of files fails after server restart

Sometimes tempoarray folders are not reestablished after the server boots

  • Frontend: Personal menu > Services > Rebuild folders
  • Backend: Modules > Admin services
An error has occured

Sometimes lowlevel tampering with field configuration, or force changing field types will result in this error.

  • Workaround: Deploy solution
  • Resolution
    1. Check which field fails: Modules > Event viewer
    2. Delete field and create again


References not fixed during restore where components need renaming (solution/bundles)

Workaround: Correct all parent/child references manually and redeploy solution

Solution configurations cannot be set to an empty value

Workaround: Set value to single whitespace " ".

Old backups from other solutions found in list of backups

When deleting solutions the Designer does not delete corresponding backups (saftety reasons).

In the future a list will be implemented to browse older backups, but untill hen you should just ignore this issue.


No unfixed issues

Conatainer specific


Unable to restart services

Kille the underlying processes for both webserver and database

sudo killall -KILL mysqld_safe mysqld

If you cannot start MySQL again try removing the logfiles

sudo mv /mnt/sda/mysql/ib_logfile0 /mnt/sda/backup/
sudo mv /mnt/sda/mysql/ib_logfile1 /mnt/sda/backup/
sudo mv /mnt/sda/mysql/ibdata1 /mnt/sda/backup/

In some cases DB table repairs are needed

nano /etc/my.cnf

Add the line

innodb_force_recovery = 1

Recover data from backup

Create a restore script

 sudo nano ./
 chmod 777 ./

Add the following


for sql_file in `ls /mnt/sda/backup/rsync/${APP}base_*.sql`;
do mysql -uroot -pPASSWORD ${APP}base < $sql_file ;

for sql_file in `ls /mnt/sda/backup/rsync/${APP}live_*.sql`;
do mysql -uroot -pPASSWORD ${APP}live < $sql_file ;

for sql_file in `ls /mnt/sda/backup/rsync/${APP}test_*.sql`;
do mysql -uroot -pPASSWORD ${APP}test < $sql_file ;


Warning during server stop


SEVERE: The web application [/sandbox] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

The warning is of no importance because the shutdown automatically kills all objects in memory, and no memory leaks are there possible.


WARN errors during boot


17:56:40,337 WARN [] (MSC service thread 1-12) Class Path entry ...

The warnings are due to jar taht have their version number appended to their name. Possible fixes include stripping the names of all jar files in the /WEB-INF/lib/, but recommended solution is ignoring the warnings.