In general, any standard tool will be able to access Denodo through [JDBC interface](https://community.denodo.com/docs/html/browse/7.0/vdp/developer/access_through_jdbc/access_through_jdbc#access-through-jdbc), [ODBC interface](https://community.denodo.com/docs/html/browse/7.0/vdp/developer/access_through_odbc/access_through_odbc#access-through-odbc), [ADO.NET Data Provider](https://community.denodo.com/docs/html/browse/7.0/vdp/developer/access_through_an_ado.net_data_provider/access_through_an_ado.net_data_provider#access-through-an-ado-net-data-provider) and using the [SOAP and REST Web Service interfaces](https://community.denodo.com/docs/html/browse/7.0/vdp/administration/publication_of_web_services/publication_of_web_services).
But in order to connect to Denodo from Node.js, you could use Denodo JDBC driver since that could be the better way to connect Denodo from it.
You could also refer to the tutorial [Connecting from your application - JDBC Clients](https://community.denodo.com/tutorials/browse/basics/4connect1jdbcclient) for more information.
In addition to that, to debug the root cause of the error you are experiencing, you can also refer** vdp.log** which is available in <DENODO_HOME>/logs/vdp.
Hope this helps!