Not only can I get RH8 to fail on the Force Update, I can get it to crash catastrophically in a Windows error! I'm using the TCS 2.0 with FM9 and RH8. I have one master book in FM that consists of 4 .fm docs and 60 sub-books. Each of the sub-books has 4 .fm docs within them. Those docs are fairly empty right now (since we're just starting the authoring process) but are expected to run 50-200 pages each when finished. Even trying to do the initial linking to a project this size is causing issues - RH seems to choke on large FM books. At first I thought it was the network causing issues, so I created local c:\ RH projects to test that (while still continuing to pull the FM content off the network). That didn't work either, so I copied the FM content locally too - still no luck. I contacted Adobe Support and they suggested shortening the FM filenames to remove any spaces and ampersands that I had been using. After doing that I had better luck initially linking the master.book, but RH will still choke when doing an Update when it gets about 50 sub-books into the task. At that point you get the silly "Import session failed. If this error continues please contact Technical Support" with an OK button to continue. Clicking OK still lets the "Processing FrameMaker Document(s)" dialog continue processing, but it racks up immediately on the next .fm doc with the same message. Sometimes RH will just shut itself down after repeated OK's; sometimes it appears that it has completed, but if you do a Save or Save All, a Windows error is thrown, and you are kicked out. Just to experiment, I tried doing an import of the FM files (I know RJ all told us never to do this in his eLearning session, since it defeats the point of the workflow, but a broken workflow doesn't accomplish anything either!) I had better luck importing, but RH threw a message each time it tried to process a FM sub-book, saying something like "Unable to open xxxx.book. Not a valid FM book or FM not installed." This wasn't true at all because I had my copy of FM9 open in the background, and opening the offending book in FM worked fine. There was an OK button to continue and after clicking 60 times, it appeared to have finished. Since this isn't the way we were intending to work, I'm still experimenting with initially chopping out some of the sub-books in FM and then linking it in a new RH project. So far it hasn't crashed, but now my masterTOC and masterIX files aren't being converted into RH TOC and Index files (even though I've told it to do this in the Properties > Content Settings tab of the master.book in the RH Project Manager). I'm going to go back into FM and add more sub-books to see if RH will choke on them when the project is Updated.
... View more