Hi,You should log a support ticket with daycare.Do you have a very recent backup of the data store u can restore?I would then run a datastore consistency check[1] to see what state it is in.Regards,Opkar[1] https://helpx.adobe.com/experience-manager/kb/datastore-inconsistency-record-not-found-.html

Hi,can this issue be replicated in your dev and local instances? Have you debugged your code to see at which point the reindex is triggered? As you suggest this is not normal behaviour, have you opened a daycare ticket?Regards,Opkar

Hi Anand,can you post some of the log messages you see for your reindexing issue?Regards,Opkar

Hi,there is not enough information to understand why this is happening. It may not necessarily be a custom authentication handler. Is it a publish instance? Could it be CUG they are using?Regards,Opkar

Hi,doing an unclean shutdown can corrupt the repository[1]. The authentication support service error is a symptom of an error much further back in the error log. Please search through the error log and see what is the first exception that occurs.Regards,Opkar[1] https://helpx.adobe.com/experience-ma...

Hi Shubhankar,Please see this previous thread [1]Other articles [2],[3],[4]You need to decide your how much of your current content you want to migrate, then map old to new. You then need to extract the content from Drupal and transform it into a format that can be imported into AEM.In AEM you need ...

Hi Juan,I'd consider creating a the slave from a clone as described here[1]. It can save time as you don't have to synch a brand new instance.Regards,Opkar[1] http://cq-ops.tumblr.com/post/42523140404/quickly-creating-a-cq-cluster-using-manual-slave

Hi,what happens when you try to access the URL directly on the publish instance, does it require authentication?When you try any other content, does it result in the same errors?If you still have geometrixx, any issues accessing that content?Regards,Opkar

Hi,you can either upgrade in place or deploy your codebase to a new instance. By deploying to a new instance you will lose all your version and audit history. If you try deploying again, delete the folder "/apps/test-config/config" before deploying.I you are doing an upgrade, please be aware of the ...

Hi,at what stage in the migration process are you? Have you successfully run through all the steps in[1], you have no errors in your error.log when starting your migrated instance?Are you now importing your custom codebase?Regards,Opkar[1] https://docs.adobe.com/docs/en/aem/6-1/deploy/upgrade.html