Hi Adobe Community,
We are experiencing an issue with the "Manage Publication" functionality in Adobe Experience Manager (AEM) 6.5 with Service Pack 6.5.16.0. When attempting to schedule content publication, the process gets stuck after the scheduling step, displaying a blank screen instead of the expected page.
No error messages appear in the server logs, but I noticed an "Uncaught TypeError" in the browser console (screenshot attached). I have also logged in as an admin user and checked the logs, but there are no clear error indicators.
This issue is disrupting our content workflow. Has anyone encountered a similar problem? Any insights or troubleshooting suggestions would be greatly appreciated!
Thanks in advance for your help!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
The error message
Uncaught TypeError getReferences(...).success is not a function
suggests that the JavaScript code for the Manage Publication functionality is expecting a callback method ("success") that isn't available. This can occur when there's an API mismatch—possibly due to a change in how asynchronous responses are handled (for example, with jQuery or a related client library). Since you're on AEM 6.5 SP6.5.16.0, it's possible that either an update or a customization has led to this inconsistency.
TL;DR
The error points to a JavaScript API compatibility issue. Reviewing the client library versions, checking for customizations, and comparing them with a clean AEM instance should help pinpoint the root cause. If the issue is inherent to AEM v6.5.16.0, reaching out to Adobe Support or checking for an available hotfix may be necessary.
Long version - Troubleshooting Steps
The error message
Uncaught TypeError getReferences(...).success is not a function
suggests that the JavaScript code for the Manage Publication functionality is expecting a callback method ("success") that isn't available. This can occur when there's an API mismatch—possibly due to a change in how asynchronous responses are handled (for example, with jQuery or a related client library). Since you're on AEM 6.5 SP6.5.16.0, it's possible that either an update or a customization has led to this inconsistency.
TL;DR
The error points to a JavaScript API compatibility issue. Reviewing the client library versions, checking for customizations, and comparing them with a clean AEM instance should help pinpoint the root cause. If the issue is inherent to AEM v6.5.16.0, reaching out to Adobe Support or checking for an available hotfix may be necessary.
Long version - Troubleshooting Steps
Views
Likes
Replies