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

[Guest]

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.

[Jeff_Coatsworth]

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

[Guest]

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]

Minor omitted detail:

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

[Guest]

Yes, we googled that and discovered that step was required. But, that didn't work. It seems like all the files in the book are unrecoverable. We suspect that in addition to the out-of-memory error, there may have been something wrong with the file from which we import variables to re-brand documents. I've restored the book files and the variables file from a recent backup. I think I'll do a MIF wash on the variables file before attempting to re-brand again. Thank you so much for your help. If anything else comes to mind, let me know.

[Arnis Gubins]

When creating the PDF, make certain that all files in the book are open first. Also, do not use the CMYK option with FM10 and make certain that you are patched to the latest release (10.0.2).

The intermediate postscript file size created during the PDF process can be quite large, especially if there are a lot of graphics in your book, so allocate as many resources as you can afford to your VM and have plenty of free disk space available.

[Guest]

We always open all files in the book. We'll give the CMYK option a try because this particular book has a lot of screen shots in it.

We have two rather large books (700+ pages) where we have encountered this problem. We've tried generating the books directly on the host (Windows 8) and also as a client (Windows 7) and the same error occurs no matter where it is running. I'm not certain how much total RAM is on the machine. vSphere shows 7168 MB for the host and 7168 MB for the guest, with 6.84 GB Private (I'm never quite sure what vSphere's numbers represent). This VM is dedicated to Tech Pubs, so there isn't much simultaneous heavy-duty activity. Typically, we have only one person generating the book PDFs or WebWorks Reverb help, but these tasks do not take place at the same time.

Since this morning, we have successfully restored files from backup and generated a PDF of the book. Interestingly enough, after the PDF was successfully created, FrameMaker crashed while saving an individual file in the book (again a "no memory" issue, directly on the host).

We have the latest FM 10 patch installed. I'm reluctant to upgrade to FM 2015, but I suppose that's what Adobe would recommend.

[Bob_Niland]

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?