FrameMaker crash

Why does FrameMaker 12 crash sometimes when saving a file to PDF? Had this trouble with FM 11, too.

Does it crash when you Print to the Adobe printer instance instead of using
SaveAs PDF?
Is the Adobe printer set as your system default?
And finally, what is your environment? OS / RAM / file location / any other
bits and pieces?
Art Campbell
          [email protected]
"... In my opinion, there's nothing in this world beats a '52 Vincent and
a redheaded girl." -- Richard Thompson
                                                      No disclaimers apply.
                                                               DoD 358
I support www.TheGrotonLine.com, hyperlocal news for Groton MA.

Similar Messages

Framemaker Crashes when adding to anchored frame

I have had Framemaker crash on two files after adding an anchored frame and then putting stuff in it. One was a picture generated by another program, the second was a drawing created using the drawing toosl. This is FM 8.0.2, with the latest patch running on Vista.

David,
Can you send the files and steps to reproduce this issue to [email protected]?
Thanks,
Megha

FrameMaker crashes when selecting print book file

I have recenctly update to TCS4. FrameMaker crashes when I select Print Book but will produce a PDF is I select Save As PDF.
Anyone else experiencing this and have a resolution?

While I agree that this should not occur, you've said you can produce a PDF...
Is there a reason you don't want to print from the PDF?
Many long-time Framers are so used to doing this that we don't even use the Print dialog anymore...
That said, if you want to track down the culprit, try the excellent suggestions above:
set printer to Adobe PDF
MIF wash
Create a new book, and open all files
and add 2 more to the list:
Ensure that all the alerts are checked in Edit > Preferences > Global > Alerts
Update your book and address any missing resource messages
-Matt
@mattrsullivan

FrameMaker crashes on 68 char filename

Hi,
I'm using FrameMaker 7.1 on Windows XP. I'm running a FrameScript that basically just opens the MIF file and converts it to Frame binary (.fm) format.
If the filename of the MIF file (including .mif) is 68 chars, FrameMaker crashes with an internal error. When I change the filename to 67 chars, it works fine.
Also, I'm able to open the 68 character MIF filename file in FrameMaker directly and save it as .fm with no problem.
Is there some filename length limitation I'm not aware of? Any suggestions on how to address this w/o having the shorten filenames?
Thanks!

I created such a MIF file, opened it with FrameMaker 7.1, opened another file and imported Page Layouts without a problem. Was this your process?
Where does the MIF file come from?
Does it happen with any MIF file with this file name or just with that certain file?
Does the result depend on the content of the file?
You already started with drilling down to the core of the problem. Please continue isolating it.
And if you think a script could be the problem, please show the relevant lines of the code.
- Michael
Am 26.02.2010 um 16:06 schrieb sjje4:
Thanks for responding!
It crashes on 69 chars as well.
I did a couple tests and shortened a couple of the folder names and it still crashes. I also renamed the file so I could tell how many chars were in the filename (see below).
D:\Profiles\qa2774\Desktop\BookBuilds\Test\SMM\DB\mifext - this is the path to the MIF file. The .fm file gets placed in a different folder (same but fmext/ instead of mifext/).
Now, I should also have added that the FrameScript imports Color Defns, Document Properties, and Page Layout properties from a template file before saving as .fm. And after running these tests, I thought I should try that manually in FrameMaker (while composing this post), and sure enough it crashes on the Import!!! So I imported each property individually, and it crashes on importing the Page Layout properties!
1234567890123456789012345678901234567890123456789012345678901234.mif - this 68 char filename works when doing from FrameScript but crashes when I do it manually in FrameMaker - very strange
12345678901234567890123456789012345678901234567890123456789012345.mif - this 69 char filename crashes whether doing it from FrameScript or manually.
I changed the script to not import the Page Layout properties and it doesn't crash. But I need those Page Layout properties .
Thoughts?
Thanks!

FrameMaker crashes when saving a file as XML

