Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

[AEM Gems Webinar] Accelerating Experience Manager as a Cloud Service development with Rapid Development Environments
SOLVED

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

Avatar

Level 1

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.

Screen Shot 2018-02-27 at 20.55.36.png

Can you help me understanding the problem ?
Thank you !

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

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)

2018-02-27 at 3.11 PM.png

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

2018-02-27 at 3.08 PM.png

View solution in original post

5 Replies

Avatar

Correct answer by
Employee Advisor

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)

2018-02-27 at 3.11 PM.png

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

2018-02-27 at 3.08 PM.png

Avatar

Level 1

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.

Avatar

Level 2

1593843_pastedImage_0.png

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!