Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066.
See original GitHub issueIf set
options: { encrypt: true }
And send large data (83kb) to MS SQL then
at Socket.emit (events.js:205:15) at errorOrDestroy (internal/streams/destroy.js:107:12) at onwriteError (_stream_writable.js:438:5) at onwrite (_stream_writable.js:459:5) at internal/streams/destroy.js:49:7 at Socket._destroy (net.js:593:3) at Socket.destroy (internal/streams/destroy.js:37:8) at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:84:12) { code: 'EREQUEST', number: undefined, lineNumber: undefined, state: undefined, class: undefined, serverName: undefined, procName: undefined, originalError: Error: Connection lost - write EPIPE code: 'EREQUEST', number: undefined, lineNumber: undefined, state: undefined, class: undefined, serverName: undefined, procName: undefined, originalError: Error: Connection lost - write EPIPE
Software versions
- NodeJS: 12.4.0
- node-mssql: 5.1.0
- SQL Server: 2016
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I also faced the same issue. But it was resolved when I downgraded my node version to 10 and my same code started working. There has to be some issue with mssql with node 12.
This is a universal issue with cloud DB service providers with SSL connections, and not a problem with this library.
Would recommend investigating configuration options on the cloud DB service provider.