JCR Installation not working for embedded package/bundle due to pauseinstallation node | Community
Skip to main content
A
atikjain
Level 1
January 20, 2026
Question

JCR Installation not working for embedded package/bundle due to pauseinstallation node

  • January 20, 2026
  • 1 reply
  • 24 views

Embedded packages or bundles are not getting installed due to pauseinstallation node getting created at below location /system/sling/installer/jcr/pauseInstallation.

How to identify why the node is getting created under this directory?

 

 

    1 reply

    konstantyn_diachenko
    Community Advisor
    konstantyn_diachenkoCommunity Advisor
    Community Advisor
    January 20, 2026

    Hi ​@atikjain ,

    pauseInstallation is created by the Sling JCR Installer when it pauses installations due to a detected problem. It is not the root cause, but a safeguard.

    Common causes

    1. Bundle version downgrade (most common)
      Deploying the same or lower bundle version than what is already installed. Sling does not allow downgrades.

    2. Failed or unresolved bundle
      Missing OSGi dependencies or invalid imports prevent a bundle from starting.

    3. Corrupt or interrupted deployment
      Partial uploads or broken JARs can pause the installer.

    4. Installer stuck after a failure
      Old pause state remains after the original issue was fixed.

    How to identify the issue

    • Check bundle status and versions /system/console/bundles

    • Review Sling installer logs /system/console/slinglog

    • Look for unresolved or inactive bundles

    Once you fix a root cause, remove this node.

    Similar thread: 

     

    Kostiantyn Diachenko, Community Advisor, Certified Senior AEM Developer, creator of free AEM VLT Tool, maintainer of AEM Tools plugin.
    Terms & ConditionsAccessibility statement

    Loading footer...