This is because of upgrade is not done properly. During the upgrade few packages is not upgraded from older version to new version due to javax.jcr.nodetype.ConstraintViolationException. This is because of custom code has updated 'rep:externalId' to the users and system user in the AEM 6.2 instance....

I am upgrading from AEM 6.2 [6.2.0.SP1] to AEM 6.4. Do i need to install CFP package before upgrade. Post upgrade SP5 installation also didn't fix the problem.

Post upgrade from AEM 6.2 with SP2 to AEM 6.4 few of the packages are in not installed. The older version is on installed state.For the new package is showing the message as "A different version seems to be installed:"When i am trying to install manually i am getting the error javax.jcr.nodetype.Con...

I have added all the pom dependency with Junit, WCM io, Sling Jcr dependency.But still when i am running junit the below error is throwing when resource is adopting to page or node.java.lang.NoSuchMethodError: org.osgi.framework.BundleContext.getServiceReference(Ljava/lang/Class;)Lorg/osgi/framework...

Is there any example for customizing sites action bar in touch UI?Like copy the page in sites actionbar need to add custom button in sites actionbar.

When we upgrading AEM 6.1 with SP2 instance to AEM 6.3 the below exception occurring only on recent backup. The different backup is working which is took earlier.22.12.2017 11:14:44.695 *ERROR* [Apache Sling Repository Startup Thread] com.adobe.granite.repository.impl.SlingRepositoryManager start: U...

This issue we have fixed by disabled all the custom indexes. After that copied and renamed all the custom index names and then started re-indexing for all. It got worked.

We are tried renaming the index and name again triggered indexing for lucene but the result is same.

Oak 1.2.22. AEM6.1 with SP2. The total number of nodes traversed and logs are stable.  Usually it will take sometime and ll give the report. But now it's not giving as well as reindex property value is true.

I have triggered re indexing for the all custom and few OOTB indexes. Re indexing got completed but the report is not generated and also re indexing  property value is still "true". Because of this all the queries are going traversal. This is happening during restore of existing instance backup.