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
BedrockMission!

Learn More

View all

Sign in to view all badges

OOTB Navigation component model class error

Avatar

Avatar
Validate 25
Level 4
varuns46785756
Level 4

Likes

22 likes

Total Posts

146 posts

Correct Reply

2 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile

Avatar
Validate 25
Level 4
varuns46785756
Level 4

Likes

22 likes

Total Posts

146 posts

Correct Reply

2 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile
varuns46785756
Level 4

16-09-2019

Hi All,

I am using OOTB navigation component on my local AEM6.4 instance and its working fine as per the behavior but when I am using the same component on my client AEM6.4 instance( DEV and all instances) , I am getting model class missing error:

1833803_pastedImage_0.png

1833804_pastedImage_1.png

As compared with my client machine AEM6.4 and my local machine AEM6.4, I am using SP6.4.2 and acs-aem-commons-content-3.16.1-SNAPSHOT.zip on my local machine but both the package were not available on client machine. I have tired to install both the package also even after that I am getting the same error.

Please suggest which supporting package is missing here for navigation component.

thanks

Replies

Avatar

Avatar
Give Back 5
Employee
yanirac19051392
Employee

Likes

20 likes

Total Posts

38 posts

Correct Reply

7 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 5
View profile

Avatar
Give Back 5
Employee
yanirac19051392
Employee

Likes

20 likes

Total Posts

38 posts

Correct Reply

7 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 5
View profile
yanirac19051392
Employee

17-09-2019

Try and recompile your libraries [1], if not perhaps rebuild your bundle. 

[1] How to force a recompilation of all Sling scripts jsps, java, and sightly in AEM 6.4

Avatar

Avatar
Contributor
Employee
hamidk92094312
Employee

Likes

101 likes

Total Posts

240 posts

Correct Reply

38 solutions
Top badges earned
Contributor
Shape 1
Ignite 1
Give Back 50
Give Back 5
View profile

Avatar
Contributor
Employee
hamidk92094312
Employee

Likes

101 likes

Total Posts

240 posts

Correct Reply

38 solutions
Top badges earned
Contributor
Shape 1
Ignite 1
Give Back 50
Give Back 5
View profile
hamidk92094312
Employee

17-09-2019

Just adding to what Yanira mentioned you can use Diff tools to verify if there is any config changes between the working and non-working instances: AEM Tools for environment comparison

Avatar

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,260 likes

Total Posts

3,149 posts

Correct Reply

886 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,260 likes

Total Posts

3,149 posts

Correct Reply

886 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile
Arun_Patidar
MVP

17-09-2019

Please check if core component bundle is active state or not? There could be possibility you have multiple version core components jar.

Avatar

Avatar
Give back 300
MVP
Gaurav-Behl
MVP

Likes

243 likes

Total Posts

1,145 posts

Correct Reply

281 solutions
Top badges earned
Give back 300
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Give back 300
MVP
Gaurav-Behl
MVP

Likes

243 likes

Total Posts

1,145 posts

Correct Reply

281 solutions
Top badges earned
Give back 300
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile
Gaurav-Behl
MVP

18-09-2019

Compare runmode of local vs DEV/other env.

Refer - Regarding using core components with nosamplecontent runmode, if runmode is the issue