This was working earlier, the only change I’ve made that correlates to this functionality breaking down is updating 35 nodes. I created a component for various graphs and tables, created the report view in the component. I marked the component to allow reporting, and I have a report template node in the previous component set to paper size A3 and landscape layout. The view from the second component does show my various graphs and tables as designed. However, the output isn’t working and I’m getting an Inactive Port Object error. I’ve expanded the component and started over, but still gettig the error:
I’ve closed down KNIMNE and reopened - expanded the component and recreated the component, rebooted computer. Any thoughts on why this would become inactive? I’ve also tried ‘deleting’ the port to recreate and see if that would help, but won’t allow me to delete.
it might be that the internal report fragment generation is taking longer than the default timeout, so the port gets disabled. This can have many causes, large report views (tables…), complex views, system under load, …
Since KNIME AP 5.3.2 (and in 5.4, too), you can configure the timeout by adding the property to the knime.ini:
For example, -Dorg.knime.reporting2.report_generation_timeout_seconds=600 will set it to 10 minutes. It goes anywhere after the vmargs line.
If that does not help, does it show anything if you hover over the disabled port? Is there anything interesting in the knime.log in the workspace?
Shouldn’t the left side be a visual representation? I’m noticing that the report isn’t showing the information as well. I have it as the header in the component layout view, but it isn’t populating.
Yes, it should contain the preview on the left-hand side, like any other View (Bar Chart, …). I’ll ask internally, if anyone has an idea what could have gone wrong.
My version now reflects 5.3.3. I’ve rerun the node and it runs quickly, and correctly. Either i somehow updated the version and didn’t reboot, or something got ‘stuck’ in my system? Under ‘about’ it now reflects 5.3.3 and the node runs properly:
Not sure what happened but it seems to now have been corrected (i also had a notification that I had three nodes to update, which I did, before rebooting).