Framemaker crashes on start up.

[Guest]

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 ===

[Jeff_Coatsworth]

First off, there's no sense in posting the contents of the error file here - that stuff only means something to Adobe techs - this is a user to user forum. Send it to Adobe as the message asks you to.

The fact that it got stuck at Localization probably indicates that you've got a corrupted Linguistics folder. There are several threads describing what to do. Also - your version hasn't been patched - make sure you load the patches one at a time (Adobe patches are sequential, not cumulative) so that you're up to FM9 p255.

[Guest]

I have patched it up to day Since i posted this, Still the same error. I have tryed a repair in the current install still the same error.

[Jeff_Coatsworth]

Did you search the forums for the Linguistics fix? - I seem to remember it involves renaming the folder - FM then recreates it when it starts up.

[Guest]

Unfortunatly this did not fix our problem i think my next mvoe is to install it on another PC and see how that gets on.

[Jeff_Coatsworth]

You could try uninstalling/reinstalling completely - contact Adobe Support - installation issues are free calls.

[mlw9]

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.

[AxialInfo]

mlw9, a great solution to the "changed printer" problem is to use the freebie "SetPrint" utility by http://www.sundorne.com

SetPrint lets you specify the printer that FM (and only FM) will see and use as the default printer when FM opens, regardless of whether you have any other printer (e.g. your barcode printer)  set as your Windows default printer.  Most users set their Acrobat printer as the system default in SetPrint.