i am new in this forum and hope someone could help me. The hints I’ve found up to know didn’t solve my problem.
I’ve a knime workflow (created under MAC) established in august. As I opened the WF yesterday to carry on working on it ALL nodes are gone which means I glanced in an empty editor.
New Workspace, new knime version, exporting and importing the WF, deleting the knime log file, installing knime under a virtual windows machine and importing was unsuccessful. Even copying the complete directory in a new workspace including all files and subdirectories (remark in which i can see all nodes, the workflow-file and svg-file) came to the same result. As far as I open the workflow I see an empty editor with no nodes in it. Does anybody has another idea what i still could do to restore the workflow.
In a terminal window, could you change directories to the location of the original workflow, then do an: ls -laR
then copy and paste the contents of the terminal window into a text file?
Then, using 4.0.1 could you create a new workspace directory, then import the workflow, then ZIP up both of those log files (.metadata/knime/knime.log and .metadata/.log) plus the above text file and attach the ZIP to your next reply?
Thanks - it is odd that your knime.log file is empty - did you grab it after you did a File → Import KNIME Workflow... ? Was the timestamp on the file appropriate to when you made a brand new workspace? Maybe try going to Preferences → KNIME and set the log level to INFO?
As far as the ls -laR i was hoping you would do it for just the workflow in question, as opposed to your old workspace. Could you let me know the name of the workflow you’re seeing these problems with?
well see above:
Thanks - it is odd that your knime.log file is empty - did you grab it after you did a File → Import KNIME Workflow...no I didn’t? Was the timestamp on the file appropriate to when you made a brand new workspace? *yes it was *Maybe try going to Preferences → KNIME and set the log level to INFO?
As far as the ls -laR i was hoping you would do it for just the workflow in question, as opposed to your old workspace. Could you let me know the name of the workflow you’re seeing these problems with? I am not sure gotten this clearly. The ls -aR file represents the OLD workspace and the corrupt WF is “Budgetplanung_Folgejahr”.
In addition find enclosed the old Logfile as mentioned in my request I had removed from the old workspaceknime_old.log.zip (398.3 KB)
. An also the ls -laR from the current space ls-lar_new_test_space.zip (15.6 KB)
Hmm… i think there’s some confusion going on here, at least on my side. Budgetplanung_Folgejahr is not a workflow - it is a directory that has a bunch of workflows in many directories underneath it.
I was under the impression that you were attempting to import a single workflow. ?
Additionally, once we nail down which single workflow you’re attempting to import without success, it would be helpful to see the knime.log file from a fresh workspace, after the import attempt has finished.
Hi quaeler,
now the confusion is complete to me . Yeah we are talking about one single WF.
No, Budgetplanung Folgejahr is the name i had given to the wf in Knime. Please see the attached screenshot which i think is the workflow. Hope I haven’t an absolute wrong understanding which a Knime WF is.
I right now once again imported the workflow in a new workspace and i can’t help the Logfile once again is empty.
To import the steps were as followed: 1.Create a new subdirectory. 2. Change Workspace. 3. executing the knime functionality import… using a “knfw” file.
Ah… yes - there are a number of directories there that represent nodes and a workflow.knime file, but there is also an Example Workflows directory peer to the nodes which it, itself, contains many workflows.
If you move the Example Workflows directory out of your original working and try to import that workflow into a new workspace, do you have better luck?
(The workflow.knime file in the second ls -laR output you provided is suspiciously small for the number of nodes you have present:
-rw-r--r-- 1 Michael staff 1581 15 Sep 20:58 workflow.knime
For example, the example one in ./Budgetplanung_Folgejahr/Example Workflows/Basic Examples/Building a Simple Classifier is 31KB with 9 nodes.
Is the workflow.knime also only ~1.5KB in the original workflow’s directory too?)
And even the trial using the option -clean in a windows machine didn’t help. So being clueless I suppose I’ll give up my restoring activities and will develop the workflow again manually. Nevertheless thanks a lot for you effort and up to next time.
cheers Miky.
Since you’re on a Mac - could you try and time machine a backed up version of that workflow.knime file?
I suspect if you do in a terminal:
more "./Budgetplanung_Folgejahr/Example Workflows/Basic Examples/Building a Simple Classifier/workflow.knime"
you will see a whole bunch of stuff, while if you do,
more ./Budgetplanung_Folgejahr/workflow.knime
you will see almost nothing - and the problem being that somehow, at some point, this file which describes the contents of your workflow, got altered.
:- /
No - the terminal commands were more to visually demonstrate to you what a ‘complete’ workflow.knime file looks like so that when you look at the quite small one at ./Budgetplanung_Folgejahr/workflow.knime you could understand the scope of what is missing.
If you don’t have a backup of this file, i’m afraid you’ll have to reconstruct the workflow by hand.