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(ConfigurationChecker.java:312) at org.alfresco.repo.admin.ConfigurationChecker.access$000(ConfigurationChecker.java:72) at org.alfresco.repo.admin.ConfigurationChecker$1.execute(ConfigurationChecker.java:178) at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:278) at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:227) at org.alfresco.repo.admin.ConfigurationChecker.onBootstrap(ConfigurationChecker.java:182) at org.alfresco.util.AbstractLifecycleBean.onApplicationEvent(AbstractLifecycleBean.java:62)
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.