Help!! FrameMaker crashes when I attempt to open certain book files. I am using FrameMaker Version 9.0 p255 on Windows XP pc. Other details:
- This problem began mid April about 5 weeks ago. Some book files are just fine while others crash the system. The internal error codes listed with each crash have overlap but are not identical (they all have at least 9004). The last one stated: “Internal Error 9004, 5242025, 5220528, 6335542. FrameMaker has detected a serious problem and must quit…”
- Attempting to open individual .fm files within the crashing book file does NOT cause a crash.
- Tried opening it through windows explorer and directly through Frame with the same result.
- Failed fixes attempted per forums.adobe.com: rebooting, renaming the linguistics library, deleting linguistic library in case it was corrupted (C:\Documents and Settings\jchen\Application Data\Adobe\Linguistics\Dictionaries\FMUserDictionary\all), changing book file name, replacing book file with a backup copy of the book file, and recreating book file. In the past, replacing book file with an archived copy worked but most of the time it did not work. Sometimes recreating the book file worked, but not always.
- I believe I cannot do a MIF wash since I need to be able to OPEN the book file first in order to be able to save it as a MIF file??
- Tried to install Frame 9 updates from http://www.adobe.com/support/downloads/product.jsp?product=22&platform =Windows, but got an error message stating, “You do not have correct version of FM install on your system. This patch installer will work only with Version 9 p196. Patch installer will quit now.”
- I’ve emailed fmerror@adobe.com (per crash message window) and have not received suggestions on how to fix. L
- On a side note, my MS Word 2007 is acting super buggy lately… where when I try to do basic things like performing a “Save As”, etc., the screen goes blank or partially blank and takes some time to recover.
Besides reinstalling FrameMaker 9, does anyone have any suggestions? Hoping to reach the root of the problem as this issue keeps resurfacing in slightly different forms.
Thanks.
Judy