MS SQL Server: "I/O Error: Socket closed" by first execution run

[D00mi]

Hi everyone,
I have a rather strange problem: When I open a workflow and press “Execute all” (or just the Connector node), it takes several seconds and prompts the following error:

Status: DataLoadError: Microsoft SQL Server Connector 3:337
Status: DataLoadError: Loading model internals failed: I/O Error: Socket closed

Now I can press “Execute” again, and it immediately connects successfully to the server, and everything is okay.

My problem is: I cannot run it in batch mode like this, since it always stops because of this error.
Does anyone have any idea what could be causing this problem? Would it be possible to run the same node twice within the workflow (as a work araound…)?

Many thanks in advance!

My Settings:
MS SQL Server 2019 Standard

Driver Name: jTDS for Microsoft SQL Server
Authentication None/native authenication
ssl true
integratedSecurity true
Automatically reconnect to databse true
Restore database connection true

[D00mi]

Okay, I was able to “solve” the issue with a workaround: I placed the SQL request in a loop with try and catch blocks, and repeated the loop until there were no errors anymore or the batch took too long to finish. I didn’t know about this feature before. Hopefully, it will work in a stable manner

[ScottF]

Hi @D00mi and welcome to the forum.

Nice use of the Try/Catch - is it still working for you? Thanks for posting your workaround to benefit everyone!