AEM 6.0 to 6.2 Upgrade Issues

[a_lex_]

Hello,

Having an issue upgrading author/publisher instances that are running AEM 6.0SP3 to AEM 6.2. I have run through the Adobe upgrade guide multiple times, and finally get to the point where I run the upgrade with

java -jar aem-quickstart-6.2.0.jar -r author,crx3,crx3tar,nosamplecontent

java -jar aem-quickstart-6.2.0.jar -r publish,crx3,crx3tar,nosamplecontent

However, after the instance starts post-upgrade (with new 6.2 splash screen), many of the AEM bundles are not updated. There are many errors about missing dependencies in the logs because of this major version mismatch between bundles.

I tried stripping the .jar files out of the quickstart.jar and manually installing them by placing them in the crx-quickstart/install folder. This updates many of the bundles that do not update during the upgrade, but a few are still missing and I am concerned that it isn't a fully successful upgrade. I am trying to figure out why these do not update in the first place when I run the upgrade.

I found this in the guide (https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade.html), which sounds like what I am encountering, but the information Adobe gives is very sparse and I am not sure what I am looking for in CRXDE.

In case packages fail to install during the upgrade, the bundles they contain will not be updated either. This category of issues is usually caused by data store misconfiguration. They will also appear as ERROR and WARN messages in the error.log. Since in most of these cases the default login may fail to work, you can use CRXDE directly in order to inspect and find the configuration problems.

If anyone has encountered this, or has any ideas, I am all ears. Thanks!

Alex

[Feike_Visser1]

You might need to recompile/redeploy your code.

Did you try to deploy your code to 6.2?

[a_lex_]

Feike Visser wrote...

You might need to recompile/redeploy your code.

Did you try to deploy your code to 6.2?

Before starting the upgrade I uninstalled all custom bundles/code. I also tried your suggestion of redeploying my code post-upgrade but core AEM bundles were not updated and retained the 6.0 versions.

[Feike_Visser1]

Thanks for your reply. I can't answer it with this info.

Other way of upgrading is to use crx2oak to transwer content/config from your 6.0 instance.

[a_lex_ · Accepted solution]

Figured it out. Missed the /apps/dam/content migration step in the guide, which was causing the instance to not upgrade properly.