"20.10.2024 07:44:04.286 *ERROR* [qtp1932271856-175] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.
20.10.2024 07:44:04.288 *ERROR* [qtp1932271856-89] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
20.10.2024 07:44:04.288 *ERROR* [qtp1932271856-89] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies. "
1.Stop the AEM instance.
2.Delete the following files:
/publish/crx-quickstart/repository/segmentstore/repo.lock
/publish/crx-quickstart/launchpad/felix/cache.lock
/publish/crx-quickstart/repository/index
/crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit
Restart the AEM instance.
We could access the configuration Manager with admin credentials in browser. If we cross verified the Granite Authentication Handler, that bundle is active only.
We noticed the bundle "Adobe Experience Manager Graph QL for Content Fragment scq-dam-cfm-Graph QL" is in installed state and we couldn't change that to active state.
Is there any relationship between these error and this Graph QL bundle? can anyone suggest solution for this issue?
Views
Replies
Total Likes
Hi @GVijikala ,
Yes, it might be due to Adobe Experience Manager Graph QL for Content Fragment scq-dam-cfm-Graph QL
You can expand and check which dependency is not satisfied and add accordingly.
Thanks
Hi Mukesh,
I verified that as well, even in bundles i could not see the missing dependencies. Rather than, if i tried to activate the bundle i could see below error message in sling logs.
21.10.2024 06:10:46.468 *ERROR* [FelixDispatchQueue] cq-dam-cfm-graphql FrameworkEvent ERROR (org.osgi.framework.BundleException: Unable to resolve cq-dam-cfm-graphql [618](R 618.2): missing requirement [cq-dam-cfm-graphql [618](R 618.2)] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.ui.wcm.commons)(version>=1.1.0)(!(version>=2.0.0))) Unresolved requirements: [[cq-dam-cfm-graphql [618](R 618.2)] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.ui.wcm.commons)(version>=1.1.0)(!(version>=2.0.0)))])
org.osgi.framework.BundleException: Unable to resolve cq-dam-cfm-graphql [618](R 618.2): missing requirement [cq-dam-cfm-graphql [618](R 618.2)] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.ui.wcm.commons)(version>=1.1.0)(!(version>=2.0.0))) Unresolved requirements: [[cq-dam-cfm-graphql [618](R 618.2)] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.ui.wcm.commons)(version>=1.1.0)(!(version>=2.0.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.lang.Thread.run(Thread.java:750)
21.10.2024 06:10:46.468 *INFO* [FelixStartLevel] com.adobe.cq.remotedam.cq-remotedam-commons BundleEvent STARTING
In dependencies,
I could see the package installed.
Hi @GVijikala ,
Error suggest cannot resolve com.adobe.cq.ui.wcm.commons
, could you please verify below
Verify Bundle Status:
/system/console/bundles
).com.adobe.cq.ui.wcm.commons
is installed and look at its version.Check Required Version:
com.adobe.cq.ui.wcm.commons
is:
Also you may restart or refresh the bundle as well as you may try in incognito as well https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-5-osgi-configuration...
Thanks
Try to delete this folder, crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit
After that also delete the org.apache.sling.jcr.repoinit.RepositoryInitializer~my-project.cfg.json OSGI config from your project.
I have deleted this folder. Then it is giving this error message.
@GVijikala Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies