Troubleshooting

Alation Cloud Service Applies to Alation Cloud Service instances of Alation

Customer Managed Applies to customer-managed instances of Alation

Core Connector Core connectors are included with all Alation platform tiers (subject to each tier’s connector limits) and are fully supported by Alation.

Refer to Troubleshoot OCF Connectors.

Refer to the following scenarios for help in troubleshooting common issues.

Error Using the SSL Configuration

Problem

SQL Server OCF connector test connection failing with the following error:

Error using the SSL configuration.

Solution

If the connection is not intended to use SSL, set the encrypt parameter to false in the JDBC URI.

SQL Server Connection Fails with the Error “Login failed from untrusted domain”

Test connection fails when user attempts to login from an untrusted domain that is not compatible with Windows authentication (NTLM).

Problem

You are configuring authentication for a SQL Server data source using NTLM Authentication. When you test the connection from the General Settings tab, the connection fails with the following error, preventing you from connecting to the SQL Server:

Login failed. Login was attempted from an untrusted domain that is not compatible with integrated authentication.

The error appears in the following locations:

  • The Connection Test result dialog box

  • The OCF connector logs

Cause

This error occurs when there are domain trust or authentication configuration issues between the Alation server and the SQL Server’s domain environment. Common causes include:

  • The domain specified in the JDBC URI is incorrect or not fully qualified.

  • No trust relationship exists between the Alation server’s domain and the SQL Server’s domain.

  • NTLM authentication is not configured correctly on the SQL Server.

  • Network connectivity issues prevent proper domain authentication.

Solution

Follow these steps to resolve a domain authentication issue:

  1. Verify the domain configuration

    1. Verify that the domain name in your JDBC URI is fully qualified (for example MYDOMAIN.COMPANY.COM not just MYDOMAIN).

    2. Ensure that the domain controller is reachable from the Alation server.

    3. If connecting across domains, verify there is a trust relationship between them.

  2. Configure NTLM authentication

    1. Ensure that your JDBC URI includes integratedSecurity=true.

    2. Add the authenticationScheme=NTLM parameter to your JDBC URI.

    3. Verify that the SQL Server service runs under a domain account, not local account.

  3. Test network connectivity (Customer Managed instances and Alation Cloud Service instances with the connector installed on the Alation Agent)

    1. Verify the network accessibility between Alation and the domain controller.

    2. Ensure that the following ports are open: 88 (Kerberos), 135 (RPC), 389 (LDAP), 445 (SMB).

    3. Test the DNS resolution for both domain controller and SQL Server.

  4. Validate service account permissions (Customer Managed and Agent deployments)

    1. Ensure that the service account has necessary domain permissions.

    2. Ensure that the account can authenticate to the SQL Server instance.

  5. Re-test the connection

    Return to the data source General Settings tab and click Test Connection.

For additional NTLM configuration details, refer to the Microsoft documentation: Using NTLM Authentication to Connect to SQL Server.