AEM Forms not loading after LTS upgrade in Author and Publish environments
This article provides steps to resolve an issue where AEM Forms are present in the repository but don’t load or appear in the AEM Forms UI on Author and Publish environments following an AEM Long-Term Support (LTS) upgrade.
Description description
After performing an AEM LTS upgrade, forms are visible in CRX/DE but don’t appear or load in the AEM Forms UI on either the Author or Publish environments. Attempts to access affected forms results in errors such as javax.servlet.jsp.JspException: Error while executing script formBody.jsp and Apache Sling errors indicating the request can’t be served. This issue can prevent testing and business activities that rely on AEM Forms.
Environment
Adobe Experience Manager (AEM) Forms, all supported versions.
Symptoms
- Forms are present in the repository (CRX/DE) but don’t appear in the AEM Forms UI.
- Forms fail to load on both Author and Publish environments.
- Error messages referencing
formBody.jspor Apache Sling are displayed when accessing forms.
Cause
Content changes introduced by the LTS Modernizer Content Transformer tool during the AEM LTS upgrade affects AEM Forms compatibility, causing forms to become invisible or fail to load.
Resolution resolution
Follow the steps below to resolve the issue:
- Review recent AEM LTS upgrade activities, especially any content transformation steps performed using the LTS Modernizer Content Transformer tool.
- Check for changes in the repository content that have affected AEM Forms compatibility or visibility.
- If forms are missing or not loading, restore the affected Author and Publish environments to a previously healthy state using a backup taken before the upgrade.
- After restoration, validate that forms are visible in the AEM Forms UI and load as expected on both Author and Publish environments.
- For future upgrades, perform additional validation of AEM Forms compatibility before and after content transformation, and establish rollback decision points earlier in the upgrade process to minimize impact if issues are detected.