Internal Error: 7004, 5048919, 6050789, 6047376

[_n3u_]

Hi all,
I got this error and after looking for it into the web, I tend to believe that no one had the same.

I'm using Framemaker 7.0 (Build 7.0p492) on Windows XP with the fdk 7.0.
Also, I'm using Acrobat Distiller 5.0.5.2001101100.
As a note, I have to say that I'm not allowed to change any release of this applications because the supply chain is quite long and noone wants to run the risk to incur in compatibility problems.

My program uses the APIs to open a book, show/hide certain conditionals (selected with the arguments) and save the result in a PDF file.
It works generally fine but for certain sets of conditionals Framemaker crashes giving the Internal Error of the subject.
I'm posting also the FrameLog at the end of this message.

Does anyone have a clue about this?
Please don't hesitate to suggest whatever thing that can be useful because I really need to solve this.

Thanks for your attention,
n3u.

Here is the the FrameLog:

=== Header Begin ===
Internal Error: 7004, 5048919, 6050789, 6047376
FrameMaker 7.0.0 for Intel
Build: 7.0p492
Window System: MSWindows
Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 2)
Generated on: sabato 30 agosto 2008 19.07.45
To file: c:\programmi\adobe\framemaker7.0\FrameLog_08.08.30_19.07.45.txt
=== Header End ===

=== Stack Trace Begin ===
$4d0a57
$5c53e5
$5c4690
$5c5ba2
$74c663
=== Stack Trace End ===

=== Open Window List Begin ===
# not implemented
=== Open Window List End ===

=== Recent Commands Begin ===
=== Recent Commands End ===

=== Recent API Calls Begin ===
# not implemented
=== Recent API Calls End ===

=== Windows Relocation Information Begin ===
Application: 00400000
framemaker.exe: 00400000 00477000
ntdll.dll: 7c910000 000b6000
kernel32.dll: 7c800000 00100000
ADVAPI32.dll: 77f40000 000ab000
RPCRT4.dll: 77da0000 00092000
Secur32.dll: 77f10000 00011000
COMCTL32.dll: 5d4d0000 0009a000
GDI32.dll: 77e40000 00047000
USER32.dll: 7e390000 00090000
comdlg32.dll: 76360000 0004a000
SHLWAPI.dll: 77e90000 00076000
msvcrt.dll: 77be0000 00058000
SHELL32.dll: 7c9d0000 0081e000
FMDBMS32.dll: 10000000 00013000
ole32.dll: 774b0000 0013d000
OLECLI32.dll: 71da0000 00015000
MPR.dll: 71aa0000 00012000
oledlg.dll: 7e1e0000 00022000
VERSION.dll: 77bd0000 00008000
WINSPOOL.DRV: 72f70000 00026000
SFTTR32.dll: 00330000 00020000
BIB.dll: 00350000 0002d000
CoolType.dll: 00880000 00171000
WINMM.dll: 76b00000 0002e000
SVGRE.dll: 6f130000 0023c000
icuuc20.dll: 4a800000 00056000
icudt20.dll: 4ad00000 007d8000
IMM32.DLL: 76340000 0001d000
LPK.DLL: 62e40000 00009000
USP10.dll: 74d20000 0006b000
avgrsstx.dll: 003b0000 00005000
comctl32.dll: 773a0000 00103000
uxtheme.dll: 5b180000 00038000
RocketDock.dll: 01330000 00012000
PSAPI.DLL: 76bb0000 0000b000
MSCTF.dll: 746b0000 0004b000
shfolder.dll: 76740000 00009000
fmres.dll: 014c0000 0009e000
fmdlg.dll: 01560000 00057000
fmcustom.dll: 015c0000 0000a000
apphelp.dll: 77b10000 00022000
msctfime.ime: 752e0000 0002e000
CLBCATQ.DLL: 76f90000 0007f000
COMRes.dll: 77010000 000d2000
OLEAUT32.dll: 770f0000 0008b000
ps5UI.dll: 4f500000 00021000
PSCRIPT5.DLL: 4ce00000 00075000
mscms.dll: 73aa0000 00015000
AD2KRePi.DLL: 70000000 00006000
ATMLIB.dll: 73b90000 0000b000
ACE.dll: 01c10000 00074000
OPP.dll: 017e0000 00017000
AGM.dll: 01ca0000 00254000
PDFL50.dll: 01f10000 002d0000
AdobeWeb.dll: 60800000 0011f000
xpsp2res.dll: 20000000 002d5000
clickprt.dll: 02630000 00037000
mailer.dll: 02680000 0003f000
MAPI32.DLL: 62280000 0001f000
bookerrlog.dll: 026d0000 00044000
pdfsize.dll: 02730000 00045000
WebDAV.dll: 02790000 00084000
ARM.dll: 61800000 00108000
mapper.dll: 02840000 0005b000
masterpages.dll: 029b0000 0003e000
tablesort.dll: 02a00000 00042000
afmfdk.dll: 02b60000 00049000
SETUPAPI.dll: 778f0000 000f7000
GRPHFILT.DLL: 03a80000 0001a000
=== Windows Relocation Information End ===

