3 different FrameMaker Crash types & Logs - Help!

[Greg_Eisen]

We have 6 or 7 users all experiencing "random" crashing in FrameMaker 10. The machines are solid with enough ram, hd space and cpu power. Also FrameMaker has been patched with the newest patch out. I have already tried a complete fresh install and re-patch to see if that would fix the issue. I am leaning towards an error with whatever they are creating but would like verification of this. I am not very FM knowlegable.

Users claim that sometimes FM will work fine for days but sometimes it crashes over and over in a single day. There are 3 different  Internal Error's they are experiencing. Below are the log files.

Thanks!

------------------------------------------------LOG Type 1------------------------------------------------

=== Header Begin ===

Internal Error: 10014, 7686536, 7686826, 10069773

FrameMaker 10.0.1 for Intel

Build: 10.0.1.402

Window System: MSWindows

Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 3)

Generated on: Thursday, October 27, 2011 7:42:58 AM

To file: C:\Documents and Settings\mjs\Application Data\Adobe\FrameMaker\10\FrameLog_11.10.27_07.42.58_2.txt

=== Header End ===

------------------------------------------------LOG Type 2------------------------------------------------

=== Header Begin ===

Internal Error: 10014, 5989163, 8095170, 5911460

FrameMaker 10.0.1 for Intel

Build: 10.0.1.402

Window System: MSWindows

Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 3)

Generated on: Wednesday, October 26, 2011 3:17:55 PM

To file: C:\Documents and Settings\mjs\Application Data\Adobe\FrameMaker\10\FrameLog_11.10.26_15.17.55.txt

=== Header End ===

------------------------------------------------LOG TYPE 3------------------------------------------------

=== Header Begin ===

Internal Error: 10014, 7253204, 7257867, 6478147

FrameMaker 10.0.1 for Intel

Build: 10.0.1.402

Window System: MSWindows

Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 3)

Generated on: Thursday, October 27, 2011 7:42:45 AM

To file: C:\Documents and Settings\mjs\Application Data\Adobe\FrameMaker\10\FrameLog_11.10.27_07.42.45.txt

=== Header End ===

[Edited by host]

[Michael_Müller-Hillebrand]

Greg,

I have not heard that those log files are of any use at all (apart from telling the version number and platform).

Have you installed from DVD or from hard disk? The latter is the preferred method, as there are reports of errors in the installation from optical media. But this does not usually lead to random crashes, but to very often crashes.

I fear the users have to try to find some kind of pattern.

You are using Windows XP?

- Michael

[Greg_Eisen]

We have installed from hard disk. Windows XP SP3 is the OS used on all machines.

By the way....why have error logs if they don't give us any useful information!?

[Jeff_Coatsworth]

Send the log files to Adobe Tech - they're the only ones who can make sense of them. We're all just users here ;>)

[Greg_Eisen]

ahh ok, did not know this was a user only forum.

Thanks!

[Bob_Niland]

ahh ok, did not know this was a user only forum.

We users might be able to help if we knew what your users were doing prior to the crash, and whether there's anything the least but peculiar about the structure of your documents (like the right run-in frames that give rise to a certain Error 7103 in my work).

Any chance the documents came in from older Frame versions?

Have you tried a MIF wash?

Based on historical rumors, your error 10014 decodes as:

10 Major release 10

0 Minor release 0

1 Undocumented error #1, meaning likely of little use to end usersy

4 Windows version of Frame (3 would be Unix, dunno what Mac or Linux would have been)

Or it may decode as "Wing Attack Plan R". It's hard to tell.

_______

You might want to edit the basenote to just the content above "Header End"

[Greg_Eisen]

FrameMaker 9 was used previously, and is still installed on all of the users workstations. However, I do not know if the files were created in 9. I will check on this.

[Greg_Eisen]

Are there instructions on how to MIF wash?

[Arnis Gubins]

In FM10, when you open the Book file, you should see a Book Utilities menu option. There is a MIF Wash option there.

Alternatives:

1. save the file in MIF format, then open the MIF and re-save as a binary FM file.

2. Get the mif2go utility from Omni Systems. The MIF wash function is fully useable in the demo version. See: http://www.omsys.com/dcl/riskless.htm

[Bob_Niland]

Are there instructions on how to MIF wash?

There might be something in FM10, but it's historically been just oral tradition in the Frame subculture.

1. Open the book and all component files.
2. Save each in MIF format to a file with a .mif extension.
3. Close all the files.
4. Make backups of the original .book and .fm files.
5. Open all the MIFs.
   Watch the console for any interesting errors (may be none).
6. Save the files in FM10 format as .book or .fm.

Evidently the FM binary format can contain data structures that aren't valid as MIF.