I can´t "Save" or "Save As" an workfloe in Knime 5.3.0 (the problem is back)

The error message …

FATAL SaveAsRunnable File not found - this exception will be re-thrown as an InterruptedException.
ERROR WorkflowEditor Could not save workflow: File access problems: C:\localK\w5\XXXXX\dev\0100E\XXX_k5_44\renew auth (#357)_re_Auth (#83).savedWithData (Access is denied)
FATAL InplaceSaveRunnable File not found - this exception will be re-thrown as an InterruptedException.
ERROR WorkflowEditor Could not save workflow: File access problems: C:\localK\w5\XXXXX\dev\0100E\XXX_k5_43\config (#324)\auto (#273)\min (#272).savedWithData (Access is denied)
FATAL InplaceSaveRunnable File not found - this exception will be re-thrown as an InterruptedException.
ERROR WorkflowEditor Could not save workflow: File access problems: C:\localK\w5\XXXXX\dev\0100E\XXX_k5_43\config (#324)\auto (#273)\min (#272).savedWithData (Access is denied)

This happens when I use “Save” or “Save As”, after a while (minutes) after I have changed and run the workflow, even after resetting all nodes.

To try to work around this issue up to version 5.2.5 I used to export the workflow, but it doesn’t work anymore.

Hi @Aldo_Barduco,

based on the error message it seems that either your user has no write permissions on the folder C:\localK\w5\XXXXX\dev\0100E\XXX_k5_43\config (#324)\auto (#273)\min (#272) or the file C:\localK\w5\XXXXX\dev\0100E\XXX_k5_43\config (#324)\auto (#273)\min (#272).savedWithData is not actually a file, but a folder. Maybe some sync engine is working on the background? The path looks different to the “usual” Windows paths I know. Is your workflow located in some special location like a network drive?

Best,
Manuel

3 Likes

Hi Manuel,

It seems that way, but it’s not true. The user has full read/write rights this local drive (Windows Server). And everything works until version 3.x and 4.1.
The same problem used to happen in version 2.1x.

IMHO the problem is related to “node resetting” process, because after resetting all nodes it should not have any node with data to be saved.

Kind regards,

s Aldo

IMHO the problem is related to “node resetting” process, because after resetting all nodes it should not have any node with data to be saved.

The problem has been fixed in version 5.3.1, at least on local drives.
The issue PERSISTS on network drives.

Hi Aldo,

I asked around in the dev team. We did not change the save logic of a workflow in quite some time. We also had a look at the code again, and cannot see anything obvious like accidentally trying to access a path with trailing slash as a file.

Also, there are no internal tickets that sound related and try to fix a “Access is denied” problem – for neither of the versions you mentioned. I looked over all 47 closed tickets for 5.3.1 and neither of them had something to do with the code in question. Therefore, we cannot think of a reason related to Analytics Platform why it would suddenly work on local drives in 5.3.1. It must be some permission problem or something with the Windows setup you are using.

But, I found some related problem in the forum: Unable to save_as workflow due to File access problems Math Formula node (Access is denied)

A helpful link to Microsoft suggested that the # character might be forbidden in some organizations’ OneDrive or SharePoint setup: Restrictions and limitations in OneDrive and SharePoint - Microsoft Support

Some organizations don’t yet support # and % in names. If you’re a global admin or SharePoint admin in Microsoft 365, see Enabling # and % Support on the SharePoint blog to learn how to allow these characters.

To diagnose this a bit further, you can put a test file containing the # character in the filename into the workflow’s data directory, e.g. C:\localK\w5\XXXXX\dev\0100E\XXX_k5_43\data\testfile #123.csv, and read it with a file reader node and write to it with a file writer node. It may also help to put that test into a loop with a wait node so it is executed periodically. This may be needed because you wrote that the problem happens “after a while (minutes)”.

Regarding node resetting:
The file is not absent if all nodes are reset. It is always present if a workflow is saved normally (“Save” or “Save As”). It is only absent if it is exported without data (link to source). So the particular file should not be the problem.

Best,
Manuel

2 Likes

Hi Manuel,

First of all thank you for your answer and your time and attention to this issue.
I think the easily way to answer you is that is the same machine (same machine image) and the same network drives I´ve been using in Knime version 3.x and 4.x. Nowadays, in Knime 4´s workkflows I don´t have this issue.
The same problem used to happen in version 2(.8?), but it was a very long ago.

FATAL SaveAsRunnable File not found - this exception will be re-thrown as an InterruptedException.
ERROR WorkflowEditor Could not save workflow: File access problems: K:\k\w5dev\XXX\dev\test_SaveWithDataError 4\Extract Sys (#649).savedWithData (Access is denied)
FATAL SaveAsRunnable File not found - this exception will be re-thrown as an InterruptedException.
ERROR WorkflowEditor Could not save workflow: File access problems: K:\k\w5dev\XXX\dev\test_SaveWithDataError 6\Extract Sys (#649).savedWithData (Access is denied)
test_SaveWithDataError 5.knwf (66.5 KB)

Hi Manuel (@hotzm ),
To contour this problem I edit it in Knime Hub where it works fine. When I finish the workflow editing I export it to .knwf (with the “Reset Workflow(s) before export” option set) file and I imported it after to the network drive.