Identifier com.adobe.cq.wcm.core. cannot be correctly instantiated by the Use API | Community
Skip to main content
Cr9home
February 27, 2018
Solved

Identifier com.adobe.cq.wcm.core. cannot be correctly instantiated by the Use API

  • February 27, 2018
  • 5 replies
  • 12260 views

Hi guys,

I am new to AEM and I'm following this tutorial for understanding.

Adobe Experience Manager Help | Getting Started with AEM Sites - WKND Tutorial

After I've finish chapter 2 I should have 1 page ready but I get this error instead.

Can you help me understanding the problem ?
Thank you !

Best answer by Daniel_Gordon

The error indicates that Core Components Page model is not registered correctly. A couple of things to check:

1. Verify Local AEM Instance setup:

2. Verify that Core Components 2.0 have been uploaded and installed by navigating to CRX Pack Manager (http://localhost:4502/crx/packmgr/index.jsp)

3. Look in the OSGi console (http://localhost:4502/system/console/bundles ) for the Core WCM Components Core bundle

5 replies

smacdonald2008
February 27, 2018

Is the OSGi bundle in an Active state on the server?

Daniel_Gordon
Adobe Employee
Daniel_GordonAdobe EmployeeAccepted solution
Adobe Employee
February 27, 2018

The error indicates that Core Components Page model is not registered correctly. A couple of things to check:

1. Verify Local AEM Instance setup:

2. Verify that Core Components 2.0 have been uploaded and installed by navigating to CRX Pack Manager (http://localhost:4502/crx/packmgr/index.jsp)

3. Look in the OSGi console (http://localhost:4502/system/console/bundles ) for the Core WCM Components Core bundle

Daniel_Gordon
Adobe Employee
Adobe Employee
February 27, 2018

Another user had a similar issue and it was because the version of Java was not 1.8. More details here: Unresolved dependencies on fresh AEM 6.3.1 · Issue #12 · Adobe-Marketing-Cloud/aem-guides-wknd · GitHub

Cr9home
Cr9homeAuthor
February 28, 2018

You are a life saver !!!

I found out that the Core WCM Components Core bundle was not running.

Started that and my problem is fixed.

sindhug14537977
October 11, 2018

we have the verison 1.0.2.

is it mandatory to have version 2 to resolve this issue.

we didn't install any feature packs too. please let me know if this is mandatory.

Thank You!