AEM 6.4 Upgrade from 6.2 Publish Instance Resolver Map Entries are missing after upgrade

[devisreer29]

I was trying to upgrade AEM 6.2 to AEM 6.4 for Publish Instance.

I followed all the steps

The upgraded instance is Up and Running but I am unable to access few consoles like assets.html miscadmin useradmin and few others.

After investigation I found that there are missing Resolver Map Entries under /system/console/jcrresolver  where as these are present in the 6.2 instance

Not sure what is the issue with these missing Resolver Map Entries. I can see this message in error.log while I am trying to access these urls in the instance

04.07.2019 16:03:31.490 *INFO* [16.116.145.133 [1562256211488] GET /assets.html/content/dam HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /assets.html/content/dam not found

There are no custom mappings under etc/maps/http also in the 6.2 instance.

How can I fix this and access the consoles?

[arunpatidar]

Hi,

I checked in AEM 6.4 Vanilla instance, all mappings are presents. You must raise ticket with adobe to get patch or something.

Though there option to create new mappings from below osgi config or a sling filter to match and redirect

http://localhost:4504/system/console/configMgr/org.apache.sling.jcr.resource.internal.JcrResourceRes...

[devisreer29 · Accepted solution]

This issue has been Resolved .After restarting the sever all the consoles are accessible.It took almost 10 hours for the index to update .All the resolver mappings are back after the restart .