@ErsinKa The two CVEs mentioned are related to different issues:Apache Log4j <=1.2.17 Remote Code Execution Vulnerability in SocketServer - CVE-2019-17571This CVE does not impact AEM Forms 6.5.CVE-2015-4000 is specific to the DHE_EXPORT cipher suite. There are steps[0] to update the secure AEM again...

@dpkhmhs Can you check the packages[0] and bundles[1] on the AEM Forms instance. All the Packages (search for aemfd* and aemds*) should be installed and bundles should be in active state.  [0] - http://localhost:4502/crx/packmgr/index.jsp [1] - http://localhost:4502/system/console/bundles 

@andrea_eth Thanks for sharing the form! This issue is not related to API version of the XFA generator.The PDF shared is a Dynamic XFA form and Adobe Sign supports Static XFA PDFs only. Its possible to do this conversion with AEM forms server but if you don't have one then you can print the form wit...

@andrea_eth Don't have an old form or LC Designer to cross check, but what is the API version of the XFA generator you've in the XML source of the form? Recent forms have APIVersion="3.6.13061.0"You can the compatibility by switching to a newer version.

@bsaefiling Would need some more information on the architecture (Linux/windows, Jboss version?).Did you try clean application deployment (removing svc* folders and deploy EARs)?Please attach the server start-up logs.

@SBI_89 If the data is consistent across different environments then why don't you copy the data from Dev DB to other environments and create new datasource for each instead of using the AF to push the data for each environment.

@krist_wang Do you have relevant selection made in the Style/Data/Submission tab while creating the form?The create button will be greyed out if the options in any of these tabs is unselected OR there is a permission issue with the user.

@krist_wang Do you have relevant selection made in the Style/Data/Submission tab while creating the form? The create button will be greyed out if the options in any of these tabs is unselected OR there is a permission issue with the user.

@dannyd21850928 More context : The login health check in AEM periodically checks if default username and password of account admin and author has been changed or not from default author:author and admin:admin.This "author" account is not a built-in user, but used as a demo user for we-retail demo si...

@_Norah_ If there are no custom rules to hide/unhide the captcha component, then seems to be a form specific issue. Please raise a ticket with Adobe support to troubleshoot the issue over a screenshare session.