Copy link to clipboard
Copied
Copy link to clipboard
Copied
When you start FM, do you see the FM logo window with the display of the components being loaded? Does the crash occur at a specific component?
Have any system patches,new softwarem etc. been installed since you last used FM?
Copy link to clipboard
Copied
Arnis,
Yes, exactly, when I try to start FM 9, the FM logo displays, the Fonts load, and then during the Localization process, the crash occurs.
The only software updates that were pushed by Microsoft since I last used FM 9 without problems were Windows Defender updates. I'm running XP Pro. I've restarted my laptop with Windows Defender disabled, but the crash still occurs. (I have not yet tried to uninstall Windows Defender.)
Hope to find an answer soon ...
Copy link to clipboard
Copied
A bit of a long shot, but since the crash seems to be happening when you hit the Localization step, have you added or used your personal or site dictionaries lately? FM9 is very finicky as to their location and it's different than in prior versions.
Also make sure that all of your language dictionaries are available - this was an issue during the pre-release that would crash FM9. You should have a \Linguistics folder in your personal Document and Settings \Application Data\Adobe folder. This is where all of the dictionaries reside. If you tried editing the location in the maker.ini (to match the FM8 or earlier locations) you could have created a problem.
Copy link to clipboard
Copied
No, I have not added any personal or site directories, nor manipulated the maker.ini file. There is a Linguistics folder and it contains 4 dictionaries.
Any other pointers are welcome.
Thanks,
Copy link to clipboard
Copied
Sysinternals (now owned by Microsoft) makes some great freebie utilities, and I'm thinking there's one that will let you log what's happening when specific programs start up.
Unfortunately I don't remember which one it is ... maybe Process Explorer... I'd start with looking at the section called "Process Utilities".
Here's a good thread about a PE guide: http://forum.sysinternals.com/forum_posts.asp?TID=10998
http://technet.microsoft.com/en-us/sysinternals/default.aspx
Copy link to clipboard
Copied
One potential reason for this crash might be Dictionary corruption. Please try by renaming :“C:\Documents and Settings\<$username>\Application Data\ Adobe\Linguistics” directory and try launching FrameMaker.
Please see that this will reset any entries in UserDictionary that you might have created in earlier sessions of FrameMaker.
Copy link to clipboard
Copied
Rajat,
Great! Your suggestion soled the problem! After I renamed the Linguistics directory in the folder to Linguistics1, Frame 9 opened without a problem.
Thanks very much for you help,
RK
Copy link to clipboard
Copied
Just for future reference for anyone running into this problem:
Problem
The following internal error occurs during the Localization process of the program initialization (that is, the FrameMaker 9 start-up), and then you can no longer access the program:
"Internal Error 9004, 6919244, 9675646,0. FrameMaker has detected a serious problem and must quit."
Solution
The Dictionary is corrupted. Rename the “C:\Documents and Settings\<$username>\Application Data\ Adobe\Linguistics” directory and launch FrameMaker. (For example, rename the Linguistics directory in this folder to Linguistics1.)
Copy link to clipboard
Copied
For my problem (see my error number above), I had received an email from Adobe Support suggesting I apply the following hot fix:
http://blogs.adobe.com/techcomm/2008/07/hotfix_for_framemaker_1.html
After I applied it, my issue was resolved.
Copy link to clipboard
Copied
I get this "Internal Error: 9004, 6920492, 9676798, 0" whenever - and only when - I quit FrameMaker. Everytime - when closing FM direct after opening as well as when closing FM after hours of otherwise successful work. The "Recent Items" list won't update.
It's FrameMaker 9.0.2 (or 9.0p237) on Windows XP --- interestingly, the (personal) maker.ini says "Version=9.0p196".
Btw, renaming the "Linguistics" folder had no effect...
Copy link to clipboard
Copied
I get this "Internal Error: 9004, 6920492, 9676798, 0" whenever - and only
when - I quit FrameMaker. Everytime - when closing FM direct after opening
as well as when closing FM after hours of otherwise successful work. The
"Recent Items" list won't update.<
Do you have the old cudspan plugins installed? The cudlog.dll program caused
the same problem for me with FM9 (though I don't recall if your error number
is the same as mine was). Removing cudlog.dll made all well again. I haven't
noticed conflicts with any of the other cudspan plugins, though I doubt I've
used them all to actually test.
I believe that Chris Despopoulos has said that he was working on FM9 updates
for his plugins.
Mike Wickham
Copy link to clipboard
Copied
Alas, no, I haven't any plugins installed so far ...
Maybe I should add that my FrameMaker is part of the Technical Communication Suite.
Copy link to clipboard
Copied
I think I found the reason for my problems - a small application called Virtual Dimension (a virtual desktop manager, as you might expect). I've been using this tool for years, even with older versions of FrameMaker, without any problem, but it's quite obvious: whenever Virtual Dimension is running, FrameMaker crashes on Exit; but without Virtual Dimension, Frame Maker terminates normally.
Copy link to clipboard
Copied
I used to be on FM 7.2. I recently installed the Technical Communication Suite 2 after uninstalling my previous versions of Robohelp, Acrobat, FrameMaker etc. Since then, the "FM 9 Error 9004, 6920492, 9676798, 0" error has cropped up at least 4 times when working with FM 9.
Here are some details:
I notice that your original post is a month old. Has anyone found the answer to this problem by now?
Thanks,
Mala
Copy link to clipboard
Copied
Mala,
From my own experience and from other users’ reports I strongly recommend the following steps, if you work with files that come from older FrameMaker versions:
This has helped me and others to avoid crashes.
I guess the reason behind this are the new features of the FrameMaker book, which partly apply to generated documents as well.
HTH,
- Michael
Copy link to clipboard
Copied
I am getting 9004 crashes on a pretty constant basis now, whether I am editing my book files or other individual documents. It always seems to happen when I have more than one document open, and I tab over from one document to the other. The dominant error is 9004,7885529,5204862,5204599, although I have also gotten 9004,6920492,9676798,0.
I deleted my .book file and rebuilt it, deleted the TOC file, gutted and replaced anchored frames, nothing seems to help. I desperately need a solution to this problem as I can barely work on my book any more.
Copy link to clipboard
Copied
YZZYX, and anybody else reporting these errors, would you be so kind as to identify which specific FM version from Help > About, the "pxxx" numbers, your RAM, and your O/S plus service pack, and do so in every post related to this issue -- with this new forum software it's difficult for responders to look back/forth to find out the relevant details each time. (Thank you Mala and previous posters who did so).
Copy link to clipboard
Copied
AxialInfo wrote:
YZZYX, and anybody else reporting these errors, would you be so kind as to identify which specific FM version from Help > About, the "pxxx" numbers, your RAM, and your O/S plus service pack, and do so in every post related to this issue -- with this new forum software it's difficult for responders to look back/forth to find out the relevant details each time. (Thank you Mala and previous posters who did so).
FM Version: 9.0p237
RAM: 2GB
O/S: Windows XP SP3
Copy link to clipboard
Copied
Have you cleaned up the individual component files in the book by saving to MIF and opening those files and saving them over your FM files?
Art
Copy link to clipboard
Copied
Any resolution after you've checked to see that you have the most recent update(s) applied, i.e. 9.0.3 p250 ?
http://www.adobe.com/support/downloads/product.jsp?product=22&platform=Windows
Copy link to clipboard
Copied
Preface: Normally I can edit a single file, no problem. As I said before, if I try to edit 2 or more files, the FM crashes when I tab between them. Curiously, this only seems to happen after I save the files; if I just open the files fresh I can tab between them just fine.
So I took 2 of my book chapters which consistently crash. First, I tried saving them as MIF, then saving them back as .fm files. I was then able to edit both files for 30 minutes or so, saving and tabbing, no problem. A fix perhaps?
Second, I updated FM to 9.03p250. Then opened the same 2 chapters, and the crashes are back! But now I get a different crash number: 9004,7887353,5205950,5205987.
Third, I tried again saving to MIF and saving back to .fm, but the crashes persist.
So I am at the same point, with a constantly crashing FM.
Copy link to clipboard
Copied
YZZYX,
To me it sounds like some problem with the file content or some obscure hardware issue, because I have built some authoring environments with FrameMaker 9 and no such problems.
Regarding hardware: There have been reports on and off about graphic card issues throughout the years. This could be checked if you have access to another computer with different hardware but the same software. Do the problems persist?
More probable from my point of view are content issues. It could be a faulty graphic filter and/or a seldom or wrong image format and/or a fonts issue and/or the use of OLE embedding and/or other things I have not thought about. I know it sounds like a waste of time, but the only way to come to the root of such a problem may be called »divide and conquer«: Reduce the size/content of your files until they can be used OK. For a starter you could start with new empty files based on your well-designed template and add just text to them (create lots of text here: http://www.lipsum.com/). Do they crash? Then go on to add your typical graphic formats and so on...
- Michael
Copy link to clipboard
Copied
"Regarding hardware: There have been reports on and off about graphic card issues throughout the years. This could be checked if you have access to another computer with different hardware but the same software. Do the problems persist?"
I will try this.
"More probable from my point of view are content issues. It could be a faulty graphic filter and/or a seldom or wrong image format and/or a fonts issue and/or the use of OLE embedding and/or other things I have not thought about."
I don't use OLE, I use pretty vanilla fonts (Times New Roman, Arial, and Symbol), and I only use TIFF images and only import-by-reference. I thought it might be a problem with copied anchored frames, so I deleted all my frames and re-created them and re-imported the TIFF images. No dice. Also, I have tried loading only text documents (no graphics) and it still crashes.
"Yzz, when you describe the crashes you mention "tab between them" to jump between documents. How exactly do you tab over, what keys do you use?"
I am using the tabbed-document interface, and use the mouse to click on the tab of the document I want to edit. That's when it crashes. As long as I don't tab to another document, I don't think it ever crashes. Also, it seems I can load 2 documents and tab between them all day long, so long as I don't save them. As soon as I save them (even if I didn't edit anything) it will then crash.
"Second question. when you're editing your documents do you copy paragraphs, frames or graphics -- any copying -- from the master pages or from body pages, between documents, i.e. doing copy / cut / paste or just copy / paste or whatever?"
Sure, I do that all the time. Souldn't a word processor be able to handle this?
"The reason this might be significant is that FM has unique ID numbers for every object (graphic object, text object, etc etc, everything). Because saving to MIF seems to clear out the gremlins for a short time, I'm wondering if the crashes are related to it getting mixed up with these IDs, because saving to MIF and reopening the files forces FM to re-evaluate the unique IDs and resolve them once again. Just saving the FM file doesn't do this re-solving step, which is why saving to MIF has often been known to clear out otherwise unidentified gremlins."
If FM cannot resolve such simple object ID issues without forcing the user to jump through hoops all the time, then it sounds like a fundamental software design flaw that needs to be fixed.
- Carl
Copy link to clipboard
Copied
Without minimizing your problem at all... the problem boils down to finding what, in your environment, is triggering the crash. It's obviously not normal behavior and there are thousands of installs in the field that aren't experiencing this....
A couple more questions:
Cheers,
Art
Copy link to clipboard
Copied
Yzz, you mention crashes seeming to only happen on save.
are you saving locally, to your own system or to a networked location?
Do you have any backup or source safe type programs running?
do you have the network file locking turned on or off in preferences? Automatic backup on Save?
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more