KB-1922 Unable to add SQL Server data source from Admin Console due to "Failed datasource validation"

Nicholas Van Dyke — Wed, 12 Aug 2020 14:07:29 GMT

Current Revision posted to Appian Knowledge Base by Nicholas Van Dyke on 8/12/2020 2:07:29 PM

Symptoms

From the Admin Console, a user is unable to add a SQL Server data source hosted in Microsoft Azure Cloud. The following error is printed in the tomcat-stdOut.log located in the <APPIAN_HOME>/logs directory:

DEBUG com.appiancorp.rdbms.datasource.DataSourceFactory - Successfully created Data Source from DataSourceInfo{id=null, uuid='null', name='jdbc/<schema_name>', type=SQL Server, connectionUrl='jdbc:sqlserver://<database_url>:1433;database=<database_name>;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;authenticationMode=ActiveDirectoryPassword'}. Total Data Sources created: 88
ERROR com.appiancorp.expr.server.scriptingfunctions.DataSourceFunctions - Failed datasource validation
com.appiancorp.rdbms.datasource.DataSourceValidationException: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
Caused by: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8

Cause

The logged in user attempting to configure the data source connection is unable to authenticate against the active directory.

Action

Any one of the following steps can resolve the issue:

Engage the Microsoft Active Directory (AD) team to resolve the authentication issue and ensure that the user attempting to connect to the data source has the appropriate permissions.
Disable Active Directory (AD) authentication and use SQL Server authentication instead of authentication on the Azure Console or on the database server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2020

Tags: sql server, database, infrastructure

KB-1922 Unable to add SQL Server data source from Admin Console due to "Failed datasource validation"

James Lee — Wed, 12 Aug 2020 13:54:20 GMT

Revision 6 posted to Appian Knowledge Base by James Lee on 8/12/2020 1:54:20 PM

Symptoms

DEBUG com.appiancorp.rdbms.datasource.DataSourceFactory - Successfully created Data Source from DataSourceInfo{id=null, uuid='null', name='jdbc/<schema_name>', type=SQL Server, connectionUrl='jdbc:sqlserver://<database_url>:1433;database=<database_name>;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;authenticationMode=ActiveDirectoryPassword'}. Total Data Sources created: 88
ERROR com.appiancorp.expr.server.scriptingfunctions.DataSourceFunctions - Failed datasource validation
com.appiancorp.rdbms.datasource.DataSourceValidationException: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
Caused by: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8

Cause

The logged in user attempting to configure the data source connection is unable to authenticate against the active directory.

Action

Any one of the following steps can resolve the issue:

Engage the Microsoft Active Directory (AD) team to resolve the authentication issue and ensure that the user attempting to connect to the data source has the appropriate permissions.
Disable Active Directory (AD) authentication and use SQL Server authentication instead of authentication on the Azure Console or on the database server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2020

Tags: database, infrastructure

KB-1922 Unable to add SQL Server data source from Admin Console due to "Failed datasource validation"

Nicholas Van Dyke — Tue, 11 Aug 2020 16:07:37 GMT

Revision 5 posted to Appian Knowledge Base by Nicholas Van Dyke on 8/11/2020 4:07:37 PM

Symptoms

Using the Admin Console, users are unable to add a SQL Server data source hosted in Microsoft Azure Cloud. The following error is printed in tomcat-stdOut.log located in the <APPIAN_HOME>/logs directory:

DEBUG com.appiancorp.rdbms.datasource.DataSourceFactory - Successfully created Data Source from DataSourceInfo{id=null, uuid='null', name='jdbc/<schema_name>', type=SQL Server, connectionUrl='jdbc:sqlserver://<database_url>:1433;database=<database_name>;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;authenticationMode=ActiveDirectoryPassword'}. Total Data Sources created: 88
ERROR com.appiancorp.expr.server.scriptingfunctions.DataSourceFunctions - Failed datasource validation
com.appiancorp.rdbms.datasource.DataSourceValidationException: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
Caused by: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8

Cause

This issue occurs when the logged in user (attempting to configure the data source connection) is unable to authentication against the active directory.

Action

Any one of the following steps can resolve the issue:

Engage the Microsoft Active Directory (AD) team to resolve the authentication issue and ensure that the user attempting to connect to the data source has the appropriate permissions.
Disable Active Directory (AD) authentication and use SQL Server authentication instead of authentication on the Azure Console or on the database server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2020

Tags: database, infrastructure

KB-1922 Unable to add data source from Admin Console due to "Failed datasource validation"

Jordan Horwat — Thu, 25 Apr 2019 15:38:40 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 4/25/2019 3:38:40 PM

Symptoms

Using the Admin Console, users are unable to add MS SQL data source hosted in Microsoft Azure Cloud. The following error is printed in the tomcat-stdOut.log located in the <APPIAN_HOME>/logs directory:

