Expand my Community achievements bar.

Join us in celebrating the outstanding achievement of our AEM Community Member of the Year!
SOLVED

Error while migrating from AEM 6.3 to 6.5

Avatar

Level 5

Hi Everyone,

 

I have a system running on AEM 6.3.3.8 and I wanted to migrate it to 6.5. I want to keep every setting as-is. So, I am performing an in-place upgrade. Every log was OK except the below error - lines from upgrade.log file

*INFO* [FelixStartLevel] com.adobe.cq.upgradesexecutor.Activator UPGRADE TASK STARTING: CQ63MonitoringDashboardsConfigUpdate
*INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq63.CQ63MonitoringDashboardsConfigUpdate Migrating custom dashboard configs from /libs and /apps to /conf
*INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq63.CQ63MonitoringDashboardsConfigUpdate Migrating custom dashboard configs failed
*ERROR* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq63.CQ63MonitoringDashboardsConfigUpdate migration failed
javax.jcr.nodetype.ConstraintViolationException: No matching property definition: sling:configCollectionInherit = true
at org.apache.jackrabbit.oak.jcr.delegate.NodeDelegate.setProperty(NodeDelegate.java:528) [org.apache.jackrabbit.oak-jcr:1.10.2]
at org.apache.jackrabbit.oak.jcr.session.NodeImpl$35.perform(NodeImpl.java:1387) [org.apache.jackrabbit.oak-jcr:1.10.2]
at org.apache.jackrabbit.oak.jcr.session.NodeImpl$35.perform(NodeImpl.java:1374) [org.apache.jackrabbit.oak-jcr:1.10.2]
at org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:207) [org.apache.jackrabbit.oak-jcr:1.10.2]
at org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112) [org.apache.jackrabbit.oak-jcr:1.10.2]
at org.apache.jackrabbit.oak.jcr.session.NodeImpl.internalSetProperty(NodeImpl.java:1374) [org.apache.jackrabbit.oak-jcr:1.10.2]
at org.apache.jackrabbit.oak.jcr.session.NodeImpl.setProperty(NodeImpl.java:436) [org.apache.jackrabbit.oak-jcr:1.10.2]
at com.day.cq.compat.codeupgrade.impl.cq63.CQ63MonitoringDashboardsConfigUpdate.doUpgrade(CQ63MonitoringDashboardsConfigUpdate.java:152) [com.day.cq.cq-compat-codeupgrade:1.7.100]
at com.day.cq.compat.codeupgrade.impl.AbstractCodeUpgradeTask.run(AbstractCodeUpgradeTask.java:65) [com.day.cq.cq-compat-codeupgrade:1.7.100]
at com.adobe.cq.upgradesexecutor.Activator.runUpgradeTasks(Activator.java:376) [com.day.cq.cq-upgrades-executor:2.0.8]
at com.adobe.cq.upgradesexecutor.Activator.finishUpgradeExecution(Activator.java:244) [com.day.cq.cq-upgrades-executor:2.0.8]
at com.adobe.cq.upgradesexecutor.Activator.start(Activator.java:189) [com.day.cq.cq-upgrades-executor:2.0.8]
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:698)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:2402)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2308)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1539)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.lang.Thread.run(Thread.java:748)

 

Is there any fix, I can apply for this scenario? Any suggestion would be appreciated!

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 4

Hi @RitendraS11 ,

 

There are few structural changes between 6.3(6.4) and 6.5.

in terms of configurations, moved from /etc to /conf where applicable, especially for templates, policies, and designs.

Please check this https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/rest...

 

Thanks,

Raju.

 

View solution in original post

2 Replies

Avatar

Correct answer by
Level 4

Hi @RitendraS11 ,

 

There are few structural changes between 6.3(6.4) and 6.5.

in terms of configurations, moved from /etc to /conf where applicable, especially for templates, policies, and designs.

Please check this https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/rest...

 

Thanks,

Raju.

 

Avatar

Level 9

Hi@RitendraS11 

 

Maybe when you're trying to migrate the monitoring dashboard it is expecting to have sling:configCollectionInherit = true property available in /apps. Like in this example:

https://github.com/heervisscher/htl-examples/blob/master/ui.apps/src/main/content/jcr_root/apps/sett...

Maybe you can manually add it before triggering your migration and see how it goes.