If you do  a search on the forums you will see that creating a package for the admin user is not supported in OAK, please try it without the admin user, also probably best to exclude tokens. But a search should bring up the correct information.RegardsOpkar

Hi,please review the documentation[1], the section "Incremental Upgrade" it will help you understand the process and answer your question."If an existing repository is passed as the destination, then only a diff between source and destination will be migrated. It allows to migrate the content in a f...

Hi Reini,as has been mentioned REST principles specify each request should be stateless[0], which your http sessions breaks. It should also be noted that by using an http session, you would need to maintain a sticky connection, as the session would only exist in the publish instance that created the...

Great news Gunalan!Can you share the hot fix number for the quartz scheduler error log issue? How did you find the issue with the file OsgiManager.config?Regards,Opkar

Using packages to migrate content from 5.6.1 to 6.2 is not supported, there are changes in the repository structure which would not be correctly updated using this method. In the documentation the recommendation is to do an inlace upgrade, which you said have done. You could look at incremental migr...

Hi Naveen,If you are planning to use the same OS, then you can simply create an archive of your current repo (e.g. zip file) and transfer it to your new server, check all the environment variables have been setup correctly, configure your start service and restart the instance. You will have to reco...

Hi,You should raise a daycare ticket about this. Thread dumps will help to identify what is blocking shutdown in your instance. Did you do a code deployment just before this issue started?Regards,Opkar

JK Kendall wrote...  "setting up Mongo for a cluster on the publish tier is not recommended" Be aware - the recommendations for the platform store and for UGC store are different as the storage locations and characteristics of working with the various forms of content are not the same. For example, ...

Hi,it would help if you told us:What version of AEM this isAny configurations you have done i.e. external file datastore, "nocamplecontent"Any hot fixes or service packsHas this issue only started happening recently, have there been any changes to the repository: Code deployment, SP or hot fixRegard...

JSRP is only really suitable for single publish instance deployments, as setting up Mongo for a cluster on the publish tier is not recommended, you would need to get approval for your use case and architecture from daycare/engineering before Adobe would support it [0]. Unfortunately, quite a few of ...