Changes for page Troubleshooting

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -31,7 +31,7 @@
31	31	)))|This error message is shown for general errors. See the issue 2.2 below.
32	32	|2.2|(((
33	33	* Error message: An unexpected error has occurred while processing the submitted form data. / Submission failed
34		-)))|The data that have been submitted could not be processed. Usually this is caused by an action in the [[workflow processing>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.WebHome]] that could not processed correctly. such as when a mail could not be sent, no mail server has been configured, a PDF could not be created. When you are using custom plugins, check whether they are throwing any uncaught errors. To resolve this issue, a detailed examination of the [[log>>doc:Formcycle.UserInterface.Protocol]] and {{formcycle/}}'s internal log files may be required.
	34	+)))|The data that have been submitted could not be processed. Usually this is caused by an action in the [[workflow>>doc:Formcycle.Designer.Workflow.WebHome]] that could not processed correctly. such as when a mail could not be sent, no mail server has been configured, a PDF could not be created. When you are using custom plugins, check whether they are throwing any uncaught errors. To resolve this issue, a detailed examination of the [[log>>doc:Formcycle.UserInterface.Protocol]] and {{formcycle/}}'s internal log files may be required.
35	35	|2.3|(((
36	36	* Error message: This form has already been sent.
37	37	)))|When you would like to submit the form again and create a new form record, open the original link to the form in a new browser tab or window. Do not use a link that has been generated when saving the form for later editing.
...	...	@@ -51,7 +51,7 @@
51	51	== Inbox ==
52	52
53	53	|= |=Problem|=Lösung
54		-|1|Form records in the inbox cannot be deleted.|Form records are deletable if they are selected and a //Delete// icon {{ficon name="trash-alt2"/}} appears in the form record list. Contact your administrator or check whether the option [[Form records in this state can be deleted>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.States.WebHome]] has been set for the form's current state.
	54	+|1|Form records in the inbox cannot be deleted.|Form records are deletable if they are selected and a //Delete// icon {{ficon name="trash-alt2"/}} appears in the form record list. Contact your administrator or check whether the option [[Form records in this state can be deleted>>doc:Formcycle.Designer.Workflow.States.WebHome]] has been set for the form's current state.
55	55
56	56	== Frontend server ==
57	57
...	...	@@ -71,7 +71,6 @@
71	71	* Rarely it may be necessary to restart {{formcycle/}}. In this case, check the {{formcycle/}} log files as well.
72	72	)))
73	73	|2|A database update has been detected. It is reccommended to have the database updated by an administrator.|This happens mainly when {{formcycle/}} has bee updated. You can still use {{formcycle/}}, but we strongly reccommend to run the database update. Contact your system administrator. See the help pages on [[updating the system>>doc:Formcycle.Installation.Update]] for further instructions.
74		-|3|When creating or updating the database, or during normal use, the following error occurs: //java.lang.ClassCastException: class java.time.LocalDateTime cannot be cast to class java.lang.String (java.time.LocalDateTime and java.lang.String are in module java.base of loader 'bootstrap')//|This is due to an incompatibility with the //MySQL Connector/J// in version 8.0.23. Please use the previous //Connector/J// version 8.0.22 instead.
75	75
76	76	== Form designer ==
77	77
...	...	@@ -102,3 +102,6 @@
102	102
103	103	|= |= Issue|=Solution
104	104	|1|Application servers, eg. Tomcat or JBoss, crashes with the error message //OutOfMemory//.|You need to increase the available RAM for the Java virtual machine. For Tomcat, these settings are described on the [[help pages for setting up Tomcat>>doc:Formcycle.SystemSettings.TomcatSettings.LimitUploadSize]].
	104	+|2|It is not possible to log in to {{formcycle/}} as sadmin with the default password directly after the initial installation on a Linux-based system.|{{formcycle/}} needs to store certain settings in the file system. Some Linux-based systems do not set a home directory for the tomcat user by default. This can usually be configured in the {{code language="none"}}/etc/passwd{{/code}} file. After the tomcat user has been modified, a restart is required.
	105	+|3|High CPU load already at the start of the application without further accesses|Older Java 11 releases [[contain a bug in the SSLEngine>>https://bugs.openjdk.org/browse/JDK-8241054]], which under certain circumstances can lead to dead loops when calling URLs over SSL, resulting in high CPU usage. This bug has been officially fixed in Java 11 release 11.0.8. If you are using an older Java 11 version up to and including 11.0.7, please upgrade to a newer version.
	106	+|4|DB connection cannot be established after updating the MS SQL JDBC driver|Newer versions of the MS SQL JDBC driver check whether the certificate used by the database server is valid. After an update of the driver, errors may therefore occur when connecting to the database, which are visible in the log as {{code language="none"}}sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target{{/code}}. Either the root certificate (and any intermediate certificates used) with which the certificate of the database server was generated must be imported into the Java TrustStore or the certificate check must be switched off via parameters in the JDBC URL ({{code language="none"}}encrypt=true;trustServerCertificate=true{{/code}}). Further information and examples are provided in the [[Microsoft documentation>>https://learn.microsoft.com/en-us/sql/connect/jdbc/connecting-with-ssl-encryption?view=sql-server-ver16]]. When importing into the TrustStore, it should be noted that the Java environment must be restarted for the changes to be applied, which may require a restart of the machine.