KB-2311 Unable to connect to SQL Server after upgrading to 24.1

pauline.delacruz — Wed, 05 Jun 2024 19:09:56 GMT

Current Revision posted to Appian Knowledge Base by pauline.delacruz on 6/5/2024 7:09:56 PM

Symptoms

After upgrading to Appian 24.1, users are unable to connect to the SQL Server data source in the Admin Console. The following error will be seen in the tomcat-stdOut.log:

ERROR com.appiancorp.process.runtime.activities.QueryRdbmsActivity - java.sql.SQLException: Cannot create PoolableConnectionFactory ("encrypt" property is set to "false" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. ClientConnectionId:<id>)

Cause

In Appian 24.1, the SQL Server JDBC driver was updated to version 12. This included a change from Microsoft in how SQL Server handles certificate validation. Certificate validation now validates when encryption is negotiated from either the client or the server side, not just the client side.

Action

Add trustServerCertificate=true to the database connection string in the Admin Console.

Affected Versions

This article applies to Appian 24.1 and later.

Last Reviewed: May 2024

Tags: sql server, database, integration

KB-XXX Unable to connect to SQL Server after upgrading to 24.1

pauline.delacruz — Mon, 13 May 2024 16:14:54 GMT

Revision 4 posted to Appian Knowledge Base by pauline.delacruz on 5/13/2024 4:14:54 PM

Symptoms

After upgrading to Appian 24.1, users are unable to connect to the SQL Server data source in the Admin Console. The following error will be seen in the tomcat-stdOut.log:

ERROR com.appiancorp.process.runtime.activities.QueryRdbmsActivity - java.sql.SQLException: Cannot create PoolableConnectionFactory ("encrypt" property is set to "false" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. ClientConnectionId:<id>)

Cause

Action

Add trustServerCertificate=true to the database connection string in the Admin Console.

Affected Versions

This article applies to Appian 24.1 and later.

Last Reviewed: May 2024

KB-XXX Unable to connect to SQL Server after upgrading to 24.1

pauline.delacruz — Mon, 13 May 2024 16:14:23 GMT

Revision 3 posted to Appian Knowledge Base by pauline.delacruz on 5/13/2024 4:14:23 PM

Symptoms

After upgrading to 24.1, users are unable to connect to the SQL Server data source in the Admin Console. The following error will be seen in the tomcat-stdOut.log:

ERROR com.appiancorp.process.runtime.activities.QueryRdbmsActivity - java.sql.SQLException: Cannot create PoolableConnectionFactory ("encrypt" property is set to "false" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. ClientConnectionId:<id>)

Cause

In 24.1, the SQL Server JDBC driver was updated to version 12. This included a change from Microsoft in how SQL Server handles certificate validation. Certificate validation now validates when encryption is negotiated from either the client or the server side, not just the client side.

Action

Add trustServerCertificate=true to the database connection string in the Admin Console.

Affected Versions

This article applies to Appian 24.1 and later.

Last Reviewed: May 2024

KB-XXX Unable to connect to SQL Server after upgrading to 24.1

lyann.sun — Mon, 22 Apr 2024 17:02:12 GMT

Revision 2 posted to Appian Knowledge Base by lyann.sun on 4/22/2024 5:02:12 PM

Symptoms

After upgrading to 24.1, users are unable to connect to the SQL Server data source in the Admin Console. The following error will be seen in the tomcat-stdOut.log:

ERROR com.appiancorp.process.runtime.activities.QueryRdbmsActivity - java.sql.SQLException: Cannot create PoolableConnectionFactory ("encrypt" property is set to "false" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. ClientConnectionId:<id>)

Cause

Action

Add trustServerCertificate=true to the database connection string in the Admin Console.

Affected Versions

This article applies to Appian 24.1 and later.

KB-XXX Unable to connect to SQL Server after upgrading to 24.1

lyann.sun — Mon, 22 Apr 2024 15:13:10 GMT

Revision 1 posted to Appian Knowledge Base by lyann.sun on 4/22/2024 3:13:10 PM

Symptoms

After upgrading to 24.1, users are unable to connect to the SQL Server data source in the Admin Console. The following error will be seen in the tomcat-stdOut.log:

ERROR com.appiancorp.process.runtime.activities.QueryRdbmsActivity - java.sql.SQLException: Cannot create PoolableConnectionFactory ("encrypt" property is set to "false" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. ClientConnectionId:<id>)

Cause

In 24.1, the SQL Server JDBC driver was updated to version 10.2. This included a change from Microsoft in how SQL Server handles certificate validation. Certificate validation now validates when encryption is negotiated from either the client or the server side, not just the client side.

Action

Add trustServerCertificate=true to the database connection string in the Admin Console.

Affected Versions

This article applies to Appian 24.1 and later.