Worked for me. I deleted the license file and when entered the credentials, it let me in on my publish instance and re-generated the license file.

I did similar thing in my previous engagement where I migrated content from legacy CMS to AEM. I used Content fragment APIs to do that. You can explore it more here  https://javadoc.io/static/com.adobe.aem/aem-sdk-api/2020.6.3696.20200610T021539Z-200604/com/adobe/cq/dam/cfm/FragmentTemplate.html Cod...

For future visitors, Last time when I saw this error was when I was trying to switch between AEM 6.3 and AEM 6.5 instance. Deleting repoinit folder from my AEM instance fixed this issue for me. Either you can run below command  rm -rf crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit OR ...

For future visitors, Deleting repoinit folder from my AEM instance fixed this issue for me. Either you can run below command  rm -rf crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit OR delete the folder manually.  There are other ways too but this is the quickest I found  

Deleting repoinit folder from my AEM instance fixed this issue for me. Either you can run below command  rm -rf crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit OR delete the folder manually.  There are other ways too to fix this but above one is the quickest I found.

For future visitors, Deleting repoinit folder from my AEM instance fixed this issue for me. Either you can run below command  rm -rf crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit OR delete the folder manually.   

Deleting repoinit folder from my AEM instance fixed this issue for me. Either you can run below command  rm -rf crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit OR delete the folder manually.  Blog post which Jorg mentioned, also talk about repoinit as one of the reason for getting this...

Hello,Try checking if you are already running any AEM instance on same port, if not, killing Java process completely and then start your AEM helps most of the time.Thanks

Try using below combinationjcr:read\,jcr:versionManagement\,jcr:modifyProperties\,jcr:addChildNodes\,jcr:lockManagement\,jcr:nodeTypeManagementAnd JFYI, below is the mapping for permissions (might help)"READ": ["jcr:read"]"MODIFY": ["jcr:modifyProperties","jcr:lockManagement","jcr:versionManagement"...

Workaround, if you are blocked, use http://localhost:4502/libs/cq/workflow/content/console.html to access models.Also, when you hit http://localhost:4502/libs/cq/workflow/admin/console/content/models.html what are you seeing in error log, can you paste it here