This article provides troubleshooting guidance for database connection issues that happen during testing a connection in the Syniti Knowledge Platform (SKP). It includes error messages you might see, explains why they occur, and walks you through the resolution steps.
Error Message | Explanation | Resolution |
|---|---|---|
* The input string was not in a correct format. * The given key 'serviceName' was not present in the dictionary. * Keyword not supported: '*****:*****://abcde123:*****;instancename'. | These error messages may occur if you are using a JDBC-formatted connection string to connect to your database system. With the release of cloud-based scanning functionality, Syniti no longer supports the use of JDBC connection strings. | Recreate the connection using the connection properties available for your database system. |
Cannot open server <destination IP address> requested by the login. The login failed. | This error message is specific to Microsoft Azure SQL connections and occurs due to incorrect Username format. | Modify the connection details to enter the username in the following format:
When Hostname = abc123.database.windows.net and Username = Gary, then update the Username to Gary@abc123.database.windows.net |
* Oracle Communication: Failed to connect to server or failed to parse connect string. * Connection failed (RTE:[89013] Socket closed by peer {127.0.0.1:<port number> -> 127.0.0.1:<port number>}. | The database system’s hostname is not recognized or the hostname is not mapped in the | Use the IP address in the connection properties whenever possible, instead of the hostname. If not possible, make sure the hostname is correct and/or include the hostname with the correct IP address in the |
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 31 - Encryption(ssl/tls) handshake failed) | * The SQL Server that the user is trying to connect to is an older version using TLS v1. * The server address provided on the connections page is a hostname (which is not recognized) and NOT an IP address. | * If SQL Server is not compliant with current TLS security standards. You must update this server to a more secure version before you can connect to the SKP. If you are unable to update the server, you can consider alternative methods to extract the data, such as Flat File Extracts, SSIS Packages, or Syniti Connect (BOOMI). * If the error is due to using a hostname in the connection details, please make sure the hostname is correct and include the hostname with the correct IP address in the |