Skip to main content
Known Participant
February 23, 2009
Question

Book Changes in FM cause RH to crash

  • February 23, 2009
  • 1 reply
  • 681 views
When I have an existing RH project with a reference to a FM book, and I then add a chapter to the FM book OR I rename chapters in the book, and then update my RH project where the book is referenced, my project hangs. I have tried Update, Force Update, and Update All...same result.

I am using RH 7.02 w/ FM 8.

RH crashes while updating many times, the topics don't update correctly, and ultimately, right now I am left with a RH file that just doesn't match my FM book.

The new chapter was added to RH as a folder, not as a referenced file.

I am thinking if I can't get an answer here I need to recreate my project, which also includes re-mapping styles.

Does anyone have steps or a workaround that makes RH behave correctly and update the project with newly-added FM book chapters? I would not like to have to do this each time we change the book structure in FM.

Thanks,
Rita Norris
This topic has been closed for replies.

1 reply

Mayank_Agrawal
Participating Frequently
February 24, 2009
Here are the possible explanations and suggestions.
It could be possible that the newly added chapters or the book is locked by FrameMaker or by any other user that may result in such a situation. Please make sure that the files/book are not locked(look for .lck files).
If you want to create a project from scratch, you can reuse the RH-FM style mapping by using the Export/Import of style mapping settings.
You may also try RH8 which is much better in performance and has most of such issues resolved.
rita_nAuthor
Known Participant
February 24, 2009
Thanks for the response. Unfortunately, this occurs when files are not locked. I still get crashes, and I when I view details on the error there are multiple exceptions listed. We can import the mapping styles, but it still takes a lot of extra time to recreate a project, unfortunately.

Still hoping for a workaround before my deadline is due. We may be upgrading sometime in the future, but I see this as an issue that needs to be fixed...I would hope it would be fixed in both versions, with a fix not dependent upon an upgrade, but maybe that is not the case.