Skip to main content
March 2, 2016
Question

FrameMaker 10 crashes when opening files with Internal Error 10024, 9323487, 9022944, 9008636 (leaves files unrecoverable)

  • March 2, 2016
  • 2 replies
  • 610 views

We're running unstructured FM 10 on a VM, Windows 2008. This morning, while creating a PDF of a 700+ page book, we got an out-of-memory error and after that, we are unable to open any file in the book without crashing FM. Since we can't open the files, a MIF wash isn't possible. Our VM had 4096 MB of memory (most of which was consumed) when this happened. We increased it to 7168 MB, but it seems like some serious damage was done to the files. Of course, we have an upcoming product release (FrameMaker seems to be keenly aware of deadlines). Any ideas on how to recover these files? We can resort to a backup if all else fails.

    This topic has been closed for replies.

    2 replies

    Bob_Niland
    Community Expert
    Community Expert
    March 2, 2016

    re: running unstructured FM 10 on a VM, Windows 2008.

    So is Windows Server 2008 the host or the client? If not the client, what is?

    How much total RAM, and how much assigned to the VM?

    Has this configuration been functional and stable for other documents?

    Jeff_Coatsworth
    Community Expert
    Community Expert
    March 2, 2016

    Try a “heroic” open - Esc, o, H (meaning Escape, lower-case O, and capital H pressed in sequence rather than in combination)??

    March 2, 2016

    Thanks for the speedy reply, but that didn't work (although I'll keep that in my bag of tricks for future attempts). Any other ideas?

    Arnis Gubins
    Inspiring
    March 2, 2016

    Minor omitted detail:

    You need to have a blank FM document open first before trying an heroic open. See if it works then.