Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

upgrade to aem 6.5.17 errors

Avatar

Level 7

i am seeing below issues after aem instance upgrade to 6.5.17

 

 

 

 

14.09.2023 13:50:00.341 *ERROR* [FelixStartLevel] ERROR: Bundle '632' Error starting jcrinstall:/libs/fd/channelcore/install/channel-core-impl-2.0.84.jar (org.osgi.framework.BundleException: Unable to resolve com.adobe.aemfd.channelcore-channel-core-impl [632](R 632.0): missing requirement [com.adobe.aemfd.channelcore-channel-core-impl [632](R 632.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.wcm.msm.api)(version>=5.9.0)(!(version>=5.11.0))) Unresolved requirements: [[com.adobe.aemfd.channelcore-channel-core-impl [632](R 632.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.wcm.msm.api)(version>=5.9.0)(!(version>=5.11.0)))])
org.osgi.framework.BundleException: Unable to resolve com.adobe.aemfd.channelcore-channel-core-impl [632](R 632.0): missing requirement [com.adobe.aemfd.channelcore-channel-core-impl [632](R 632.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.wcm.msm.api)(version>=5.9.0)(!(version>=5.11.0))) Unresolved requirements: [[com.adobe.aemfd.channelcore-channel-core-impl [632](R 632.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.wcm.msm.api)(version>=5.9.0)(!(version>=5.11.0)))]
	at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368)
	at org.apache.felix.framework.Felix.startBundle(Felix.java:2281)
	at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1539)
	at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
	at java.base/java.lang.Thread.run(Thread.java:829)
14.09.2023 13:50:08.773 *ERROR* [FelixStartLevel] ERROR: Bundle '690' Error starting jcrinstall:/libs/fd/signatures/install/adobe-aemfd-signatures-6.0.30.jar (java.lang.NoClassDefFoundError: org/bouncycastle/jce/provider/BouncyCastleProvider)
java.lang.NoClassDefFoundError: org/bouncycastle/jce/provider/BouncyCastleProvider
	at com.adobe.fd.signatures.activator.Activator.start(Activator.java:34)
	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.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.ClassNotFoundException: org.bouncycastle.jce.provider.BouncyCastleProvider not found by adobe-aemfd-signatures [690]
	at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1597)
	at org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
	at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1982)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
	... 7 more

 

 

 


 
sreenu539_0-1694725272665.png

 

seeing a flash of "html resource rendered" dump while loading pages on author.

 

Has anyone encountered these issues? 

 

Thanks,

Sri

 

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hello @sreenu539,

 

I managed to upgrade the AEM version to 6.5.17 without any issue.

Please make sure you follow the steps recommended by Adobe: https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/service-pack/6.5.17.html...

 

Thanks 

View solution in original post

4 Replies

Avatar

Correct answer by
Community Advisor

Hello @sreenu539,

 

I managed to upgrade the AEM version to 6.5.17 without any issue.

Please make sure you follow the steps recommended by Adobe: https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/service-pack/6.5.17.html...

 

Thanks 

Avatar

Community Advisor

Hi @sreenu539 ,

There are some dependency in pom which are not compatible with uber 6.5.17. Please make sure there are no conflict among them. Make sure to updtae the dependency one by one.

Thanks
Tarun

Avatar

Community Advisor

Did you upgraded the aem-Uber jar as well to the 6.5.18 with service pack upgrade?

it seems your project jar is looking for the older version of the com.day.cq.wcm.msm.api jar 

Avatar

Administrator

@sreenu539 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.



Kautuk Sahni