DEBUG com.appiancorp.rdbms.datasource.DataSourceFactory - Successfully created Data Source from DataSourceInfo{id=null, uuid='null', name='jdbc/<schema_name>', type=SQL Server, connectionUrl='jdbc:sqlserver://<database_url>:1433;database=database_name;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;authenticationMode=ActiveDirectoryPassword'}. Total Data Sources created: 88
ERROR com.appiancorp.expr.server.scriptingfunctions.DataSourceFunctions - Failed datasource validation
com.appiancorp.rdbms.datasource.DataSourceValidationException: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "soundphysicians.com" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
Caused by: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "server_name" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8

Cause

This issue occurs when the logged in user (attempting to configure the data source connection) is unable to authentication against the active directory.

Action

Any one of the following steps can resolve the issue:

Engage the Microsoft AD team to resolve the authentication issue and ensure that user used to connect to the datasource has the appropriate permissions.
Disable Active Directory Authentication and use MS SQL authentication instead on the Azure Console or on the database server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: database, infrastructure

DRAFT KB-XXXX Unable to add data source from Admin console due to failed "Datasource validation"

Anirudh Rathi — Wed, 24 Apr 2019 22:14:21 GMT

Revision 3 posted to Appian Knowledge Base by Anirudh Rathi on 4/24/2019 10:14:21 PM

Symptoms

DEBUG com.appiancorp.rdbms.datasource.DataSourceFactory - Successfully created Data Source from DataSourceInfo{id=null, uuid='null', name='jdbc/<schema_name>', type=SQL Server, connectionUrl='jdbc:sqlserver://<database_url>:1433;database=database_name;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;authenticationMode=ActiveDirectoryPassword'}. Total Data Sources created: 88
ERROR com.appiancorp.expr.server.scriptingfunctions.DataSourceFunctions - Failed datasource validation
com.appiancorp.rdbms.datasource.DataSourceValidationException: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "soundphysicians.com" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
Caused by: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "server_name" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8

Cause

This issue occurs when the logged in user (attempting to configure the data source connection) is unable to authentication against the active directory.

Action

Any one of the following steps can resolve the issue:

Engage the Microsoft AD team to resolve the authentication issue and ensure that user used to connect to the datasource has the appropriate permissions.
Disable Active Directory Authentication and use MS SQL authentication instead on the Azure Console or on the database server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: database, infrastructure

DRAFT KB-XXXX Unable to add data source from Admin console due to failed "Datasource validation"

Jordan Horwat — Mon, 22 Apr 2019 17:43:26 GMT

Revision 2 posted to Appian Knowledge Base by Jordan Horwat on 4/22/2019 5:43:26 PM

Symptoms

DEBUG com.appiancorp.rdbms.datasource.DataSourceFactory - Successfully created Data Source from DataSourceInfo{id=null, uuid='null', name='jdbc/<schema_name>', type=SQL Server, connectionUrl='jdbc:sqlserver://<database_url>:1433;database=database_name;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;authenticationMode=ActiveDirectoryPassword'}. Total Data Sources created: 88
ERROR com.appiancorp.expr.server.scriptingfunctions.DataSourceFunctions - Failed datasource validation
com.appiancorp.rdbms.datasource.DataSourceValidationException: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "soundphysicians.com" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
Caused by: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "server_name" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8

Cause

This issue occurs when the logged in user (attempting to configure the data source connection) is unable to authentication against the active directory.

Action

Any one of the following steps can resolve the issue:

Engage the Microsoft AD team to resolve the authentication issue and ensure that the user used to log in has proper permissions.
Disable Active Directory Authentication and use MS SQL authentication instead.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: database, infrastructure

DRAFT KB-XXXX Unable to add data source from Admin console due to failed "Datasource validation"

Anirudh Rathi — Mon, 22 Apr 2019 16:49:44 GMT

Revision 1 posted to Appian Knowledge Base by Anirudh Rathi on 4/22/2019 4:49:44 PM

Symptoms

Using the Admin console, users are unable to add MS SQL data source hosted in Microsoft Azure Cloud due to failed data source validation. The following error is printed in the tomcat-stdOut.log located in <APPIAN_HOME>/logs directory:

DEBUG com.appiancorp.rdbms.datasource.DataSourceFactory - Successfully created Data Source from DataSourceInfo{id=null, uuid='null', name='jdbc/<schema_name>', type=SQL Server, connectionUrl='jdbc:sqlserver://<database_url>:1433;database=database_name;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;authenticationMode=ActiveDirectoryPassword'}. Total Data Sources created: 88
ERROR com.appiancorp.expr.server.scriptingfunctions.DataSourceFunctions - Failed datasource validation
com.appiancorp.rdbms.datasource.DataSourceValidationException: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "soundphysicians.com" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
Caused by: java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot open server "server_name" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8)
...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open server "<server_name>" requested by the login.  The login failed. ClientConnectionId:08642aef-2dd8-4c2a-8e04-ae2db07b8ae8

Cause

This issue occurs because the user used to log in is unable to authentication against active directory.

Action

Anyone of the following steps can resolve the issue:

1. Engage the Microsoft AD team to resolve the authentication issue and ensure that the user used to log in has proper permissions.

2. Disable Active Directory Authentication and use MS SQL authentication instead.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: database, infrastructure