Node.js Teddious.js不支持的协议

在尝试使用冗长的命令连接到本地sql server数据库时，我看到以下错误。我尝试使用IP地址和本地主机，但它无法连接。已在sql server配置管理器中为MSSQLSERVER启用TCP/IP。我还验证了sql server browser是否也在运行

错误：

ConnectionError: Failed to connect to 127.0.0.1:1433 - 22996:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:c:\ws\deps\openssl\openssl\ssl\statem\statem_lib.c:1942:

at ConnectionError (E:\ExpressServer\kagetruckroutingappServer\node_modules\tedious\lib\errors.js:13:12)
at Connection.socketError (E:\ExpressServer\kagetruckroutingappServer\node_modules\tedious\lib\connection.js:1641:56)
at Socket.<anonymous> (E:\ExpressServer\kagetruckroutingappServer\node_modules\tedious\lib\connection.js:1405:14)
at Socket.emit (events.js:326:22)
at emitErrorNT (internal/streams/destroy.js:100:8)
at emitErrorCloseNT (internal/streams/destroy.js:68:3)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
code: 'ESOCKET'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! kagetruckroutingappserver@0.0.0 start: node ./bin/www
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the kagetruckroutingappserver@0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! Redacted

 E:\ExpressServer\kagetruckroutingappServer\app.js:36
            throw err;
            ^
    ConnectionError: Login failed for user 'sa'.
        at ConnectionError (E:\ExpressServer\kagetruckroutingappServer\node_modules\tedious\lib\errors.js:13:12)
        at Parser.<anonymous> (E:\ExpressServer\kagetruckroutingappServer\node_modules\tedious\lib\connection.js:1171:51)
        at Parser.emit (events.js:314:20)
        at Readable.<anonymous> (E:\ExpressServer\kagetruckroutingappServer\node_modules\tedious\lib\token\token-stream-parser.js:27:14)
        at Readable.emit (events.js:314:20)
        at addChunk (E:\ExpressServer\kagetruckroutingappServer\node_modules\readable-stream\lib\_stream_readable.js:298:12)
        at readableAddChunk (E:\ExpressServer\kagetruckroutingappServer\node_modules\readable-stream\lib\_stream_readable.js:280:11)
        at Readable.push (E:\ExpressServer\kagetruckroutingappServer\node_modules\readable-stream\lib\_stream_readable.js:241:10)
        at E:\ExpressServer\kagetruckroutingappServer\node_modules\readable-stream\lib\internal\streams\from.js:49:29
        at Generator.next (<anonymous>) {
      code: 'ELOGIN'
    }
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! kagetruckroutingappserver@0.0.0 start: `node ./bin/www`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the kagetruckroutingappserver@0.0.0 start script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     C:\Users\chris.kretman\AppData\Roaming\npm-cache\_logs\2021-04-29T12_50_43_835Z-debug.log

编辑-更改服务器后，现在出现不同的错误 我在代码中更改了服务器，现在我看到用户“编辑”的登录失败。你知道怎么解决这个问题吗

错误：

ConnectionError: Failed to connect to 127.0.0.1:1433 - 22996:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:c:\ws\deps\openssl\openssl\ssl\statem\statem_lib.c:1942:

at ConnectionError (E:\ExpressServer\kagetruckroutingappServer\node_modules\tedious\lib\errors.js:13:12)
at Connection.socketError (E:\ExpressServer\kagetruckroutingappServer\node_modules\tedious\lib\connection.js:1641:56)
at Socket.<anonymous> (E:\ExpressServer\kagetruckroutingappServer\node_modules\tedious\lib\connection.js:1405:14)
at Socket.emit (events.js:326:22)
at emitErrorNT (internal/streams/destroy.js:100:8)
at emitErrorCloseNT (internal/streams/destroy.js:68:3)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
code: 'ESOCKET'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! kagetruckroutingappserver@0.0.0 start: node ./bin/www
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the kagetruckroutingappserver@0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! Redacted

 E:\ExpressServer\kagetruckroutingappServer\app.js:36
            throw err;
            ^
    ConnectionError: Login failed for user 'sa'.
        at ConnectionError (E:\ExpressServer\kagetruckroutingappServer\node_modules\tedious\lib\errors.js:13:12)
        at Parser.<anonymous> (E:\ExpressServer\kagetruckroutingappServer\node_modules\tedious\lib\connection.js:1171:51)
        at Parser.emit (events.js:314:20)
        at Readable.<anonymous> (E:\ExpressServer\kagetruckroutingappServer\node_modules\tedious\lib\token\token-stream-parser.js:27:14)
        at Readable.emit (events.js:314:20)
        at addChunk (E:\ExpressServer\kagetruckroutingappServer\node_modules\readable-stream\lib\_stream_readable.js:298:12)
        at readableAddChunk (E:\ExpressServer\kagetruckroutingappServer\node_modules\readable-stream\lib\_stream_readable.js:280:11)
        at Readable.push (E:\ExpressServer\kagetruckroutingappServer\node_modules\readable-stream\lib\_stream_readable.js:241:10)
        at E:\ExpressServer\kagetruckroutingappServer\node_modules\readable-stream\lib\internal\streams\from.js:49:29
        at Generator.next (<anonymous>) {
      code: 'ELOGIN'
    }
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! kagetruckroutingappserver@0.0.0 start: `node ./bin/www`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the kagetruckroutingappserver@0.0.0 start script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     C:\Users\chris.kretman\AppData\Roaming\npm-cache\_logs\2021-04-29T12_50_43_835Z-debug.log