You are currently reviewing an older revision of this page.
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:
<APPIAN_HOME>/logs
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
This issue occurs because the user used to log in is unable to authentication against active directory.
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.
This article applies to all versions of Appian.
Last Reviewed: April 2019