Intermittent AccessDeniedException during translation project creation
This article describes how to resolve intermittent AccessDeniedException errors that occur when creating translation projects in Adobe Experience Manager as a Cloud Service.
Description description
Environment
- Adobe Experience Manager (AEM) as a Cloud Service, builds prior to 2026.6.0
Issue/Symptoms
-
Creating a translation project in AEM Sites intermittently fails.
-
The affected project remains in Draft status and doesn’t progress.
-
Successful attempts show the asynchronous job executing as the initiator, and the project completes successfully.
-
Failed attempts show the asynchronous job executing as a read-only service identity, and translation job node creation fails with
AccessDeniedException. -
Error logs contain stack traces similar to:
javax.jcr.AccessDeniedException: Access denied.javax.jcr.LoginException: Login Failure: all modules ignored
-
The issue is intermittent: some translation projects succeed, others fail, without configuration changes.
Cause
A product defect in the translation framework caused the background job to intermittently run under a read-only service identity instead of the initiating user, resulting in insufficient permissions to create the translation job node. This was corrected in AEM as a Cloud Service build 2026.6.0.
Resolution resolution
To fix the AccessDeniedException error during translation project creation, follow these steps:
- Verify the AEM as a Cloud Service build version.
- Confirm whether the affected environment is running a build earlier than 2026.6.0.
- Update to AEM as a Cloud Service build 2026.6.0 or later.
- Deploy the latest available build to all affected environments (development, stage, production).
- Follow the standard deployment and validation procedures for your organization.
- Retest translation project creation by initiating a new translation project and verifying that it progresses past Draft status and completes successfully.
- Check the logs to confirm that the async job executes as the initiator and no
AccessDeniedExceptionis thrown. - If the issue persists after updating, collect relevant logs and job execution details and contact Adobe Support for further assistance.