Hello -
I am encountering a problem saving a .fm file as a .xml file. I have saved many .fm files as .xml files in the past with no issues. However, lately FM crashes with a "serious error" on certain files when I try the same save process. My initial thought was that the file was somehow corrupted, but this morning I ran into this scenario: I have 3 FM licenses in my office, I was trying to save a .fm file as .xml and FM kept crashing. So I had another co-worker try to save the exact same file as a .xml file and it WORKED!?!?!?!
We all were using FM 11, but I have since installed FM 12 thinking that version 12 wouldnt have the same problem, but the same issue is happening with both versions of FM. I read that FM has issues when working across a network so I have tried it both ways, across the network and locally and the same issue occurs.
Again, this problem occurs occasionally on various files - not every file, but as previously mentioned I was able to successfully save a file on a different machine that I could not save on my machine. I have the most recent log file that was generated after a crash:
[*** LOG FILE REMOVED BY MODERATOR***]
Thanks in advance for any help in this matter.
Gavin

An update -
So FM now appears to crash "sometimes" when saving as an xml file AND when saving the file in general. I have 3 machine with FramMaker installed, first with version 11 now with version 12. These 3 machines are all identical as far as SW running on them, etc... I have been unable to detect a pattern as to when FM will crash thus far. Sometimes it will crash when I try to save the file as an .xml file and sometimes it will save just fine. I have resorted to marking up the document a little at a time, saving the file, then trying to save as an XML file. It will work sometimes and other times it will crash. Sometimes it crashes when trying to save the .fm file other times it works; sometimes it will crash when I try to save the .fm file as a .xml file, other times it will work. About the only thing in common that I have found thus far is the fact that it happens with the same file over and over again; meaning that if I have a pool of 12 files that I need to load into FM and markup, 11 of the 12 files may work just fine and the 12 file will not - it will crash FM at some point in the markup/saving process every time. One might guess that the original file is somehow corrupt and that may be, but at this point I am not sure how I prove that is the case as FM seems to load it in just fine and I can save it right off the bat just fine. Does anyone know how I can prove that the structured file i receive initially is corrupt when it loads into FM fine? If we were causing some issue with the import of our modified EDD then why dont we have the same issue with the other 11 files in the batch as they all are using the same EDD?
I have sent my most recent log files to adobe tech support this morning. I have tried saving files on shared drives as well as on local drives. I have tried the same process on the other workstations with the same results.
Does anyone have ideas on how I can isolate a problem with the source file (structured doc) or on why FM is crashing when I perform these actions?
Thanks,
Gavin (Ryan)

Framemaker crashes on start up.

I have just recently downloaded and installed Frammaker9.
So we can test it i dont really want to splash out £100's
So any help here is much apprechiated.
So after i installed it i got an error.
And in that log file was this.
=== Header Begin ===
Internal Error: 9004, 6919244, 9675646, 0
FrameMaker 9.0.0 for Intel
Build: 9.0p196
Window System: MSWindows
Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 3)
Generated on: 09 December 2010 10:57:50
To file: C:\Documents and Settings\USERNAME\Application Data\Adobe\FrameMaker\9\FrameLog_10.12.09_10.57.50.txt
=== Header End ===

I recently had the same problem although I had a working FM9 installation already. Suddenly it failed during start-up as indicated. It was caused by my default printer being incompatible with FrameMaker. I had changed the default printer to a barcode printer for an unrelated reason. FM9 would fail in the general vicinity of "Localization" and show the logfile message. Changing back to my standard printer eliminated the problem immediately.
Hope that helps. I hadn't worked through the full Adobe list of system problems before this possibility occurred to me. Maybe it's listed as something to check; maybe not. It does make a difference.

Issue with ScrollBox - Crashes Framemaker 10

