Why can't I connect to the ODBC-ODBC Bridge's target data source?
There can be many reasons for getting SQL_ERROR
back from SQLDriverConnect or SQLConnect. Refer to How do I find out why an ODBC call is failing first. The most likely reasons are:
- "IM002 - DSN or TargetDSN not found." The Easysoft ODBC-ODBC Bridge client couldn't find the data source in
odbc.ini
or ODBC Data Source Administrator. The Driver Manager couldn't find the data source. TheTargetDSN
attribute was missing from the data source or connection string. Refer also toHY000
below.The most common reason for this when connecting to Windows is setting
TargetDSN
to specify a user DSN instead of a system DSN. Check that the ODBC data source on your Windows machine is a system DSN. - "28000 - Invalid authorization specification." Either the
LogonUser
andLogonAuth
attribute pair or theTargetUser
andTargetAuth
attribute pair have invalid values.LogonUser
andLogonAuth
must specify a user name and password that the ODBC-ODBC Bridge server can use to log on to the target machine. The ODBC-ODBC Bridge passesTargetUser
andTargetAuth
to the remote SQLDriverConnect call. The target ODBC driver uses these credentials for database authentication (if required). - "08001 - Client unable to establish connection." The machine specified by
Server
can't be found, is not running the ODBC-ODBC Bridge server, or is affected by a networking issue. Check that theServer
attribute value is a valid machine name or IP address. Check the machine name is resolvable by DNS or is present in thehosts
file. Check that you are on the same network by pinging the target server. Check thePort
attribute in the specified data source is correct. Try telnetting to the server machine on that port. - "HY000 - A general error." Check that you've supplied all the connection attributes required to connect to the server. For example, if you omit the
SERVER
attribute from the data source, you get anIM002
error and then a secondaryHY000
error explaining what the problem is.