Source MSSQL - The connection tests failed

Connector Questions & Issues
1
  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Ubuntu
  • Memory / Disk: 8Gb / 1 Tb
  • Deployment: Docker
  • Airbyte Version: 0.40.10
  • Source name/version: airbyte/source-mssql/0.4.20
  • Destination name/version:
  • Step: The issue is happening during setting up a connection.
  • Description: I am trying to connect to a named MSSQL instance eg: <sql_server_host><named_instance>

I get an error as follows:

The connection tests failed.
State code: 08S01; Message: The TCP/IP connection to the host <hostname>, port 1433 has failed. Error: "Connection refused. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".

But I also get sources.jobStatus.check_connection_source.succeeded log file.

2022-10-12 13:01:14 INFO i.a.w.t.TemporalAttemptExecution(get):108 - Docker volume job log path: /tmp/workspace/b4537d1f-c7db-4a68-afe2-ceb38f4aa43e/0/logs.log
2022-10-12 13:01:14 INFO i.a.w.t.TemporalAttemptExecution(get):113 - Executing worker wrapper. Airbyte version: 0.40.10
2022-10-12 13:01:15 INFO i.a.c.i.LineGobbler(voidCall):114 - 
2022-10-12 13:01:15 INFO i.a.c.i.LineGobbler(voidCall):114 - ----- START CHECK -----
2022-10-12 13:01:15 INFO i.a.c.i.LineGobbler(voidCall):114 - 
2022-10-12 13:01:15 INFO i.a.c.i.LineGobbler(voidCall):114 - Checking if airbyte/source-mssql:0.4.20 exists...
2022-10-12 13:01:15 INFO i.a.c.i.LineGobbler(voidCall):114 - airbyte/source-mssql:0.4.20 was found locally.
2022-10-12 13:01:15 INFO i.a.w.p.DockerProcessFactory(create):119 - Creating docker container = source-mssql-check-b4537d1f-c7db-4a68-afe2-ceb38f4aa43e-0-xemom with resources io.airbyte.config.ResourceRequirements@12154986[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=]
2022-10-12 13:01:15 INFO i.a.w.p.DockerProcessFactory(create):163 - Preparing command: docker run --rm --init -i -w /data/b4537d1f-c7db-4a68-afe2-ceb38f4aa43e/0 --log-driver none --name source-mssql-check-b4537d1f-c7db-4a68-afe2-ceb38f4aa43e-0-xemom --network host -v airbyte_workspace:/data -v /tmp/airbyte_local:/local -e DEPLOYMENT_MODE=OSS -e USE_STREAM_CAPABLE_STATE=true -e WORKER_ENVIRONMENT=DOCKER -e AIRBYTE_ROLE= -e WORKER_CONNECTOR_IMAGE=airbyte/source-mssql:0.4.20 -e WORKER_JOB_ATTEMPT=0 -e AIRBYTE_VERSION=0.40.10 -e WORKER_JOB_ID=b4537d1f-c7db-4a68-afe2-ceb38f4aa43e airbyte/source-mssql:0.4.20 check --config source_config.json
2022-10-12 13:01:16 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):103 - starting source: class io.airbyte.integrations.source.mssql.MssqlSource
2022-10-12 13:01:16 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):103 - integration args: {check=null, config=source_config.json}
2022-10-12 13:01:16 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):103 - Running integration: io.airbyte.integrations.base.ssh.SshWrappedSource
2022-10-12 13:01:16 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):103 - Command: CHECK
2022-10-12 13:01:16 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):103 - Integration config: IntegrationConfig{command=CHECK, configPath='source_config.json', catalogPath='null', statePath='null'}
2022-10-12 13:01:16 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):100 - Unknown keyword order - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2022-10-12 13:01:16 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):100 - Unknown keyword examples - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2022-10-12 13:01:16 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):100 - Unknown keyword airbyte_secret - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2022-10-12 13:01:16 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):100 - Unknown keyword multiline - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2022-10-12 13:01:17 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):103 - Starting connection with method: NO_TUNNEL
2022-10-12 13:01:17 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):103 - HikariPool-1 - Starting...
2022-10-12 13:01:17 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):103 - HikariPool-1 - Start completed.

I tired different ways to connect with the host but no success. It this a bug or still not a developed part or am I missing something

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

Hey @melroy-bsk, thanks for your post and welcome to the community.

A couple of questions:

  1. Did you recently upgrade from an older version of this connector to the latest? This section might be relevant: https://docs.airbyte.com/integrations/sources/mssql/#upgrading-from-0417-and-older-versions-to-0418-and-newer-versions

  2. What version of Microsoft SQL Server are you using?

  3. Is your instance of Microsoft SQL Server configured correctly? This may help: https://stackoverflow.com/questions/18841744/jdbc-connection-failed-error-tcp-ip-connection-to-host-failed

I haven’t seen any issues on our github relating to similar connection issues. If this is a bug, I will escalate this but let’s try troubleshooting some things first. Hope this helps

4

Hey, thanks for the support.

I figured out with the IT team that the PORT number is not the default port number 1433 but a different port number for the named instance.

They said that internally the SQL server does a lookup for the instance and the client contacts the host on the default port no (1433), which then returns the port number for that instance and connects to it.