How to resolve error "SQL1513N The connection failed because the name specified with DSN connection string keyword could not be found..."

The error occurs because there is no DB2 database alias configured on the machine where you run Intelligent Converters software. This situation may take place when the system uses IBM Data Server Driver for ODBC and CLI to connect to DB2 database. It must be configured manually since it is not part of the integrated IBM Server or Client environment.

Check the DSN configuration. The error typically indicates that the specified DSN name in the connection string cannot be found:

• Ensure that you have created a DSN with the correct name on your system. The DSN is created through the ODBC Data Source Administrator tool, which can be found in the Windows Control Panel or by searching for "ODBC" in the Start menu.
• Open the ODBC Data Source Administrator tool and switch to the "System DSN" tab. Look for the DSN name mentioned in the error message. If it is not listed, you may need to create a new DSN with the correct name.
• If the DSN is listed, double-check the spelling and ensure that it matches exactly with the DSN specified in the connection string.

Check the connection string you are using to connect to the database. The DSN name should be specified correctly. Ensure that there are no typographical errors or extra spaces in the connection string. Use the ODBC Data Source Administrator tool to test the connection to the DSN. Follow these steps:

• Open the ODBC Data Source Administrator tool
• Switch to the "System DSN" tab
• Select the DSN name mentioned in the error message
• Click the "Configure" or "Test Connection" button
• Follow the prompts to test the connection. If the test fails, review the configuration and make any necessary corrections

Ensure that the database server associated with the DSN is running and accessible. Check the server name, port number, and network connectivity to the server. If you made changes to the DSN configuration or the connection string, restart the application that was generating the error and check if the issue is resolved.

You can learn how to configure connection for ODBC and CLI IBM Driver in article Connecting to DB2 database

Have questions? Contact us