Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure - ECONNRESET when running long SQL using Tedious Driver on Node.js 12.6+ #928

Closed
palczewski opened this issue Oct 21, 2019 · 8 comments

Comments

@palczewski
Copy link

Node-mssql/Tedious will generate the following error when running a long SQL string on Node.js 12.6+
RequestError: Connection lost - write ECONNRESET

Expected behaviour:

Should execute successfully

Actual behaviour:

RequestError: Connection lost - write ECONNRESET

Recommended resolution

Please see:
tediousjs/tedious#923

Tedious needs to be upgraded to a newer version

Software versions

  • NodeJS: 12.13.0
  • node-mssql: 4.3.7
  • SQL Server: 14
@willmorgan
Copy link
Collaborator

You could try upgrading to 6.0.0 which uses a much newer version.

@frco9
Copy link

frco9 commented Oct 24, 2019

@willmorgan, v6.0.0 is still in beta is it safe to use ?

@jtsmedley
Copy link
Contributor

jtsmedley commented Oct 24, 2019

Ditto this issue with MSSQL v5.1.0

@willmorgan
Copy link
Collaborator

@frco9

v6.0.0 is still in beta is it safe to use ?

Your issue states that upgrading Tedious is necessary; 6.0.0 has that newer version, so maybe try and see if that works?

The beta is not inherently unstable but might have some extra functionality added or further bugs fixed.

@baiganhong
Copy link

Recently I ran into same error with Node 12.13 on MSSQL module 5.1 when I run a long update statement with parameterizing more than 53 fields, but when I reduced to 52 fields, it succeeds. In addition, now my workaround is using non-parameterized update statement string. That is OK.
BTW, there is no problem with Node 10.16.

@dhensby
Copy link
Collaborator

dhensby commented Nov 3, 2019

There is no specific node 12 support at this time and the tedious version required is not supported in v5, you must use v6.

@dhensby dhensby closed this as completed Nov 3, 2019
@Schroet
Copy link

Schroet commented Nov 20, 2019

So guys, any ideas what to do ?

@dhensby
Copy link
Collaborator

dhensby commented Nov 20, 2019

Use v6 of the lib

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants