AEM WCM Component Core bundle is not active

I am trying to run WKND site on AEM 6.5.12. Created AEM Project using below archetype command.

mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \
 -D archetypeGroupId=com.adobe.aem \
 -D archetypeArtifactId=aem-project-archetype \
 -D archetypeVersion=41\
 -D aemVersion=6.5.12 \
 -D appTitle="WKND App" \
 -D appId="wknd-app" \
 -D groupId="com.adobe.aem.guides.wkndapp" -D frontendModule="decoupled"

I am getting below error when loading the WKND home page properties.

Compilation errors in org/apache/sling/scripting/sightly/apps/core/wcm/components/commons/editor/dialog/inherited/v1/inherited/render_html.java: Line 39, column 2543 : com.adobe.cq.wcm.core.components.commons.editor.dialog.inherited.InheritedField cannot be resolved to a type.

To fix this error, check the core component bundle status.

 If bundle is not active then check the AEM version and Core component compatibility at here. 

After installing 2.19.2 version for AEM 6.5.12 then bundle status is changed to active.

HTTP ERROR 503 AuthenticationSupport service missing. Cannot authenticate request.

 I was not able to login to local AEM instance and figured out instance is working after removing the repoint folder under path "crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit".

java.nio.file.FileSystemException: dispatcher\src\conf.d\enabled_vhosts\aem_author.vhost: A required privilege is not held by the client.

When creating new AEM Project using maven archetype version 41, I was getting below error.

"[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate (default-cli) on project standalone-pom:  java.nio.file.FileSystemException: C:\Kishore\aem-nextjs\dispatcher\src\conf.d\enabled_vhosts\aem_author.vhost: A required privilege is not held by the client."

Below is the command to create AEM Project using Maven Archetype 41

mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \

 -D archetypeGroupId=com.adobe.aem \

 -D archetypeArtifactId=aem-project-archetype \

 -D archetypeVersion=41\

 -D aemVersion=6.5.17 \

 -D appTitle="WKND App" \

 -D appId="wknd-app" \

 -D groupId="com.adobe.aem.guides.wkndapp" \

 -D frontendModule="decoupled"

To avoid this, run the command prompt or terminal as Administrator.

AEM as a Cloud Service: Local Setup

Adobe is providing AEM SDK to install it locally.

Follow below steps to install SDK locally and install WKND site.

Navigate to Experience Cloud Software Distribution

Go to the General tab, download the latest Java version.

AEM as a Cloud Service: Dispatcher Setup

Local Dispatcher Setup

The AEM as a Cloud Service SDK includes a validator tool and docker image for simulating it locally.

 Dispatcher Tools is comprised of:

• a baseline set of Apache HTTP Web server and Dispatcher configuration files, located in .../dispatcher-sdk-x.x.x/src
• a configuration validator CLI tool, located at .../dispatcher-sdk-x.x.x/bin/validator
• a configuration deployment CLI tool, located at .../dispatcher-sdk-x.x.x/bin/docker_run
• a Docker image that runs Apache HTTP Web server with the Dispatcher module

AEM Log Tracer: Chrome Plugin

AEM Log Tracer is a Chrome browser extension that exposes server-side log information per-request in the browser.

AEM Log Tracer collects and exposes per-request:

1. AEM Logs
2. Request Progress
3. Queries executed