Você está visualizando o conteúdo de ajuda da versão:
- 6.4
- 6.3
- 6.2
- Versões anteriores
This document includes several troubleshooting scenarios. For each scenario, some steps are provided to troubleshoot the problem. Follow these steps and, if the problem persists, configure the Logger to get and review logs for errors/warnings. For more details about HTML5 forms logging, see Generating Logs for HTML5 forms.
In the exception details, search for word caused by.
The probable reason is that one or more parameters in the URL are incorrect.
Check the following parameters:
Parameter | Description |
template | The filename of the template |
contentRoot | The path where template and associated resources reside |
dataRef | Absolute path of the data file that is merged with the template. Note: Path defines the absolute path of the data file. |
data | UTF-8 encoded data bytes that are merged with the template. |
-
Ensure that the specified parameters are correct. For detailed information on parameters, see Render Parameters.
-
Log in to CQ Web Console (Felix Console) at http://<server>:<port>/system/console/bundles.
Ensure that the status of the following bundles is "active":- scala-lang.bundle [osgi] (com.adobe.livecyclescala-lang.bundle)
- Adobe XFA Forms Renderer(com.adobe.livecycle.adobe-lc-forms-core)
- Adobe XFA Forms LC Connector (com.adobe.livecycle.adobe-lc-forms-lc-connector)
-
Open the logs to identify the type of error. For detailed information on logs, see logs for HTML5 forms.
-
Go to Developer Tools -> Console. Use stack trace to locate the code which is causing the error. Debug the error to resolve the issue.
Observação:
If it is scripting failure, check if the same problem occurs during the PDF rendition of the form as well. If yes, then there is a problem in the form scripting logic.
-
Enable the client side logs as mentioned at Logs for the HTML5 forms using debug option as 1-a5-b5-c5. Then render the form and click submit. Open browser debug console and check if there is an error.
-
Locate the server logs as mentioned at Logs for the HTML5 forms. Check if there was any error in server logs during submission.
-
In the exception details, search for word caused by.
The probable reason is that one or more parameters in the URL are incorrect.
Check the following parameters:
Parameter Description template The filename of the template contentRoot The path where template and associated resources reside dataRef Absolute path of the data file that is merged with the template.
Note: Path defines the absolute path of the data file.data UTF-8 encoded data bytes that are merged with the template.