Download ODBC Drivers for Oracle, SQL Server, Salesforce, MongoDB, Access, Derby, InterBase & DB2.

Why do I get authorisation failures from the ODBC-ODBC Bridge client?

Look at the ODBC error diagnostics from SQLError, SQLGetDiagRec, or SQLGetDiagField to find out where the connection is being turned down.

If the Easysoft ODBC-ODBC Bridge turns down the connection, you get a message similar to:

28000:1:1326:[Easysoft ODBC (Client)] Invalid authorization specification

Check the LogonUser and LogonAuth attributes in your ODBC-ODBC Bridge client data source. Specify a valid user name and password for the server machine.

If the user name and password are valid, refer to Why do I get "Invalid authorization specification" when LogonUser and LogonAuth are set to a valid user name and password?

If your database engine requires a user name and password, specify them as UID and PWD values in the connection string. Alternatively, use the ODBC-ODBC Bridge data source attributes TargetUser and TargetAuth to do this. Check odbc.ini, .odbc.ini, or the ODBC Data Source Administrator to make sure these credentials are valid for your database. If the database user name or password are invalid, you get an error similar to:

28000:1:18456:[Microsoft][ODBC SQL Server Driver][SQL Server]
Login failed for user 'Fred'.