Hi all,
When I invoke a scrollbox in ExtendScript, FrameMaker crashes.
For e.g.,
var myArray=new Array("Item 1","Item 2","Item 3");
var choice = ScrollBox ("Choose an item", myArray, 0);
Alert ("You chose " + myArray[choice], Constants.FF_ALERT_OK_DEFAULT);
does not work. Is it a bug or I am doing something wrong here?
Regards,
Bruno

Bruno,
You should replace the first line in your script with this :
ar myArray=new Strings("Item 1","Item 2","Item 3"); //using Strings datatype
Vikash
FM Engineering Team

Framemaker 7.0 consistently crashes when saving files as .rtf (and other related issues)

Thank you first of all for any help from anyone. Secondly, I apologize for any of my FrameMaker naivety, I am just a beginner with it really.
I am having a problem when saving out FrameMaker files to rtf format (for eventual conversion to word -- some people just want parts of book in word so they can mess around with it). Frequently, framemaker crashes and gives me a message such as this below. What can I do to get our documents into word format?
secondly, when i get them into word format, sometimes I have this problem when paragraph marks are turned on in word -- people that have recieved the word files I send them have complained about this and unfortunately they are people I cannot tell to just turn off the paragraph marks. Why is that repeated text inserted into the line? It should just say "Removing Constraints" (with no parenthesis marks). Some of our chapters are very long and manually removing this is not applicable.
thanks for any help!

About the {XE xxx} fields in your output file, that's the way FM converts index markers and their content when outputting RTF; FM automatically turns on the display of these fields. I believe it's the same with cross-references and all other kinds of marker output.
With MIF2Go you can specify what to do with each different type of marker, so you could choose to delete them completely if you wanted, or else to retain the markers but convert them to the correct index references in RTF. Here's the section in the MIF2Go manual about the markers:
http://www.omsys.com/dcl/usergd/rtfref_0120_5141_generating_an_index_in_word.htm#Xz105x557 827
http://www.omsys.com/dcl/usergd/rtfref_0119_514_modifying_word_output_after_conversion.htm
I'm not sure whether MIF2Go has a way to control the actual display of these fields in the RTF or not, or whether that would need to be done by a vbscript after the RTF has been generated.
Sheila

Problem with FrameMaker 9 on Windows 7

A member of my unit is running FrameMaker 9 on Windows 7 with a 64bit machine and has come across a strange problem.
Whenever he has a file open for too long his FramMaker will crash once he tries to work with the file again. This usually takes a few hours before this problem arises. In trying to figure out what was going on we took a look at Windows Task Manager. We noticed that once we opened a FrameMaker file the GDI Objects for FrameMaker continued to grow steadily even when we weren’t touching the file or doing any work in FrameMaker. The value under FrameMaker GDI Objects continued to grow until it reached some point around 10 000 then FrameMaker would either crash (if the GDI Objects passed 10 000) or it would crash once one tried to open another FrameMaker file (because that would make the GDI Objects increase to over 10 000).
Has anyone else encountered this problem? Does anyone know of a way to fix this problem?

I actually have a similar problem with my machine. I am running FrameMaker 9 with Windows XP on a 32bit machine.
The problem is slightly different because on my machine the GDI Objects doesn't continue to increase over time it increases with the number of files I open and close. Every time I open a file the number of FrameMaker GDI Objects increase and when I close the file the number of GDI Objects decreases a little but not down to the original value, so when I open and close a lots of FrameMaker files the number continues to increase until it reaches 10 000 then my FrameMaker crashes.

Save as PDF in FM 9.0.3 causes crash

In FM 9.0.3 (aka 9.0p250 ... why are there 2 names for the same thing?) when I save a book or file with "Save as PDF" FrameMaker crashes.
It leaves Acrobat Distiller (9.3) open with message
Adobe PDF Settings file read error in PDFX4 2008.joboptions:
/CheckCompliance out of range
The good news is that if I go through the Print dialog and select Adobe PDF as the printer it prints fine.

Can anyone tell me how to *effectively* unsubscribe to every post in these forums being emailed to me? I've tried every obvious, and not-obvious-but-recommended-by-someone thing I can think of.
Thanks.

