The following document describes troubleshooting for Dynamic Media running dynamicmedia_scene7 run mode.
Ensure that Dynamic Media has been set up properly by doing the following:
Start up command contains the -r dynamicmedia_scene7
runmode argument.
Any AEM 6.4 cumulative fix packs (CFPs) have been installed first before any available Dynamic Media Feature Packs.
Optional Feature Pack 18912 is installed.
This optional feature pack is for FTP support or if you are migrating assets to Dynamic Media from Dynamic Media Classic (Scene7).
Navigate to the Cloud Services user interface and confirm that the provisioned account appears under Available Configurations.
Ensure that the Dynamic Media Asset Activation (scene7) replication agent is enabled.
This replication agent is found under Agents on Author.
The following are some general tips and tricks for all assets.
The following asset properties can be reviewed in CRXDE Lite to confirm the successful synchronization of the asset from AEM to Dynamic Media:
Property | Example | Description |
---|---|---|
<object_node>/jcr:content/metadata/dam:scene7ID |
a|364266 |
General indicator that node is linked to Dynamic Media. |
<object_node>/jcr:content/metadata/dam:scene7FileStatus |
PublishComplete or error text | Status of upload of asset to Dynamic Media. |
<object_node>/jcr:content/metadata/dam:scene7File |
myCompany/myAssetID |
Must be populated in order to generate URLs to remote asset of Dynamic Media. |
<object_node>/jcr:content/dam:lastSyncStatus |
success or failed:<error text> |
Synchronization status of sets (spin sets, image sets, and so on), image presets, viewer presets, image map updates for an asset, or images that were edited. |
Synchronization errors and issues are logged in error.log
(AEM server directory /crx-quickstart/logs/
). Sufficient logging is available to determine the root cause of most issues, however you can increase the logging to DEBUG on the com.adobe.cq.dam.ips
package through the Sling Console (http://localhost:4502/system/console/slinglog) to gather more information.
Before performing a Move, Copy, or Delete operation, do the following:
<object_node>/jcr:content/metadata/dam:scene7ID
value exists before performing move, copy, or delete operations.https://<server>/crx/de/index.jsp#/etc/dam/presets/viewer/testpreset/jcr%3Acontent/metadata
value exists before performing move, copy, or delete operations.When replacing an existing Dynamic Media asset (same name and location), you have the option to keep both assets or replace or create a version:
Keeping both will create a new asset with a unique name for the published asset URL. For example, image.jpg is the original asset and image1.jpg is the newly uploaded asset.
Creating a version is not supported in Dynamic Media - Scene7 mode delivery. The new version replaces the existing asset in delivery.
If you are having issues with images and sets, see the following troubleshooting guidance.
Issue | How to debug | Solution |
Cannot access copy URL/Embed button in asset detail view |
|
Refresh page/navigate to another page and come back (side rail JSP needs to be recompiled) If that does not work:
|
Asset selector in set editor stuck in perpetual loading | Known issue to be fixed in 6.4 |
Close the selector and reopen it. |
Select button is not active after selecting an asset as part of editing a set |
Known issue to be fixed in 6.4
|
Click on another folder in the Asset Selector first and go back to select the asset. |
Carousel hotspot moves around after switching between slides | Check that all slides are the same size. |
Use only images with the same size for the carousel. |
Image does not preview with the Dynamic Media viewer | Check that the asset contains |
Check that all assets have finished processing. |
Uploaded asset does not show in asset selector | Check asset has property |
Check that all assets have finished processing. |
Banner on card view shows New when asset has not started processing | Check asset jcr:content > dam:assetState = if unprocessed it was not picked up by the workflow. |
Wait until asset is picked up by workflow. |
Images or sets do not display the viewer URL or embed code | Check if the viewer preset has been published. | Go to Tools > Assets > Viewer Presets and publish the viewer preset. |
If you are having issues with video, see the following troubleshooting guidance.
Issue | How to debug | Solution |
Video cannot be previewed |
|
|
Video is not encoded |
|
|
Video processing takes too long | To determine if video encoding is still in progress or if it has entered a failure state:
|
|
Video rendition missing | When video is uploaded, but there are no encoded renditions:
|
|
If you are having issues with viewers, see the following troubleshooting guidance.