Deploying a Workflow on KNIME Server with Microsoft SQL Server Connector Using Server Credentials

Hi KNIME Community,

I’m trying to deploy a KNIME workflow to KNIME Server that connects to Microsoft SQL Server using KNIME Server credentials. The workflow runs fine locally but fails on the server with:

Question:

  1. How can I correctly configure the Microsoft SQL Server Connector to use KNIME Server credentials?
  2. Should I switch to the Microsoft JDBC Driver? If so, how do I set it up on KNIME Server?
  3. Are there any additional server-side settings required for authentication?

Any guidance would be greatly appreciated. Thanks!

@Heldyyyyy Can you clarify if you are running this workflow on KNIME Server or KNIME Business Hub? My understanding of Secrets retriever is that it is for use with Hub’s Secret storage functionality in order to retrieve secrets stored in Hub. Are you storing your secrets in Hub?

From your screenshots the configuration looks correct (assuming you are using Hub). You may find it beneficial to add a KNIME Hub Athenticator node in front of the secret retriever in case you need to run the workflow outside of Hub. The error seems to indicate that the secret was retrieved as it has the username, but login is failing. This could be due to the driver the MS SQL Server Connector is using. I would recommend using the latest available driver instead of the deprecated jTDS driver.

1 Like