name: 'RequestError', message: 'SqlContext Error. Failed on step "__result__" with: "No connection is specified for that request."', code: 'ENOCONN', step: '__result__'

[corymickelson]

So, this is the result that I get when trying to run in a lambda. The query runs and returns fine when executed locally, any idea's why or what I may be able to do to get this to work on aws lambda. Thanks

[jhovgaard]

Same experience here, but from Windows to Ubuntu.

[takotuesday]

I am experiencing the same issue. Locally everything works fine but when deployed to my Heroku-like platform I get the following error:

{
	"name": "RequestError",
	"message": "SqlContext Error. Failed on step \"__result__\" with: \"No connection is specified for that request.\"",
	"code": "ENOCONN",
	"step": "__result__"
}

@calvinb @Prestaul it'd be greatly appreciated if we could get some feedback on this. I was originally using node-mssql, and was experiencing a similar problem. I thought I might be able to leverate seriate's easy global connection and that would solve the issue. My config looks like this:

var conOptions = {
  user: user,
  password: password,
  server: server,
  database: database,
  pool: {
    max: 10,
    min: 4,
    idleTimeoutMillis: 30000,
  },
};

[calvinb]

@takotuesday Looks like other folks are having the same problem with other tedious-based libraries. I just ran across this solution that sounds like it has worked for some: tediousjs/node-mssql#383 (comment)
I'm interested to hear if it works for you.

[takotuesday]

@calvinb it seems like that solution requires me to use node-mssql instead of seriate. Is that the recommended solution? Also, after trying the implementation, I am still getting connection errors, only in this instance they are more generic.

{
"name": "ConnectionError",
"message": "Connection is closed.",
"code": "ECONNCLOSED"
}

[calvinb]

@takotuesday If you see a simple way we could get seriate to use the same approach as node-mssql does to work in this scenario, please let us know or submit a pull request. Whether I would recommend switching libraries would depend on how the estimated effort of switching compared to the estimated effort of fixing seriate for this use case.

[calvinb]

@takotuesday To clarify, seriate already uses node-mssql; the fix to seriate would likely just be adding a seriate option to use the node-mssql option that fixes the problem.

[billsinc]

I added "name": "default", to my config and it seemed to fix the issue.