When I go from "show certain conditions" to "show all" in some, but not all, files in a book, FM 10 crashes.
I've tried saving as MIF, then reopening, but it still happens eventually.
Sometimes it happens with the first file I open, sometimes not until after several files have been opened and
had their conditions changed, so it doesn't seem like a memory leak.
Saving as MIF then reopening is a MIF wash.
You've covered anything that a MIF wash would detect or fix.
Can you tell us more about the crash?
Does Frame detect a problem, generate recovery files, and shut down? What console message?
Or does it start that process, go off the rails, and leave lock files and incomplete recover files.
Or does the crash of the crash itself crash, and everything just winks out (which I often see in FM7.1, although not Condition related)?
Just happened again, and I was just adding some conditions to a previously stable file.
First I got this message:
Internal Error 10024, 7687848, 7688138, 10076935. FrameMaker has detected a serious problem and must quit.
gives the log file name and tells me to send it to firstname.lastname@example.org
Then I got this message:
Adobe FrameMaker 10 has stopped working
Windows can check online for a solution to the problem
(a couple of choices)
Then FM10 closed -- no recover files this time, although in the past, FM has generated .recover files.
Files have not stayed in the locked condition -- usually just .recover files are generated and FM closes.
Time to re-install FM 10 I think.
BTW, I'm running Windows 7.
This happens to us as well, and has been persistent since Frame 9. One thing to try (if you're desperate, and we sure have been), is to break the problem file into smaller pieces to isolate the problem. For example, save the first half of the chapter as one file, and the second half as another -- repeat until you isolate or resolve. It seems to have something to do with conditionalized cross references, but we've never been able to fully resolve it.
I believe I have resolved the issue for myself -- I removed FM8 from my
system, removed FM 10, and then re-installed only FM 10. Since doing that,
I have not had the crashes. I had been running both FM8 and FM10 -- which
I think may have been the root cause.
Another solution that works for us is to select the entire main text flow of the file, copy it to a blank frame file, and then save the temporary file. In the temporary file, you should be able to toggle your conditions on and off without an issue. If that works, delete the main text flow in the original file, save it in that state, and then copy the contents of the temporary file back in. Everything should be happy at this point.
I've had this problem since release, and it is frustrating to no end. I've lost count of the number of hours of productivity lost due to this bug.
Can we have an Adobe rep inform us what the status of this bug is in terms of fixes? Can we expect a patch in the near future?
Use this link - https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
the more people that report an issue, the more likely it is to get some attention
I have been plagued by the same internal error in Frame 10.
However, I did not receive an error when:
I opened the book, opened the chapter in my book, went to Special > Conditional Text and then either selected or deselected the "Show Condition Indicator" feature.
In my case, the error seems to be limited to trying to show/hide condition indicators from within the Show/Hide Conditional Text window.
I am getting this issue too. I click Show/Hide Conditional Text for multiple files in any book and Internal Error 10024, 9332515, 9332572, 7278063 displays just before FM crashes. I do not see a solution in the forum. I have tried MIF wash, rebuilding books, etc. This was not happening in the same books about 10 days ago; only things that have changed on the local machine are Adobe Flash, VPN client, and Mozilla Firefox updates.
Running the latest FM10 build on Win7 64-bit.
I am not using Track Changes but disabled it anyway across the book. FM still crashes. I changed from Adobe PDF as the printer in Printer Setup to the default network printer here. FM still crashes.
Did you get a better suggestion or solution from Adobe support?
Not saying you need to reveal it here. After all, "you" paid for the call.
I'm trying to figure out if this issue is worth my firm signing up for support.
All I know is I didn't need it on FM8.
I don’t have the issue (at least I have never run into it), I was only suggesting to @TekCon to call Support. The engineers are generally interested in what causes hard crashes to occur.
As far as support contracts go, the new one that Adobe offers is quite good – you get Gold level support and upgrades are now included. That alone made it worthwhile for my company to buy it.
I'm having the same problem. Adobe support said to do the MIF wash, which seemed to work, but the problem returned. I'm wondering if it's caused by combining conditions. I have a release condition (3 or 4) and an audience condition (external or internal).
Plenty of folk have reported the issue. No sign of a solution.
BTW: TekCom = Tekscribe
The first name is from personal FM license (old profile created from home base), the second is from employer/company FM license (created recently via the office). Sorry for the confusion and redundancy.
I posted previously under "[FrameMaker General Discussion] Internal Error 10024, 9332515, 9332572, 7278063". Log file has been sent several times to email@example.com. Last week, I sent many zips in separate e-mails of the entire project to Adobe Engineering Team for analysis (the project is too big to upload to Acrobat.com). No response yet. I suggested they need to test using a similar conditions as what I describe below.
BTW, I tried the above mentioned MIF wash (every single file of many book files), cut & paste to blank file, rebuild book from scratch, uninstall/reinstall FM10 ... all to no avail. I did trial and error (a shot in the dark) too: reset dictionary library, and choose other default printers (either Adobe PDF virtual printer or another physical printer on the network). Nada. No dice. It still crashes. I am not using Track Changes, so that is not likely a possible culprit.
I am running the latest FM10 patch on a Win7 64-bit HP Mobile Workstation. I have seen misc. posts online about FM crashing with laptops (Lenovo was mentioned), as well as unsubstantiated rumblings about laptop internal services or Adobe Flash or Adobe Acrobat X interferring with FM. Yes, I have many, many conditions present in book files; yes, yes, I have checked all source and target x-refs are in agreement for conditions. The only thing that works is to turn off All Cross-References in the Update Book dialog box. The book will update with that option cleared but crashes with it checked. It is definitely tied to cross-references and conditional content.
It is as if FM runs out of processing bandwidth or memory, both of which are impossible given the laptop has megatons of RAM and hard disk. IT guy here speculated maybe Symantec Endpoint (security pak) is getting in the way, but that has not been substantiated; the process of removing/reinstalling this corporately mandatory security software is onerous and we are avoiding expermenting with it for now. It is disappointing Adobe cannot exterminate whatever gremlins plague FM. As a result, I cannot trust that FM11 is worth the expense (i.e. How can I convince the powers-that-be to approve the purchase when FM10 crashes like a plane without wings?).
I will post any response I get from Adobe to this Discussion and the other one previously mentioned.
By the way @scaton, Internal Error 10024 means the app is FrameMaker 10 (the remaining digits partially referring to the patch/build number). Nothing more. Other error codes are a mystery. Adobe has not seen fit to publish the obscure meanings of FM error codes. I read this somewhere online (maybe elsewhere in this forum), but forget who was the author.
I do not have another similar machine readily available for FM11 test. No time either. I need to get work done (while carefully avoiding provoking another FM10 crash), aside from posting to this Forum and chasing Adobe Engineering.
The particular book/project that crashes was run (i.e. Update Book) successfully on a WinVista 32-bit machine running FM10+update. I may have mentioned this in the other discussion. So, my favorite theory presently is ... the crashing is tied to hardware (i.e. laptops), software (installed on the laptop), or O/S (i.e. FM10 does not function well in 32-bit mode on a 64-bit machine).
So, cross-references and/or multiple conditionals may be the trigger, but hardware, software, and/or O/S may be the fuel feeding the crash-fire.
I may have mentioned but will repeat: the chronic crashing is happening on two different but indentical HP laptops.
The HP laptops do not have any other FM version installed. Only FM10. The home machine (running WinVista 32-bit) mentioned above does have FM8 installed as well yet I was able to Update Book successfully for the same heavily conditioned project. So, the prescence of another FM is not relevant in my case. It may be an issue in other circumstances; however, optimistically I assume Adobe would suggest users uninstall old versions or the new version would do that automatically upon installation if conflicts were anticipated by their engineers/testers.
You may have achieved something accidently either by virtue of the FM8 removal or the FM10 uninstall/re-install. From experience, I think there are a variety of reasons FM misbehaves and gives up the ghost. IMO, it would be better for users to have some idea what is giving FM grief, instead of useless, cryptic error message coughed up by the software. Adobe: Are you listening?
I am sticking with the theory outlined above for chronic crashes here. For sure, conditional content has something to do with it but only in certain circumstances (hardware, software, services, conflicts, memory allocation, alignment of the planets, etc.).
In the response I got from an Adobe engineer, they allegedly did test FM10 versus Win7 and 64-bit mode. According to Adobe, Win7 64-bit is a supported platform. However, I am not convinced they tested on a variety of machines (e.g. Lenovo or HP laptops).
All the same, it must be a relief that your situation is resolved. I wish mine was...
What exact version of Windows is that?
I'm guessing Windows 7 Professional 64.
If so, you could download and install "XP Mode",
which provides an XP 32 virtual machine that
might be worth a try.
You may or may not have to re-install FM and AcroX
in the VM.
Win7 Enterprise 64-bit (Service Pack 1). I'll mention your suggestion to IT. I will not experiment further without their consent. In the meantime, I still await a response from an Adobe engineering team.
Windows Enterprise can run XP Mode (as can Professional & Ultimate).
Windows Premium, Basic and Starter refuse to run XP Mode.
FM itself won't run on Windows Server, unless it's the FrameMaker Publishing Server edition.
I get to join this thread now since FM10 has crashed on me for changing conditions...yay (?)
I have a book file with a Front file and Body file for a grand total of 10 pages (with all conditions showing - not a large doc by any means). I only have 7 conditions (which is not a lot considering at one company I had over 50 in one book and FM8 handled that just fine) and I have triple checked to make sure all the conditions are the same for each of the files in the book, which I thought could have been the problem - but no.
I am running Windows 7 on a 32-bit HP desktop, not laptop. This machine did not have a legacy version of FrameMaker installed on it - only FM10 when I received the PC (I am not working with TCS). I do have Photoshop, InDesign, and Illustrator installed along with Distiller X and Acrobat X.
I am amazed that with how many of us are having issues changing conditions that there is no patch! Everyone seems to have different system configurations and programs, but the problem is common to all. This makes me think that the issue lies somewhere deep within the code and has nothing to do with our system configurations or software that we are running...just my two cents.