Skip to main content
Attempting to edit a workbench file this morning but the file in question won't open.

 

 

Choosing file->open and selecting the file does nothing - no error, workbench remains blank, wording in title bar still displays Untitled - NONE, file name isn't in the list of recently open files.

 

 

The script itself works fine and runs daily via a .bat file

 

 

We have upgraded to the latest service pack since I last looked at this file but it only seems to be this file that is affected.

 

 

Is there anything I can try to get this file to open up in workbench?

 

 

 

Hi,

 

 

I suggest sending your workspace file to Safe. They might be able to isolate the problem and to decide whether it is due to a bug somewhere.

 

 

David
I found an errant fmw.recover file that appears to have been created a couple of weeks ago when the script was running overnight. Deleting that solved my problem
I found an errant fmw.recover file that appears to have been created a couple of weeks ago when the script was running overnight. Deleting that solved my problem

 

Had the same issue. The FME workspace did not open. Deleting the fmw.recover resolved it for me. Thanks.

Definitely sounds like an opportunity for some enhanced error checking. We'll get on it. @egomm if you still have the .recover file in your trash, would you mind recovering it and sending both it and the workspace to support@safe.com? Failing that, I'm we'll do our best to synthesize a corrupt .recover file and see if we can reproduce the issue...


Definitely sounds like an opportunity for some enhanced error checking. We'll get on it. @egomm if you still have the .recover file in your trash, would you mind recovering it and sending both it and the workspace to support@safe.com? Failing that, I'm we'll do our best to synthesize a corrupt .recover file and see if we can reproduce the issue...

4 years and 3 jobs ago, I don't still have the file in my trash @daleatsafe 😃
4 years and 3 jobs ago, I don't still have the file in my trash @daleatsafe :-D
Oh yikes. I guess I should look at the timestamps of posts a bit more carefully!

 

 


Reply