(FM8p277) Crashes when saving first doc in book after changing conditional text display

That was a mouthful :-)
Okay, this happens with any of the books that I work on --- it never happened with Frame 7.
I have a book containing several documents.
The documents contain several conditional text segments.
Start new Framemaker session, open book, open all documents.
Change conditional text display (from Show All to Show Selected, or vice-versa).
From the book, choose Save All (or from the *first* document, choose Save). The following text appears in a 'FrameMaker dialog': "File <filename of first document>.fm has changed on the disk since you last opened or saved it. Someone else has probably modified the file. Do you want to save it anyway?
Click OK. All of the files save properly. (If I had clicked Cancel, the first file would be skipped and all other files would save.)
Change conditional text display again (note: this could even be for a different book at this point, I believe, but will have to verify).
(Repeat step 3): The same text appears again in the dialog.
Click OK. FrameMaker crashes while trying to save the first file. (If I had clicked Cancel, the first file would be skipped and all other files would save. However, if I attempt to save the first file afterward, FrameMaker still crashes.)
Anybody have any insight into this? Am I the only one this happens to? Argh :-)
Thanks.

Sorry, the only answers I got were on the forum and nothing worked
That being said, at least now I know I'm not crazy! (Sorry it had to
happen to you, though.)
As it stands, I've been training myself to make sure that after the
first time I toggle the settings, I do the save, and then make sure to
save all, quit, and restart FrameMaker before I attempt another toggle.
On the odd occasion that I don't do that and get the warning message, I
select Cancel (which lets the rest of the files save), quit, restart,
and then make sure I update the first document appropriately.
All the while cursing and swearing, of course
As an aside... if you find a solution, please let me know about it if
you remember.
Thanks.
John

