Skip to main content
Solved

Manually trigger a recover

  • October 27, 2017
  • 3 replies
  • 371 views

Folks,

I have an odd scenario. I was working on a workspace and my PC crashed. It was not FME related. In fact it was during a file copy and there's some issue with my network card driver.

I had unsaved edits.

I found a recover document that points me to another location with a "wp_" prefix file. It looks like this is some kind of log of edits. Checking the "wp_" file it seems to have most of my edits.

The odd thing is on restart I wasn't given the option to recover.

1. is it possible to trigger a recover?

2. is it possible to parse the "wp_" and get some if not all the pending edits back?

Thanks in advance

Best answer by mark2atsafe

One thing it depends on is whether you have ever saved the workspace. If you've saved it previously then there should be a recover file. As long as it has the same name as the workspace file, it should trigger a recover on reopening.

However, if you've never saved the workspace at all, you won't be prompted to recover. There might be a recover file and workspace file stored temporarily on your system, but you'd have to hunt them down. But if you can, rename the recover file (might be the wp file here) to the same name as the workspace and try opening it again (but keep a backup, just in case something screwy happens).

View original
Did this help you find an answer to your question?

3 replies

david_r
Celebrity
  • October 27, 2017

The dialog asking your to recover your workspace is based on the presence of a workspacename.fmw.recover file, so if that file is missing you won't be prompted.

As an alternative solution you could perhaps look for any recent wb_recovery_* files in your TEMP directory and try to rename them as a .fmw file to see if you can recover something that way.


mark2atsafe
Safer
Forum|alt.badge.img+44
  • Safer
  • Best Answer
  • October 27, 2017

One thing it depends on is whether you have ever saved the workspace. If you've saved it previously then there should be a recover file. As long as it has the same name as the workspace file, it should trigger a recover on reopening.

However, if you've never saved the workspace at all, you won't be prompted to recover. There might be a recover file and workspace file stored temporarily on your system, but you'd have to hunt them down. But if you can, rename the recover file (might be the wp file here) to the same name as the workspace and try opening it again (but keep a backup, just in case something screwy happens).


  • Author
  • October 29, 2017
mark2atsafe wrote:

One thing it depends on is whether you have ever saved the workspace. If you've saved it previously then there should be a recover file. As long as it has the same name as the workspace file, it should trigger a recover on reopening.

However, if you've never saved the workspace at all, you won't be prompted to recover. There might be a recover file and workspace file stored temporarily on your system, but you'd have to hunt them down. But if you can, rename the recover file (might be the wp file here) to the same name as the workspace and try opening it again (but keep a backup, just in case something screwy happens).

Thanks Mark. This is probably one of my oldest workspaces so yes there were many and frequent saves over the past few months. Oddly another workspace(completely different name and project) that I wasn't working on did offer a recover. I did try the fmw.recover rename and got an odd "different version" type error message and no result. As nothing really worked I used the "wp_" prefix file and manually transcribed the changes.

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings