IanSims

@gsamal Yeah it looks like something triggered the `cancel` for the request while it was processing, but the log outputs don't show what started the `cancel` event in the first...

Thanks @dhensby, we'll take a look!

@sergueis Are you seeing the same issue when using tedious directly?

@mikermcneil Any progress update? Were you able to figure out the issue?

Hi @salman-ud, can you provide a repro, the error stack, and what tedious version you're using?

Hi @MartinJLee, this is a known issue. Checkout #678. The issue is that `Many (but not all) of the data types supported in SQL Server do not map 1:1 to...

Hi @jon-shipley, this error is fixed in the latest version of tedious (11.0.4). Is it possible for you to upgrade?

Hi @malarcherc, can you provide the script you attempted to run? It might be because the server IP is not found in the config, in which case you can try...

@jokarl `node-mssql` uses an old outdated version of `tedious` so I recommend using the latest `tedious (11.0.6)` if you can. I apologize for the documentation not communicating the new API...

The [documentation has been updated](https://tediousjs.github.io/tedious/getting-started.html)! I hope this clarifies the API a bit better. Sorry for the confusion earlier!