Problem uploading component from Knime Analytics Platform to KNIME Hub

Recently I encountered an issue while uploading a component I created to KNIME hub. The upload failed and the error message read:

An internal error occurred during: “Upload of Plate well expansion (Component - config) to My-KNIME-Hub:/Users/xxxxxxx/High-Throughput Screening Tools/Plate well expansion (Component - config)”. Server returned HTTP response code: 500 for URL:

May I know what it means? I have no problem uploading (or rather transferring) the same component into another local folder in my KNIME explorer. I would right-click the component → Component → Share to upload it to KNIME hub (in the KNIME explorer), and I could do this for all other components except this particular one. Is there something in my component that is preventing its upload to KNIME hub?

Your feedback would be much appreciated.


Hi @ndwulst

Can we know which version of KNIME AP are we using? Also did we try to disconnect the HUB and connect back again with user details. Post which can we try once again to upload the component to KNIME HUB?

Also can we know if there are any external nodes used inside the component?

Nagarjun S

Hi @nagarjun36

Thanks for getting back to me. I am currently using KNIME AP 4.6.1. I have disconnected the HUB and connected back again, but still encounter the same issue. I have attached the workflow with the component that I wanted to upload to the hub - the component is located at the top left corner. If I am not mistaken I don’t think I have any external nodes inside the component. Meanwhile, since I last posted the previous message, I was able to upload another component into the hub without much problem.


Hi @nagarjun36,

I too hit what appears to be a similar issue to @ndwulst this evening.

Attempting to share a specific component on the hub repeatedly resulted in the error pasted below. I tried creating another component (basically turned a single table creator into a component) and attempted to upload that and it worked without issue. I also tried logging out of the

The component in question contained only standard KNIME nodes, and the only thing I can think of, of note, was that the java snippet node has this “Additional Bundle” specified.

I’m on KNIME AP 4.6.2 [Edit - and I’ve just updated to 4.6.3, but same problem occurs]

The workflow containing the component is here:
Test ip address in subnet.knwf (3.4 MB)

– details of error –

java.lang.RuntimeException: Server returned HTTP response code: 500 for URL:
	at com.knime.explorer.server.internal.view.actions.WorkflowUpload.runSync(
	at com.knime.explorer.server.internal.view.actions.WorkflowUpload$
Caused by: Server returned HTTP response code: 500 for URL:
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
	at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Unknown Source)
	at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source)
	at java.base/$ Source)
	at java.base/$ Source)
	at java.base/ Source)
	at java.base/ Source)
	at java.base/ Source)
	at java.base/ Source)
	at java.base/ Source)
	at com.knime.explorer.server.internal.view.actions.WorkflowUpload.uploadWorkflow(
	at com.knime.explorer.server.internal.view.actions.WorkflowUpload.runSyncInternal(
	at com.knime.explorer.server.internal.view.actions.WorkflowUpload.runSync(
	... 2 more

Hi All,

thanks for reporting this and thank you @takbb for sharing a workflow/component to reproduce the issue. We have recently released a change that should hopefully fix the issue.

Kind regards


Thanks @marvin.kickuth , I’ll give it a try in the next few days with components I think would have previously failed and let you know the result.

Edit: and initial indications are good as I was able to upload my IP Subnet Address Comparison component :slight_smile:

Best regards.


This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.