=== Windows Stack Traceback Begin ===
[Sta

[_Heinz_Wrobel_]

FM can react rather violently if you change conditional text settings and thereby break cross references in a book. I had the problem that updating a book crashed FM when I had accidentally set up things in a way that the target of a visible cross ref suddenly turned out to be in hidden text.
Took me a while to understand this, and now I am careful to avoid such a situation. While a hidden target of a visible cross ref is not a good idea, I think FM could be a bit nicer about that situation and tell you about it in a friendly way.

Hope this helps.

Heinz

[_Scott_Prentice_]

I think that the first thing you need to do is to determine where in your process, this crash is occurring. If you can repeat the crash by setting the conditions in a certain way, is it the setting of those conditions, the update of the book (if you do that), or the PDF generation that's causing the error? Can you duplicate the crash by setting the conditions manually?

Sounds like you need to do a bit more debugging.

...scott

[_n3u_]

Scott,
the crash is sure under certain conditions.

What I can see is that showing certain pattern of "conditionals" the crash always happens, while the same book with other show/hide combination of conditionals it doesn't.

The exact moment where the FrameMaker crashes and gives the error is during the F_ApiSave call inside this piece of code:

BOOL DMFrameMaker::SavePDF(CString sPDFLocation)
{
F_PropValsT params, *returnp;

params = F_ApiGetSaveDefaultParams();
returnp = NULL;

int i = F_ApiGetPropIndex(&params, FS_FileType);
params.val.propVal.u.ival = FV_SaveFmtPdf;

m_foDocId = F_ApiSave(m_foDocId,
(unsigned char *) sPDFLocation.GetBuffer(512),
&params,
&returnp);

F_ApiPrintSaveStatus(returnp);

return TRUE;
}

I tried to set the conditionals manually but the same conditionals aren't giving problems to the FrameMaker in an interactive run.
So I fear it can be a problem inside my program or the API, but I don't know how to inspect further (keep in mind that with a single different conditional to show/hide it works well).

Please, help me discover something more about this mess!
Thanks,
n3u.

[_Scott_Prentice_]

Hi n3u...

Does the crash always happen on the second (or later) save? You're not freeing the F_PropValsT variables. Try adding this before the return ..

F_ApiDeallocatePropVals(&params);
F_ApiDeallocatePropVals(returnp);

In order to separate the PDF issue from the scene, you might try making a test version of the app that saves to another FM file rather that saving to PDF. There are all sorts of reasons that PDF export can have problems.

Also .. I've seen some funky problems when mixing CPP data types with FDK apps. I try to keep the two quite separate. It may just be unnecessary paranoia on my part .. but you never know.

...scott

[_n3u_]

Hi,

my application does only one save and then closes itself, however I'm concerned about good programming (and also I'm desperate) so I added the two lines you suggested to the function.

I also did some changes to the variables type, so my new code looks like this:

BOOL DMFrameMaker::SavePDF(CString sPDFLocation)
{
F_PropValsT params, *returnp;
StringT stPDFLocation = (unsigned char *) sPDFLocation.GetBuffer(1024);

params = F_ApiGetSaveDefaultParams();
returnp = NULL;
int i = F_ApiGetPropIndex(&params, FS_FileType);
params.val.propVal.u.ival = FV_SaveFmtPdf;

m_foDocId = F_ApiSave(m_foDocId, stPDFLocation, &params, &returnp);

F_ApiPrintSaveStatus(returnp);

F_ApiDeallocatePropVals(&params);
F_ApiDeallocatePropVals(returnp);

return TRUE;
}

Needless to say, the FM still crashes.
What can I do now?
Please help me!
n3u.

[_Scott_Prentice_]

I'd try saving to a MIF rather than a PDF to see if it is a PDF issue or a general save issue. If it still crashes, I'd take a careful look at what types of objects are hidden .. is there something that's hidden that is referenced by objects that are not hidden?

