Hi,is the content path different for each region?Could you not create separate templates for each region that extend a common component, this would be cleaner I think. Only need a single design as well.You get 3 instead of 1 template, but since they all extend the same component, it is pretty straig...

When you deploy your package to AEM, tail the error.log file and see if any errors are thrown when your bundle is started.Regards,Opkar

There seems to be some details on this issue online, looks like your java code may need to be updated. What version of AEM are you migrating from?https://issues.apache.org/jira/browse/FELIX-4586http://apache-sling.73963.n3.nabble.com/jira-Created-SLING-3792-Fields-in-ResourceAccessSecurityTracker-mu...

Hi Rama,as has been mentioned, with the TarMK farm, you are running multiple separate Publish instances all independently kept in synch by the author instance.In front of you publish instances, you have your web server with the dispatcher module(usually in a 1 to 1 relationship with a publish instan...

Hi,In the upgrade docs [1] the in place upgrade requires a workflow purge. It looks like the node in you error log has become corrupt. If you did not run the workflow purge before upgrading, and running the upgrade again is not possible(taking into account the known issues and the cleanup tasks) you...

What version of crx2oak-1.0.x did you use?Looks like you may have to contact daycare about this issue.regards,Opkar

Hi,if you unable to rerun the upgrade, performing all the cleanup tasks and applicable kwon issue fixes on a copy of your original 5.x AEM instance. Then I suggest you contact daycare to help with the current issue.Regards,Opkar

The error is a a symptom is an symptom of an underlying issue with the repository. Most likely you will have an exception during startup. Please check your logs and identify the root cause. Post the error so we can see what the issue is.Regards,Opkar

It could be there is an old Job that is referencing the workflow instance in the error. Daycare will be able to help with this.

You don't have to enable DEBUG, the exception will be in the standard settings for error.log