FM9 crashing when trying to open book file

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 [email protected] (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

Judy,
The 9004 code just means that FM9 crashed. The subsequent numbers provide some clue to engineering as to where the fault was, but can't be deciphered by anyone else. If these seem to be all different values, then this may be an installation or machine issue.
The p255 version means that you have all of the patches applied.
The fmerror mailing address is just a one way street, where Adobe keeps track of issues and looks at trends. They will never reply via this channel. Also, since they've been at FM11 for almost a year now, odds are that single FM9 issues won't be flagged as high priority items by engineering - that's kind of why us users have to help each other out.
Since the individual files open properly and your system doesn't crash, then the problem sounds like it's either in the .book files themselves or you may have a system resource issue (you mention flakiness in Word too).
If you re-create a clean book file from scratch, does it immediately crash or when you open it again? You could try saving the book file as a MIF at that point and trry working from the MIF. Also does there seem to be any pattern as to when (i.e. after how many open/close cycles) a book file will start to crash after you have recreated it or used an old, archived one?
Do you have another machine (coworkers?) with FM that you could test the files on? If they don't crash there, then odds are it's something specific with your machine.
With regards to resources, do you have significant free space available in your system TEMP area? Have you defragmented your drives? How much memory does your system have? Do these crashes occur at any time or after you've been working on the machine (from a cold start) for a while?

Why is FM crashing during import of PDF comments?

I'm running FM 9.0p255 on Windows 7 and using Acrobat Pro 9.4.5 (running in Windows XP on another computer) to enable commenting in Adobe Reader. After saving the file, in Windows 7 I open Adobe Reader 9.2.0 and make comments, then save the file. In FM 9 I open my 2-page file and import pdf comments. FM crashes. I've been trying everything to eliminate the problem, all the way down to creating an FM file with just the words "This is a test" in it. I went through the Acrobat comment process and added one word. When I tried importing pdf comments, I got this error:
"The modification date of the source file is newer than creation date of the tagged PDF. PDF comments may not be imported correctly. Click Yes to continue."
When I click Yes, FrameMaker crashes.
What is strange is that my FM file has 8/5/2011 4:39 PM as the Date modified.
My commented PDF has 8/5/2011 4:43 PM as the Date modified.
I've tried rebooting my computer and that didn't help. Does anyone know anything else I can try?

Linda, I'm wondering if there's some "conflict" being triggered because you're using both Win 7 and WinXP --
Specifically, I wonder if the two systems have off-kilter time stamps, and that's why FM is giving the "newer creation date" problem.
I don't quite understand what role the XP system has in your test, though -- can you not just use FM == and == make the PDF on the same Win7 box, make the comment on that box, then import the comments?
Understandably you will probably eventually need to be able to import comments from all sorts of other systems, but for troubleshooting could you try making the full create-comment-import cycle on the Win7 box only?
If that does work, then you might see of you can set the system time on the XP box to be somewhat slower than the Win7 box, and re-try with the XP box in the mix.
Edit: changing the system time clock is suggested only as a testing procedure, to see if we can isolate the exact cause, I'm not suggesting that in order to work reliably all your reviewers would need to synchronize their systems :-)
Sheila

Selecting conditional text in book crashes FM 9

You never know when it will occur or on which files .... I am in a book file and select several files, select View > Show/Hide Conditional Text, and change my condition settings, then click Apply.
Framemaker crashes. Sometimes three, four times in a row.
Yes I've made new files, etc., etc., and some others in our group have the same problems with conditional text in some books. This is not consistent behavior so that's why we scratch our heads.
I have 4GB of memory and an empty hard drive, so that's not the issue. We work off a network but the same thing can happen if I save a book locally.
What on Earth could be happening?

Some files are new. Some files were ported from previous versions. Because the crashes are always different, it isn't always the same files or books where crashes occur. One never knows what will trigger the crash or when, as I mentioned. I've rebuilt files and had them crash, but someone else can use them (and change the same setting) without problems.
There's no discernible pattern.
Crashes for team members occur consistently at the book level. I seem to be the only person who can set conditions at the book level (though not consistently, as you can see). Crashes can occur for me at the book level or when I have a file open. Typically a file that crashes at book level also crashes with the file open.
I am trying to change one condition for these companion volumes (a set of three books that share some files). I successfully changed the condition a couple of hours ago.
Our network isn't backed up until very early in the morning and it's afternoon here -- that's not the issue. Nobody else is working on this project so that's not the issue.
Our templates have all of our conditions already defined so theoretically there shouldn't be conflicts. As I recall, a conflict triggers a notification when you update a book, and I successfully updated the companion book and printed to PDF a couple of hours ago.
Content doesn't seem to matter. The files in question consist of headings and tables. There are no graphics or linked files. The most sophisticated thing in them is cross-references (some conditional).
I just successfully changed the condition on all of the files in that chapter except one. The file that crashes Frame is very simple (no graphics or linked files, just cross-references) and it is one of the files that successfully switched conditions just a few hours ago.

FrameMaker 5.5, imported graphics couldn´t be saved after editing

Hey togehther,
i have a problem with FrameMaker 5.5 on a Windows XP Workstation with Spervice Pack 2:
In case of editing an imported graphic in a FrameMaker documnet (e.g. an AutoCAD drawing) and saving the document after editing the drawing, FrameMaker crashes/freezes.
After reopening the document the drawing/graphic is not changed.
What cause can be present here?

Hi Okeller,
You may have placed an OLE link into the FM document by just copying and then pasting into FM. Hence Your double click can open the original application to edit the graphic. Avoid OLE like hell!
But you hear MMH: FM 5.5 is now 12 years old and XP is 5 years younger ...
Try the following:
- Double click on your graphic to open the app in which you edit it
- In this application create a graphic from the file, something that FM can handle: eps with preview or as the last a pixel image (tiff) and save this to the project directory
- in FM remove the graphic from the anchored frame and import the new graphic file by reference (not copy) and adapt size etc.
HTH
Klaus Daube

FrameMaker crash

Similar Messages

Maybe you are looking for