Hy everyone, we are encountering a problem when tr...
# replication-troubleshooting
l
Hy everyone, we are encountering a problem when trying to normalize the data we got from our mssql 2019 DB to put it in our mssql 2019 DB. We get the Error:
Copy code
Encountered an error:
Database Error
  ('HYT00', '[HYT00] [unixODBC][Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired (0) (SQLDriverConnect)'),retryable=<null>,timestamp=1675434737625], io.airbyte.config.FailureReason@64441cbe[failureOrigin=normalization,failureType=system_error,internalMessage=('HYT00', '[HYT00] [unixODBC][Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired (0) (SQLDriverConnect)'),externalMessage=Normalization failed during the dbt run. This may indicate a problem with the data itself.,metadata=io.airbyte.config.Metadata@1ebd324a[additionalProperties={attemptNumber=2, jobId=923, from_trace_message=true}],stacktrace=AirbyteDbtError: 
Encountered an error:
Database Error
  ('HYT00', '[HYT00] [unixODBC][Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired (0) (SQLDriverConnect)'),retryable=<null>,timestamp=1675434737625]]]
We are running Airbyte Version 0.40.18 on our own Ubuntu Server: 22.04.1, with the Version 0.4.28 for the SQL Source Connector and 0.1.22 for the mssql destination. Any Ideas what could be the problem and how to fix it?
n
Hi, Leon! As a first step, please update your Airbyte instance and any connectors to the latest versions.
l
So I updated all the connectors and Airbyte itself, but it gives me the same error message.
n
Would you be able to attach the full logs? I see it says
This may indicate a problem with the data
, so I think it would make sense to look for a type error in the sync logs.
l
This is the whole Log of the most recent try
@Nataly Merezhuk (Airbyte) Is there any update regarding this topic?
n
Hi, Leon! Sorry for the wait! I'm still looking into this, but my first thought is that something is timing out in your MSSQL instance. I have also seen normalization issue arise when the destination configuration is incorrect. Just as a sanity check - could you recheck the configuration? Go through these requirements: https://docs.airbyte.com/integrations/destinations/mssql#setup-guide Could you try a test run without normalization?
l
Hi Nataly, without the normalization the connection works perfectly fine. I checked through all the settings/requirements and it should be fine, but I am still going to attach a screenshot to double check if something is wrong.
n
I found an issue that's also related to normalization: https://github.com/airbytehq/airbyte/issues/8806 I wonder if it would help us to dig into the dbt logs as they did in that thread. There is also a workaround here: https://github.com/airbytehq/airbyte/issues/8806#issuecomment-1209451064 Would you be able to do that? I'm continuing to look into this and will get feedback from my team!
l
So I tested the workaround but it didn't work. I made a new test db in all lowercase as well as the name of the destination table in lowercase and I still got the same error message. Thanks for continuing to look into this issue. I also tried to normalize the data I got from the Amazon Ads API and it also didnt work and I got the same error message again.
I have some news regarding this topic. We are currently in testing to also connect a Google Sheet File with our SQL Server 2019. And for testing purposes I used airbyte Cloud and by accident I did not switch the settings to Raw Data and the normalization worked. But when I tried it with the exact same settings on our local airbyte instance I got the same error again. So it may be a Problem with our local instance and not the data.
n
Interesting! I wonder what would be so different in the local instance
l
That is indeed very interesting. Is there a version difference in the Cloud and local? Or do you deploy on a different containerization software than Docker? And should I open an issue on github?
n
I'm not fully aware of what the version difference is between Cloud and OSS. I'd advise you to ask about that in the support chat in your instance!