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

"Runtime extension is not available: use" error after new package deployment

Avatar

Avatar
Give Back
Level 1
umashankar_d
Level 1

Likes

0 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Give Back
Ignite 1
Validate 1
View profile

Avatar
Give Back
Level 1
umashankar_d
Level 1

Likes

0 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Give Back
Ignite 1
Validate 1
View profile
umashankar_d
Level 1

23-04-2020

Hi Team,

After deploying new packages in the "author", I am getting the below error very often, when I try accessing the custom application pages:

 

image1.png

 

 

 

 

 

 

 

 

 

 

 

Also, when I encounter the above error in my custom application pages, I get the same error while trying to access some of the AEM pages as well (like, "/welcome.html" or "/sites.html" or "/start.html"). In many instances, I am getting the same error in "publish" as well (after replicating the pages).

This was initially a showstopper, until I came up with a solution for this. After clearing the script cache (accessible through  <server>/system/console/scriptcache), the pages load fine.

 

image.png

Now my question, I want to know the root cause for this issue, so that I can fix it on a permanent basis. This issue is absolutely erratic in nature.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

644 likes

Total Posts

605 posts

Correct Reply

239 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

644 likes

Total Posts

605 posts

Correct Reply

239 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
BrianKasingli
MVP

03-07-2020

@umashankar_d 

AEM typically will automatically clear HTML and JS script caches after a deployment. Only with special cases, /system/console/scriptcache could be used to manually clear such files.

Let me know if this happens to you again. 

Answers (0)