Troubleshooting: SQL Data Store Test Connection Fails With 'Connection Failed: Keyword Not Supported' Error

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: All
     
     

    Overview

    Testing a SQL data store connection can fail with the following error, even when the connection settings otherwise look correct:

    Connection Failed: Keyword not supported: 'x'.

    (where x can be any character.)

    A browser popup reading Connection Failed: Keyword not supported: t.

     

    Cause

    The realm's SQL connection string uses a semicolon to delimit each of its key-value pairs. If one of the values in the connection string -- most commonly the SQL service account's password -- itself contains a semicolon, that extra semicolon is misread as another delimiter, which breaks the parsing of the connection string.

     

    Resolution:

    1. On the realm's Data tab, review the SQL connection string's values (particularly the SQL service account's password) for a semicolon.
    2. If a value contains a semicolon, remove it -- for example, if it's the SQL service account's password, change the password itself so it no longer contains that character.
    3. Click Test Connection to confirm.




     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.