"Runtime extension is not available: use" error after new package deployment | Community
Skip to main content
umashankar_d
umashankar_d
Level 2
April 24, 2020
Solved

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

  • April 24, 2020
  • 2 replies
  • 3084 views

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:

 

 

 

 

 

 

 

 

 

 

 

 

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.

 

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by BrianKasingli

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

2 replies

BrianKasingli
Community Advisor and Adobe Champion
BrianKasingliCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
July 3, 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. 

    R
    Ruben_Fernando1
    October 7, 2021

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

    S
    sgad786
    New Member
    November 22, 2022

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

    Terms & ConditionsAccessibility statement

    Loading footer...