KNIME Server Connector - No session cookie available

KNIME Server
1

Hi,

I updated the KNIME Analytics Platform from version 4.6.5 to 4.7.2 .KNIME Server version is 4.16.3.

I am using the KNIME Server Connector node to connect to the server but after the update I get the following error:

ERROR KNIME Server Connector 5:3846 Execute failed: Error occurred during login: No session cookie available.

Is this a bug?

Best

A.

2

Hello,

So we have one desktop (unknown OS) running KNIME AP 4.7.2, connecting to one server host (unknown OS) running KNIME Server (KS) 4.16.3.
AP workflow has KNIME Server Connector, and when executed, produces:
Execute failed: Error occurred during login: No session cookie available.

  • is the KNIME Executor (KE) also on the same host as the KNIME server?
  • Are there any other hosts involved, such as firewalls, VPN tunnels, proxies, or load balancers?
  • is the KNIME Executor also upgraded to 4.7.2?
  • Do you have AP logs (knime-workspace/.metadata/knime/knime.log)?
  • Do you have Server/Executor logs for the same timeframe?

Note that if you would like to provide logs and there exists a possibility for them to contain proprietary or confidental data in them, please do not post them here, but, rather, reach out to us directly at support@knime.com for further assistance.

Thank you,
Nickolaus

3

Hallo @NDekay ,

thanks for your reply.

  • is the KNIME Executor (KE) also on the same host as the KNIME server?
    → Yes, the KE runs on the same host. We just updated the server (KNIME Server Ubuntu 20 Server LTS). The KNIME AP runs on Windows 10.

  • Are there any other hosts involved, such as firewalls, VPN tunnels, proxies, or load balancers?
    → We have but the same settings as before and with the old KNIME AP version 6.5, the connector still works

  • is the KNIME Executor also upgraded to 4.7.2?
    → Yes, the Executor is version 4.7.2.

  • Do you have AP logs (knime-workspace/.metadata/knime/knime.log)?

  • Do you have Server/Executor logs for the same timeframe?

→ In the end I did not need the KNIME Server Connector node with the new Call Workflow (Table Based) node included (I had to update my workflow).

I still got the error message but for me the problem is solved (Not sure if the KNIME Server Connectore node is still needed with the new configuration options in the Call workflow nodes. Interstingly, the Mountpoint Connector node works to connect to the server. I did not know of this node before.)

Many thanks.

Best

A.

4

Hello,

I am glad that you were able to find a resolution through adjusting your workflow.
If you experience any further issues, please let us know.

Thank you,
Nickolaus