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

SOLVED

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

Avatar

Level 2

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.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@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. 

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

@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. 

Avatar

Level 1

@BrianKasingli We are facing the exact issue in our AEM instance. We use AEM 6.5.9.0.

 

@umashankar_d Were you able to find the root cause of this issue? How did you solve it?

Avatar

Level 1

@BrianKasingli I'm facing the same issue on our AEM 6.5.5 instance. As a temporary fix, we are clearing the script cache manually via the Felix console. Could you please let me know if there is any permanent fix to this issue? 

@umashankar_d@Ruben_Fernando1 I know it's been a while, but were you able to find the root cause of this issue? If so, how did you fix it?