Posts tagged "content"

Adobe CQ/AEM support tools available

We have recently published a package with support tools that can be useful to help diagnose issues encountered with Adobe Experience Manager.  As the tools project continues to mature, additional tools will be provided to ease the overall diagnosis and maintenance of CQ.

Overview of tools in 1st release:

  • Logs Viewer – Provides an easy way to download all CQ logs.  The tail functionality will open a new window and start tailing the log file.  Multiple log directories can be configured via Logs Tail Plugin.  The crx-quickstart/logs is used as default if configuration is not bound.  This tool can also be used with curl.  Allows you to package up all the logs in one single click making it easy to provide the logs when opening a Daycare ticket.  Detailed info here:
  • Tar PM Scan – Scans tar files and displays node path and size for each record.  This can be useful when analyzing abnormal workspace growth.  Large individual node sizes could indicate a flat hierarchy (i.e. a large child node list > 1000).  The same nodes appearing repeatedly in the scan could indicate a code issue or some other problem related to updating the same nodes repeatedly.  Detailed info here:
  • Thread Dumps Collection & Analysis – Takes thread dumps at regular intervals and saves them in a file under crx-quickstart/threads.  The page will also display a list of links to existing thread dump files.  The tool can use jstack, if it is installed on the system, or JVM MBean.  Detailed info here:
  • Content Compare & Import – Used to compare and import content differences from one CQ instance to another CQ instance.  This helps to ensure consistency across servers.  Detailed info here:

Download and install

The tools are supported for use with CQ5.5, AEM5.6 and later versions.  Here are the instructions to download and install the support tools:

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 8.8/10 (11 votes cast)

LiveCycle ES: CONTENT INTEGRITY ERROR using Content Services


If you are working with Content Services ES you may notice the following exception in the log files:

ERROR [org.alfresco.repo.admin.ConfigurationChecker] CONTENT INTEGRITY ERROR: System content not found in content store.
ERROR [org.alfresco.repo.admin.ConfigurationChecker] Ensure that the 'dir.root' property is pointing to the correct data location.
ERROR [org.springframework.web.context.ContextLoader] Context initialization failed
org.alfresco.error.AlfrescoRuntimeException: Ensure that the 'dir.root' property is pointing to the correct data location.
 at org.alfresco.repo.admin.ConfigurationChecker.check(
 at org.alfresco.repo.admin.ConfigurationChecker.access$000(
    at org.alfresco.repo.admin.ConfigurationChecker$1.execute(
    at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(
    at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(
    at org.alfresco.repo.admin.ConfigurationChecker.onBootstrap(
    at org.alfresco.util.AbstractLifecycleBean.onApplicationEvent(


This exception will occur when the data in the database is no longer synchronized with the data in the file system data store.  Both must remain synchronized at all times, otherwise data loss will occur.  It is part of the maintenance tasks to ensure that the following items are backed up regularly at the same time:

  • GDS document store (file system/network location)
  • Content Services data store (file system/network location)
  • Database schema

This information is described in detail with instructions in the LiveCycle Administration guide:

If the data in the Content Services data store is no longer synchronized with the data in the database, then this exception is thrown, as data integrity has been compromised.  This can happen if another server/user has access to the file data store and makes changes, or if the data in the database is modified by another user/application.

It can also occur while performing configuration changes to your LiveCycle installation if the deployment of these changes quits unexpectedly leaving the database and local data stores out-of-synch.


To resolve this situation you will need to restore the components above from the last valid configuration.

If this is a fresh installation of LC content services, then you can drop the Content Services tables in the database, delete any content in the data store, and re-try the deployment. The following technote describes which tables you need to drop (i.e. it gives you the SQL commands to run):

The Content Services tables in the database get created while the adobe-contentservices.ear file is being deployed (not during database initialization).  Once you have cleaned the DB and the data store, simply re-start the application server with the content services EAR file, and the tables will be re-created.

reference: (182870106)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.5/10 (2 votes cast)