Hi all! I had a working MSSQL connector, which suddenly is no longer working, the error below is generated when I test the connector.

State code: 08S01; Message: The TCP/IP connection to the host <server_name>, port 1433 has failed. Error: "No route to host. 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.".

The connector was turned off during the holiday time, and during that time, I've upgraded AirByte to the latest version. I've noted the MSSQL connector got updated. And I tried all the MSSQL connector versions from 4.18 up to 4.26. The SQL connection does work locally on the machine, as I'm able to use SSMS. Any ideas?

Hey Ohad! Thanks for your patience - I was out last week for the holidays and am catching up with messages now. Just to verify - version

0.40.26

works for you, right? I think the thing to do here is look at exactly what got updated in the connector in the latest release. It's a GA connector so if there was a breaking change, it would have been announced. Let me look into this and I'll get back to you!

Thank you @Nataly Merezhuk (Airbyte), for your response. I have investigated this issue further, and I was able to pinpoint the issue with the AirByte upgrade (I've restored the VM, I upgraded the connector to 0.4.26, all was working, and then it broke again after the AirByte upgrade). My previous AirByte version was 0.40.10, and the current 0.40.27. Note, the other connectors I have (CSV Files) are all working fine.

Thanks for the info! Are you using the same connector you made before? What if you try making a new MSSQL connector after upgrading everything? Could you get me full logs from that? I don't see any issues that are coming up for users, so something must just be configured incorrectly 🤔

@Nataly Merezhuk (Airbyte), creating another connector did not work and provided the same result. In fact, any other internal resources (like another SQL Server) are not working. I've used a docker container tool called

network-multitool

to ping these services (like SQL Server), it always fails after the upgrade. However, it can ping external internet and the Domain Controller. Note, it can ping these services before the upgrade. Also, running the connection check always timeout after 6000 ms, which makes sense. It seems to me like an issue with the Docker configuration. I'm using Win10 x64 with the latest Docker Desktop version. My upgrade steps were taking a backup of the AB folder, git pull, and then

docker-compose up

I'll send the log file later, as I need to ask IT to take a snapshot of the VM before I can upgrade AB again. I did check it previously, but I couldn't find anything helpful there 😔.

Gotcha! Thanks for all this info. So sorry to hear you're running into these issues after upgrading, sounds really frustrating. It does look like an issue with Docker. I've seen weird issues come up with Windows deployments, are you using WSL2? I guess a nuclear option if we don't find a solution is to run something like

docker system prune

Thank you @Nataly Merezhuk (Airbyte). Yes, we are using WSL2. And I've tried your suggestion with

docker system prune

and unfortunately for us, it did not resolve the issue. I'm still getting the same error code

08S01

. Attached the server logs. What I don't understand is why the upgrade causes all Docker containers not to communicate with other internal network resources.

Are you using docker compose v2? We just switched, so maybe that would be it!

Yes, @Nataly Merezhuk (Airbyte), my docker-compose was v2.13 during these upgrade intents.

I'm still digging into this, but don't have any quick fixes at the moment, unfortunately. I know this may sound drastic - but have you tried uninstalling and reinstalling Airbyte and/or Docker?