It seems as if the dispatcher has some of your cached clientlibs. Try to reproduce the issue my removing the entire dispatcher cache. 

You can check how your request is being processed/forwarded in /system/console/requests console. You can also check the incoming requests in request.log, access.log and the reason for failure in error.log. Also try enabling DEBUG logger for your custom servlet. That may also help. Hope these help.  ...

Yes, there is.  The following doc may be helpful:https://docs.adobe.com/content/help/en/experience-manager-learn/assets/metadata/metadata-import-feature-video-use.html

On the publish server, are you able to reproduce the issue, when you bypass the dispatcher(i.e., access the publish server using its host & port directly)?a) If not, then enable DEBUG logging for dispatcher, and see which filter is blocking the request. You can then allow this request to go through ...

In addition to it, since AEM 6.4 onwards, Repository Restructuring occurred.The following doc may be helpful in finding the correct locations/paths of nodes in AEM 6.5:https://docs.adobe.com/content/help/en/experience-manager-65/deploying/restructuring/repository-restructuring.html

There are many clientlibs that are not just specific to authoring. They are also related to how your content/components appear on the UI, lazy loading of assets, etc. If you remove any clientlibs that might be required, it would mess up your UI. You would have to replicate them from author and even ...

@kartheekd203042 The count seems to be 0. It could be something to do with cqPageLucene(/oak:index/cqPageLucene). Try re-indexing it and verify whether the issue still exists. Try using OOTB cqPageLucene index and then verify whether the issue still exists.

* Check for the existence of ensure-service-user on your AMS environment.* Go to /system/console/configMgr, search for the service mapping for this bundle and ensure that the service user is included within [], and then save it.Ex: I don't have acs bundle, but I have the following mapping configured...

This issue isn't reproducible OOTB. * Do you see any Console errors in Developer Tools of your browser?* Do you see the same issue using OOTB admin user? If it's not related to permissions, try the following steps as well:* Enable DEBUG log level on query class below in /system/console/slinglogorg.a...

You can use the Asset Interface to achieve the same. // to create an asset AssetManager assetManager = resolver.adaptTo(AssetManager.class); Asset newAsset = assetManager.createAsset("/path/to/asset/document.pdf");The following docs may be helpful:https://helpx.adobe.com/experience-man...