Database connection error during data source configuration AEM Forms 6.5

[msgoldsgt]

I am trying to install AEM Forms 6.5 on Windows 2016 Server running Windows SQL2016. I am using the Partial Turnkey option, and on the Partial Turnkey Installation Options I select MSSQL Server.  The installation completes without any errors.  During the AEM Forms Configuration Manager Datasource Configuration screen, I click Test Database Connection, and I get this message “Error [ALC-LCM-130-107] Database settings failed validation. Note: Windows Authentication on SQL Server will fail the connection test.  See documentation for more details.”

I have tried the JDBC drivers mssql-jdbc-6.2.2.jre8.jar, mssql-jdbc-9.2.0.jre8, mssql-jdbc-9.2.0.jre11, and mssql-jdbc-9.2.0.jre15 with the same error.  If I ignore the error and continue with the installation, I get this error “Bootstrapping Error: ALC-TTN-103-0000 Failed on step invoking component bootstrapper task Bootstrapping UserManager   ALC-TTN-103-000 Bootstrapping request failed on server.  Message from server. ALC-TTN-024-001 Unable to connect database: caused by [javax.resource.ResourceException:IJ000453: Unable to get managed connection for java:/IDP_DS].

I have tried creating a SQL user following the instruction on installation guide, and same error.  Also, I created a SQL user with database owner rights, and same error.  Both user can connect successfully to the database from a workstation to the server, using Microsoft Access and a SQL connection.

Any ideas to continue troubleshooting this issue are greatly appreciated.  Thank you.

[Kosta_Prokopiu1 · Accepted solution]

I am sure that MSSQL is rejecting the logon from JDBC. Your test with Access and a SQL connection is different to what happens during the JDBC based communication from Configuration Manager.

In the Preparing to install AEM Forms (Single Server) manual http://www.adobe.com/go/learn_aemforms_prepareInstallsingle_65 check out chapter "Set up the SQL Server for AEM Forms", "Integrated security"  and "Configure Integrated Security on Windows"

[Mayank_Gandhi]

@msgoldsgt  I have seen this happening not only because of user access but also the default tcp port is not allowed by default in SQL Server. In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration, and check the port is enabled.