AEM 6.5 upgrade issue | Community
Skip to main content
M
mattiam68727143
February 3, 2020
Solved

AEM 6.5 upgrade issue

  • February 3, 2020
  • 3 replies
  • 3355 views

We trying to upgrade from AEM 6.3.2.0 to 6.5 but we are having some issue regarding one specific step.
We can not find the PreUpgradeTasks inside JMX Console as described in here: https://docs.adobe.com/content/help/en/experience-manager-65/deploying/upgrading/pre-upgrade-maintenance-tasks.html#install-configure-run-pre-upgrade-tasks

 

We also tried to install (invane) PRE-UPGRADE-PACKAGE-CQ63 package.

Has anyone faced the similar issue? How can we solve this problem and complete the upgrade process?
thank all

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 mattiam68727143

Hi @nirmal_jose 

 

the problem was related to a wrong version of com.google.gson imported by com.day.cq.pre-upgrade-tasks which was causing PreUpgradeTasksMBean component be in a satisfied state instead of an active state.

 

Thanks for your support.

3 replies

Nirmal_Jose
Adobe Employee
Nirmal_JoseAdobe Employee
Adobe Employee
February 3, 2020

Hi,

 

Are you able to find the preupgrade component at /system/console/configMgr/com.adobe.aem.upgrade.prechecks.mbean.impl.PreUpgradeTasksMBeanImpl

 

Once you have that one, we can get the PreUpgrade tasks at /system/console/jmx/com.adobe.aem.upgrade.prechecks%3Atype%3DPreUpgradeTasks

    M
    mattiam68727143Author
    February 3, 2020

    Hi @nirmal_jose,

     

    thank you for helping.

    Yes, I'm able to find the preupgrade component under /system/console/configMgr:

     

     

    But once I try accessing PreUpgrade tasks via URL it gives me 404.

      Nirmal_Jose
      Adobe Employee
      Nirmal_JoseAdobe Employee
      Adobe Employee
      February 3, 2020
      everything seems to be in place. Are you using admin user itself ?
      M
      mattiam68727143AuthorAccepted solution
      February 4, 2020

      Hi @nirmal_jose 

       

      the problem was related to a wrong version of com.google.gson imported by com.day.cq.pre-upgrade-tasks which was causing PreUpgradeTasksMBean component be in a satisfied state instead of an active state.

       

      Thanks for your support.

      Nirmal_Jose
      Adobe Employee
      Nirmal_JoseAdobe Employee
      Adobe Employee
      February 4, 2020
      good to know, thanks
      Terms & ConditionsAccessibility statement

      Loading footer...