@amit_kumart9551 tried to reproduce the issue in my local 6.5.12 and AEMaaCS, able to generate JSON with no issues. Try to enable graphQL endpoint as per below link and see if you can resolve your issue - AEM GraphQL API for use with Content Fragments | Adobe Experience Manager 

Hi @AEMnewbie do you have required dependencies installed, at first place seems issue is related to missing dependenciesYou should check into the below thread about missing Kafka dependencySolved: Apache Kafka Integration with AEM - Adobe Experience League Community - 416704

At high level I could say issue is relevant to permissions, may be you can clone the AEM production setup in local and try to reproduce the issue, will get some clue in the logs about the issue. @Jörg_Hoh any clue?

@ajay_bollam Are you able to reproduce the same issue in your local env?Can you share me steps I need to follow in my local env to reproduce the issue?Will it be possible for you to share debug level logs and exception/error stack trace to further investigate the issue?

@williamc8143220 were you able to resolve AEM uninstalling issue? can you please share your findings, it will help other community members and save their time. 

@ajay_bollam I am successfully able to create smart collection (private/public), in AEMaaCS  and in AEM 6.5.4 environment. Were you able to create collection using add to collection feature?Can you share AEM version details. Additionally just revalidate admin user whether it is assigned to dam-users...

Hi @williamc8143220 at high level, the issue is more related to permissions on windows system. 'Application SID does not match Conductor SID' error occurs when a program is being run at an elevated level or the user does not have permission to run the application, 

@gspatil11 1. org.osgi.framework.system.packages.extra=javax.activation; version\=1.1.1 ==> looks good to me2. you can try below steps to resolve the issue            a. create a system bundles (Creating an Extension Bundle for a 3rd party library. (adobe.com) for            b. Removing the existing...

@gspatil11 Option-1: You can use AEM standalone server installation to fix javamail dependency issues, and then move to apache tomcat server. Option-2 - If requirement is timebound open a daycare ticket  

good catch, try with wrapper first, and see if it works for you <dependency> <artifactId>org.apache.sling.javax.activation</artifactId> <version>0.1.0</version> <groupId>org.apache.sling</groupId> <scope>provided</scope> </dependency>Not sure if you already checked into below link - Using Java Mail ...