HTTP 500 error when creating an LCA archive in AEM Forms due to a missing Commons BeanUtils bundle

Last update: June 27, 2026

Creating an LCA archive in Adobe Experience Manager Forms can fail with an HTTP 500 error when the Commons BeanUtils OSGi bundle is missing or inactive after a package deployment. When this bundle is absent, dependent Forms bundles stay in the INSTALLED state with unresolved package dependencies, and the Forms archive servlet does not register. To fix the issue, restore the correct Commons BeanUtils bundle from a healthy environment so the dependent bundles resolve and move to the ACTIVE state.

Description description

Environment

Adobe Experience Manager Forms 6.5
Service Pack and Forms Add-On installed (all platforms)

Issue/Symptoms

LCA archive creation in Workbench fails and returns an HTTP 500 error.
In the OSGi console (/system/console/bundles), multiple bundles are stuck in the INSTALLED state.
The Commons BeanUtils bundle is missing or not active.
The Forms archive servlet does not register.
Dependent bundles show unresolved package dependencies, such as:

com.adobe.fd.workspace.client.types,version=[ 2.6,3) -- Cannot be resolved
        com.adobe.fd.workspace.exceptions,version=[ 2.6,3) -- Cannot be resolved
        com.adobe.fd.workspace.service.api,version=[ 2.6,3) -- Cannot be resolved
        com.adobe.fd.workspace.step.service.client.type,version=[ 2.6,3) -- Cannot be resolved

Root cause:

The Commons BeanUtils bundle was removed or overwritten during a package deployment. Because the Forms bundles depend on the packages that Commons BeanUtils exports, the dependent bundles cannot resolve and remain in the INSTALLED state. As a result, the Forms archive servlet does not register and LCA archive creation fails with an HTTP 500 error.

Resolution resolution

To fix the issue:

Sign in to the affected environment’s OSGi console at /system/console/bundles.
Confirm that the Commons BeanUtils bundle is missing or not active, and that the dependent bundles are in the INSTALLED state.
Access a healthy environment (such as a staging or test environment) running the same AEM Forms version.
Locate the Commons BeanUtils bundle in /system/console/bundles.
Note the exact bundle version (for example, 1.8.2) and symbolic name.
Download or copy the corresponding bundle JAR file from the healthy environment.
In the affected environment, go to /system/console/bundles and select Install/Update.
Upload and install the Commons BeanUtils bundle JAR, then wait for the bundle to become active.
Confirm that all previously unresolved bundles move to the ACTIVE state automatically.
Test LCA archive creation in Workbench to confirm the HTTP 500 error no longer occurs.
(Optional) Review recent package installations to identify whether a package removed or overwrote the Commons BeanUtils bundle. If so, redeploy the package correctly or reinstall the missing bundle after package deployment.

recommendation-more-help

experience-cloud-kcs-help-kbarticles