Thanks hornm for your suggestion
I tested that and unfortunately it didn’t affect the results.
For the avoidance of doubt I tried both adding both
java.net.useSystemProxies=false
and
-Djava.net.useSystemProxies=false
to the .ini file
Note that we also set the following options when trying to fix the extensions issue
-Djavax.net.ssl.trustStore=NONE
-Djavax.net.ssl.trustStoreType=WINDOWS-ROOT
I did however notice an additional detail. When I restart KNIME (on the vpn) and open the workflow, if the first thing I do is open a column filter node (which uses modern UI) then the dialog loads. And then if I execute the reporting labs component it executes successfully.
However, if I restart KNIME and attempt to do those operations the other way around, the reporting labs component fails and all the modern UI dialogs then break.
Note that in batch mode, the dialogs are never opened manually, so when the reporting labs component executes it fails. Hence why they always fail on our internal servers
This was the case during my testing today, but there must be other potential ways to trigger the dialogs to fail as it happened on a few occasions before we started using the reporting labs extension
Edit: Also, are you sure the event loop exception is unrelated? I get that error pop up again in the Error Log every time I attempt to open a broken dialog