Difference between revisions of "Known issues"

From TempusServa wiki
Jump to navigation Jump to search
old>Admin
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The following list describes known issues in Tempus Serva.
The following list describes wellknown issues in Tempus Serva.


This list is NOT yet complete - please await offical release 2013-03-01.
== Frontend ==


== Engine ==
===== 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
 
  main?command=dk.p2e.blanket.codeunit.common.PageConvertDatabaseToUTF8


===== Server suddenly crashes with a PermGen error =====
===== Special characters are not displayed correctly =====
* Cause: Your application server has too small PermGen memory space.  
You might be using an older version of the database that is not using UTF8. This can bo corrected by running this codeunit:
* Resulotion: Increase to higher value (128 mB)


Tempus Serva loads ressources when needed: This include stuff like Office templates handlers and OLAP cubes. Using the wrong settings, can cause runtime errors when a user suddenly activates a feature that has not been used before. This is behaviour by design, and will not be changed in future releases.
  main?command=dk.p2e.blanket.codeunit.common.PageConvertDatabaseToUTF8


===== Media files sometimes dont display after a boot =====
===== Media files sometimes dont display after a boot =====
Line 17: Line 23:
* Resolution: Tweak the configuration parameter '''mediaFilterDelayMS'''
* Resolution: Tweak the configuration parameter '''mediaFilterDelayMS'''


===== Users get SSL warnings in their browsers =====
===== Upload of files fails after server restart =====
This is most likely because you are using a wrapper of a site, where the URL was originally HTTP. Because of this some items in the wrapper may be referenced using HTTP (causing SSL warnings).
Sometimes tempoarray folders are not reestablished after the server boots


Resolve by completing steps in this article
* Frontend: Personal menu > Services > Rebuild folders
* Backend: Modules > Admin services


http://tempusserva.dk/mediawiki/index.php?title=Setting_up_SSL/HTTPS#Problems_with_wrappers
===== An error has occured =====
Sometimes lowlevel tampering with field configuration, or force changing field types will result in this error.


===== Performance is amazing  =====
* Workaround: Deploy solution
We know.
* Resolution
*# Check which field fails: Modules > Event viewer
*# Delete field and create again


== Designer ==
== Designer ==
===== References not fixed during restore where components need renaming (solution copies and/or bundles) =====
===== References not fixed during restore where components need renaming (solution/bundles) =====
Workaround: Correct all parent/child references manually
Workaround: Correct all parent/child references manually and redeploy solution


===== Solution configurations cannot be set to an empty value =====
===== Solution configurations cannot be set to an empty value =====
Line 39: Line 49:
In the future a list will be implemented to browse older backups, but untill hen you should just ignore this issue.
In the future a list will be implemented to browse older backups, but untill hen you should just ignore this issue.


== Platform specific issues ==
== Engine ==
 
No unfixed issues
 
== Conatainer specific ==
=== Tomcat ===
=== Tomcat ===
===== Warning during server stop =====
===== Warning during server stop =====
Line 54: Line 68:


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.
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.
=== OpenJDK ===
===== Problem with missing fonts =====
Example:
<blockquote>''java.lang.Error: Probable fatal error:No fonts found''</blockquote>
Fix: Install fonts into java library
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+got+java.awt.headless+problem

Revision as of 10:36, 30 November 2022

The following list describes wellknown issues in Tempus Serva.

Frontend

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

 main?command=dk.p2e.blanket.codeunit.common.PageConvertDatabaseToUTF8
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:

 main?command=dk.p2e.blanket.codeunit.common.PageConvertDatabaseToUTF8
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

Designer

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.

Engine

No unfixed issues

Conatainer specific

Tomcat

Warning during server stop

Example

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.

JBoss

WARN errors during boot

Example

17:56:40,337 WARN [org.jboss.as.server.deployment] (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.