- Check if you are getting any error in the log files when trying to load miscadmin- Open the developer console in browser and check for any errors in the console OR any failing requests in the network tab-  Try upping the json.maximumresults  of the Apache Sling Get Servlet

You can check if the "dam:relativePath" is indexed as part of the properties under the node at [1]. If yes, you can remove the "dam:relativePath" property from the index, re-index and try to re-run the query[1] /oak:index/damAssetLucene/indexRules/dam:Asset/properties

For Json results, it will be the "max json results" at the default get servlet[1][1] http://<host>:<port>/system/console/configMgr/org.apache.sling.servlets.get.DefaultGetServlet

[1] is the node to make the Name column sortable. To make the sorting case insensitive, try using 'sortMode' as 'local' at [2] which is set as 'remote' by default. Refer [3] for more details[1] /libs/dam/gui/content/commons/availablecolumns/name[2] /libs/dam/gui/content/assets/jcr:content/views/list...

Can you setup a DEBUG level logger on "com.adobe.granite.ui.clientlibs" and check if you can get more info about the failure.

Immediately prior to installation of your package, a snapshot package(under /etc/packages/<package_group>) is created to contain the content that will be overwritten.This snapshot will be re-installed if/when you uninstall your package.You cannot uninstall a package if the ".snapshot" directory is n...

Please reach out to Adobe CSM/TAM for more info. As far as I can check internally, there is no such info available about EOL for communities.

There are not many API that was changed from 6.3 to 6.5. So, compiling the custom code with uber jar version 6.5.0.0 should be enough.

1) Run Pre-Upgrade steps2) Stop the 6.3 instance3) Replace the jar as migration is not required when moving from 6.3 to 6.54) Unpack the jar and start the 6.5 instance.More details at [1][1] Performing an In-Place Upgrade

Which version of AEM instance are you using?