This hint is maybe useful to you if your ODBC connection is configured with server name and not with IP number.
One day
there was an error message in ETL log.
Connection failed:
SQLState: ’01000’
SQL Server
Error: 11001
[Microsoft][ODBC
SQL Server Driver][DBNETLIB]ConnectionOPen (Connect())
Connection
failed:
SQLState: ’08001’
SQL Server
Error: 6
[Microsoft][ODBC
SQL Server Driver][DBNETLIB]Specifed SQL server not found.
When I tried configurations of faulty connections with ODBC Data Source Administrator I got same errors as above again.
Then I used
command line and PING-commad (PING [server_name]). Ping went through just fine.
I tried to reconfigure connection with ODBC Data Source Administrator again. I made new connection actually. I copied settings from faulty ODBC setting but replaced server name with IP-number, which I got response from PING command. This time ODBC Data Source Administrator give SUCCESS from connection test! I renamed faulty connection with “_old” ending and renamed new connection with previous name.
ETL-process
went through with any errors.
What was wrong? I don’t know. There was other ODBC connections to different databases with
the same server and they were working just fine with server name.
But hey! Connection works!