...scott

[_n3u_]

I saved it into MIF format, with the flag "FV_SaveFmtInterchange" and, as far as I can see it, it worked well under the same conditions of the PDF creation crash (same everything, of course also same conditionals' show/hide pattern).

I opened the .mif file with FM7 and the contents seem ok (I'm not an FM technician so I'm not sure about how to do a fair check of a 250 pages book).

Can this test exclude the option of being a cross references problem?

Thanks,
n3u.

[_Scott_Prentice_]

Yeah .. it sounds like the problem has to do with PDF generation. You might try changing the default joboptions file and setting different PDF options. I'm not a PDF expert, but saving to PDF is one of those things that doesn't always work properly. You could try saving to PS then running the Distiller separately.

...scott

[Art Campbell]

If I were you, I'd try downloading the free 30-day eval of Acrobat 9 Pro, and with a fresh install, see if you can make it work. I'm sure Acrobat 5 was useful, but it's a Win2000 era program, if not earlier than that.

Also, in passing, DO NOT USE SaveAs PDF. Always set up your system so that the PDF printer is (either permanently, or via plug-in, temporarily) as the system default printer. And then Print to it. (doing the intermediate step of saving as a PS file is unlikely to do much).

Art

[_n3u_]

Hi,
I did as suggested:
- installed of acrobat 9 pro trial
- set the PDF printer as default printer
- changed from F_ApiSave to F_ApiSilentPrintDoc (there's another way to print?)

As for FrameMaker 7 and FDK 7 nothing changed.
It still crashes on the same page, depending on the show/hide pattern.
To be sure, this evening I'll try also with FrameMaker 8 and FDK 8, but... :(

Do you have other clues?
How can I survive to this?
There's a place where I can post the FrameMaker error or whatever to know something more about the possible causes of all this crashes?

Thanks alot,
n3u.

[Art Campbell]

n3U,
I hate to state the obvious, but you've updated software. And if there's still a crash on the same page, there's something physically wrong on the page or in that file.
You could try printing it, or that chapter separately... but I think you need to start by making backup copy of the problem file and then saving the file, manually, as a MIF file, opening that in Frame, and saving over your other file. This should clean up any file corruption, stray characters, and malformed tags.
If the file still triggers a crash, you need to deconstruct it, piece by piece or condition by condition until you find out what content is causing the problem.

Cheers,
Art

[_n3u_]

Hi all,
I went on investigating further the problem and I discovered how to examine the state of the book immediately after FrameMaker crashes.

Inside some previous post of Scott, he said to seek for something about hidden objects referenced by showed objects.
Well I finally discovered that I'm in that situation. There are two conditional texts, A and B, where A cross-reference to B, but B is hidden.

I don't know how to get rid of this. If I check the XRef list attached to the document I see that there's an XRef "unresolved".
I tried to bypass the problem by F_ApiDelete-ing on the XRef object, but it 's useless.

I'm getting closer to the cause of the problem... please help me!

Thanks for your efforts,
n3u.

[_Heinz_Wrobel_]

Yes, cross refs to hidden text are not handled well.

1. Make B visible again
2. Remove/fix correct cross ref in A to B so that it either is also hidden in the end or points to visible text
3. Rebuild the book to get everything into basic order with visible refs
4. Hide B again (assuming A is fixed now and no longer points to a hidden B!)
5. Rebuild the book again.

Internal error should be gone then.

Heinz

[_Heinz_Wrobel_]

-unhide B
-rebuild book to fix xrefs
- fix ref A to not point to a hidden B anymore
- rebuild book to fix xrefs
- hide B again
- rebuild book

This should be fixing xrefs to hidden text.

Heinz

[_n3u_]

Hi Heinz!

I tried to follow your list but I've been unable to find a "rebuild" command inside FrameMaker (I'm a developer, I don't know the application from the user side).

I wondered if you meant "edit->update book" and I followed your list doing update book each time you said rebuild book. Altought the book doesn't complain anymore about "unresolved" xrefs, the whole lot crashed again (on the same page as before).

So I thought you meant "edit->update cross-references" and so I opened again the book and executed the command for each document inside the book. Still crashes.

What's the right way to rebuild a book?

Thanks alot!!!!
n3u.

[Art Campbell]

Yes, that's the command to update/build the book.

What else is on the page? Some type of content is causing the crash.

If you don't see anything, SaveAs a MIF format file, then open that file and save it as a FM file. That should clean out any stray characters and parse the file to ensure that it's valid.