MSSQL - Failed to fetch schema

Connector Questions & Issues
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu
  • Deployment: Docker
  • Airbyte Version: 0.40.25
  • Source name/version: MSSQL - 0.4.26
  • Step: creating source
  • Description:

I ended up taking over a project at the company that is running airbyte (0.40.25) and we are having two issue related to a source(MSSQL - 0.4.26 ).
issue 1:
a specific source configuration stopped working while others almost identical ones keep working, error log can be seen in the attachment.

cc862601_2cef_4dda_868e_035220f3bf2a_logs_9227_txt.txt (6.2 MB)

issue 2:
To further investigate the problem I decided to create that source again and realized that I cannot successfully create any source (MSSQL) with any configuration, not even the ones that are currently working, the error I received is in the second attachment.
Any help?

image

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

Hello.
In your logs I can see this:

No cursor field specified for stream attempting to do incremental

Do you have incremental streams from MSSQL? If so, can you check if a cursor column is selected? I think that by default when you select incremental sync mode, no cursor is selected and you can miss it by mistake. Also, check if your working connections have cursors configured. Something is different, for sure.