Internal Error: 8004, 4331081, 4339064, 4341927

When attempting to import Word 2003/XP documents using .rtf saves of .doc files into Framemaker 8 p277, I get the error above. Importing the .doc file directly gives an error message but does not generate the error above. Copying the file from Word and attempting to paste special as .rtf causes the error message above.
The same thing happens if I cut pictures and figures out of the Word document before importing.
I am using Office 10 XP and Windows XP Pro SP3. Both have the latest updates.
Can anyone give a hint about what must be done to the Word file in order to achieve a successful import? (I have to do these imports on a regular basis.)
Thanks,
Ed

Art,
Thanks for your suggestion. Importing with the Japanese RTF works!
While it does not work perfectly, it still will save me an incredible
amount of work. So it appears that my RTF and DOC converters are
broken now.
I don't think they were prior to 8 Rev 3 or 4. I wonder how I back
rev. I guess I will have to explore the process of going back.
Thanks again!!!
Ed

Similar Messages

Cannot Print PDF Large volume PDF. Internal Error: 8004, 6343724, 8484240, 0

We are having an issue with printing to PDF for large volume FM files. PDF appear to work for small/medium volume PDFs however.
Internal Error: 8004, 6343724, 8484240, 0
FrameMaker 8.0.0 for Intel
Build: 8.0p273
I've checked the default printer and it is set to Adobe PDF. I've also tried to print to PDF to a different FM file just in case the current file might be corrupted and the same error appears. At this point this issue is affecting our work as we cannot save it to PDF. Does anyone have any ideas that I can try?
Thanks
Steve

Shelia,
Thank you for your reply. Here are some further details on the question that you asked:
1. At that beginning, because the PDF file has 226 pages as total and consists of 19 fm files, which I mean the big volume, I thought this problem occurs. (FYI, the small/medium volume means the PDF file has 112 pages as total and consists of 16 fm files / only around 20 pages as total and consists of only 1 fm file.)
However, now, I know the problem occurs in the specific two very small fm files. These two fm files are only 3 pages / 15 pages as total and consists of only one fm file. – So, I do not think the volume relates to this problem.
2. I always use “save it to PDF” to create PDF files so far. I am using the PDF distiller that came with FrameMaker8.
3. All files including graphics are in my local drive (C drive).
So I'm wondering if the problem is possible due to the two specific fm files. If so, what are your recommendations to get around this?
Thanks
Steve

Internal Error: 8004, 4867936, 4920984, 4921436 while attempting to save as XML

Hi,
I get the following error while trying to save fm files as XML.
=== Header Begin ===
Internal Error: 8004, 4867936, 4920984, 4921436
FrameMaker 8.0.0 for Intel
Build: 8.0p266
Window System: MSWindows
Operating System: Windows NT 6.1 (major.minor.build: 6.1.7600 )
Generated on: Tuesday, November 26, 2013 2:01:40 PM
To file: c:\program files\adobe\framemaker8\FrameLog_13.11.26_14.01.40.txt
=== Header End ===
-ramesh

Yes .. definitely get the latest FM8 patch, that may solve the problem.
http://www.adobe.com/support/downloads/product.jsp?product=22&platform=Windows
However, if this is a structured document, you should also be sure to validate (Element > Validate) the file before saving. Also check for graphics that are referenced from a reference page, and you may want to delete any cross-refs that aren't resolved (or resolve them). FM can crash for a variety of reasons when saving to XML, anything that's slightly amiss is likely to cause a problem.
Cheers,
...scott

FM 8 Internal error 8004,6335581,8468256,0

I have been using your excellent word processor during last years (beginning from v5.5.1 dec.1996) to my great satisfaction.
This morning I have installed the trial version of FMaker 8.0 (Framemaker8_WWEFG_2.exe) before purchasing it and I have tried to open a document of mine, written with the version 7.2, but the prog aborted after this message:
Internal Error 8004,6335581,8468256,0. FrameMaker has detected a serious problem and must quit.
A file named "k:\fmaker80\FrameLog_07.08.16_09.55.44.txt" has been generated which contains
information that may help Frame development improve the product for future releases.
Please describe your recent actions and send this, along with the generated file,
to [email protected] Due to the volume of feedback, we are unable to respond to technical questions.
For support, please refer to http://www.adobe.com/support.
Any advice?
Paolo GREGORIO
[email protected]

I can suggest the following:
1. Restart the machine. Sometimes this does resolve the problem.
2. Create a new document with the trial version (yes one can save with the trial version) - this is to determine if installation of the trial version is correct.
3. Create a new simple document in English language in FM7.2 (.FM or .MIF), and try loading this in the trial version. Or just try opening a template (shipped with FM 7.2) in the FM8 trial version.
4. Move to the latest FM 8 trial on the adobe site (FM 8.0.1 EFGJ trial)
5. Delete the font cache (c:\windows\system32\fntcache.dat), and restart the machine. The font cache will rebuild itself.
Please let us know the results for each step. If none of these work, I would request a sample frame file to be sent to us, with which the crash can be reproduced. Please also include the corresponding crash log file that gets created.
Thanks,
--Sumeer ([email protected])
Senior Engg Mgr,
FrameMaker, RoboHelp, Technical Suite.

Internal Error 8004, 6964255, 4843886, 4843614. FrameMaker has detected a serious problem and must q

Has anyone experienced the above error message? I always receive this message when I start scrolling through a FrameMaker file. It does not matter if I scroll with the mouse or using the keyboard. When I click OK to this message, FrameMaker immediately shuts down. At times, it corrupts the file on a particular page(s) and continually gives me this message. Most often, I need to recreate these lost pages. Very frustrating and I do not know if it is FrameMaker or a problem with refresh and the graphics card. Help!

I wanted to post this as another thread but at the same time I believe it's related to what's been discussed in this one.
These are my error codes when FM has crashed in my system:
Internal Error: 8004, 8443342, 4459945, 4414681
Internal Error: 8004, 6343116, 8483344, 0
Internal Error: 8004, 6961695, 4843246, 4842974
and others that I thought related to the scrolling thing... however, I installed FreeWheel and the crash happened again as soon as I updated my book to generate my lists. I've had the scrolling issue in past and it's true that at the time the FreeWheel solution was pretty effective. However, this time I really am sort of not knowing what to do about it.
I have FM 8 with the latest patches running on Vista.
I would really appreciate any input that could help me work this out.

FDK and FM 8: Internal Error: 8004, 6343724, 8484240, 0. FrameMaker has detected a serious problem a

I use FDK9 and FrameMaker 8. I used Visual C++ 2008 Express Edition and Microsoft SDKs to compiled sample FDK hello.c program, C:\Program Files\Adobe\FDK9\samples\hello. It compliled just fine without error or warning message. I registered the hello.dll to fminit directory and added the line: "hello=Standard, Greets user at startup,fminit\hello.dll, all" to maker.ini. When I brought up FrameMaker I got error message:
Internal Error: 8004, 6343724, 8484240, 0. FrameMaker has detected a serious problem and must quit.
A file named fminit\hello.dll has been generated which contains
information that may help Frame development improve the product for future releases.
Please describe your recent actions and send this, along with the generated file,
to [email protected] Due to the volume of feedback, we are unable to respond to technical questions.
For support, please refer to http://www.adobe.com/support.
Please help.
Thank you,
Thai Nguyen

Thai,
Here is what Wikipedia says:
"In April 2003, Microsoft introduced a minor upgrade to Visual Studio .NET called Visual Studio .NET 2003, codenamed Everett (for the city of the same name). It includes an upgrade to the .NET Framework, version 1.1, and is the first release to support for developing programs for mobile devices, using either ASP.NET or the .NET Compact Framework. The Visual C++ compiler's standards-compliance was improved, especially in the area of partial template specialization. Visual C++ Toolkit 2003 is a free version of the same C++ compiler shipped with Visual Studio .NET 2003 without the IDE, though it is no longer available and now superseded by the Express Editions. The internal version number of Visual Studio .NET 2003 is version 7.1 while the file format version is 8.0."
I think you should be OK with the later compiler. I don't know what is causing the crash, though. Perhaps you might consider setting up a new workspace according to the instructions in the Windows guide, then add hello.c to it, and see what happens. That would at least let you know if there is a compatibility problem with the sample, or if your current setup will simply not allow FDK9 development for FM8.
By the way, there is a Yahoo group dedicated to FDK development. If you don't get an answer here, consider posting there. Some of the users on that list are considerably smarter than me about these types of issues.
http://groups.yahoo.com/group/Frame_dev/
Russ

Frame 8.0 Internal Error: 8004, 4868576, 5714586, 5712441

I am getting a Frame crash in the middle of a chapter file (all of a sudden). I was trying ot replace a graphic inside an anchored frame when it crashes, and still crashes when I get to the page. The error is below. Any insight?
=== Header Begin ===
Internal Error: 8004, 4868576, 5714586, 5712441
FrameMaker 8.0.0 for Intel
Build: 8.0p277
Window System: MSWindows
Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 2)
Generated on: Wednesday, June 25, 2008 2:04:07 PM
To file: c:\program files\adobe\framemaker8\FrameLog_08.06.25_14.04.07.txt
=== Header End ===
=== Stack Trace Begin ===
$4a49e0
$57329a
$572a39
$573074
$5734c0
$5c5470
$5c6144
$5c65df
$5b8bf8
$5c7e49
$5c8069
$5a781c
$5a887f
$5a8cb0
$5a80b4
$7bf86d
$7bf9d2
$5a8cf3
$5a583a
$5a7f85
$7bf86d
$7bf9d2
$5a8cf3
$5a5658
$49efb3
$4ae3df
$4ae4d3
$693b01
$693e4f
$694180
$495ebf
$496326
$49f124
$49f610
$496a21
$4f3a54
$4f3c25
$60c799
$60d213
$60d3ac
=== 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 007c1000
ntdll.dll: 7c900000 000b0000
kernel32.dll: 7c800000 000f5000
ADVAPI32.dll: 77dd0000 0009b000
RPCRT4.dll: 77e70000 00091000
Asn.er.dll: 10000000 0003c000
OLECLI32.dll: 71e10000 00015000
USER32.dll: 7e410000 00090000
GDI32.dll: 77f10000 00047000
MPR.dll: 71b20000 00012000
SFTTR32.dll: 00330000 00021000
COMCTL32.dll: 773d0000 00103000
msvcrt.dll: 77c10000 00058000
SHLWAPI.dll: 77f60000 00076000
comdlg32.dll: 763b0000 00049000
SHELL32.dll: 7c9c0000 00817000
FMDBMS32.dll: 00370000 0002f000
ole32.dll: 774e0000 0013d000
OLEAUT32.dll: 77120000 0008b000
oledlg.dll: 7df70000 00022000
VERSION.dll: 77c00000 00008000
WINSPOOL.DRV: 73000000 00026000
urlmon.dll: 42cf0000 00127000
iertutil.dll: 42990000 00045000
NETAPI32.dll: 5b860000 00055000
WS2_32.dll: 71ab0000 00017000
WS2HELP.dll: 71aa0000 00008000
epic_eula.dll: 003a0000 00024000
epic_pers.dll: 003d0000 0001f000
asneu.dll: 00bd0000 00020000
epic_regs.dll: 00bf0000 00029000
WININET.dll: 42c10000 000cf000
Normaliz.dll: 003f0000 00009000
AdobeUpdater.dll: 00c20000 0007e000
BIB.dll: 00cb0000 0004a000
SVGRE.dll: 6f130000 00325000
JP2KLib.dll: 00d20000 00071000
MSVCR80.dll: 78130000 0009b000
icuuc28.dll: 4a800000 0008f000
icudt28l.dll: 4ad00000 0083a000
MSVCR71.dll: 7c340000 00056000
icuin28.dll: 4a900000 000a2000
icuio28.dll: 4ab00000 0000c000
MSVCP71.dll: 7c3a0000 0007b000
AdobePDFL.dll: 00db0000 00493000
AdobeXMP.dll: 01260000 00061000
BIBUtils.dll: 012e0000 00040000
ACE.dll: 01330000 000ca000
AGM.dll: 01410000 00506000
ARE.dll: 01930000 0004b000
CoolType.dll: 01990000 00284000
AXE8SharedExpat.dll: 01c30000 0002d000
XAPToolkitRelease.dll: 01c70000 0008b000
IMM32.DLL: 76390000 0001d000
uxtheme.dll: 5ad70000 00038000
MSCTF.dll: 74720000 0004b000
shfolder.dll: 76780000 00009000
Secur32.dll: 77fe0000 00011000
fmres.dll: 02a40000 0017e000
fmdlg.dll: 02bc0000 0005a000
fmcustom.dll: 02c20000 00024000
msctfime.ime: 755c0000 0002e000
adobe_caps.dll: 02d60000 00037000
MSVCP80.dll: 7c420000 00087000
SETUPAPI.dll: 77920000 000f3000
NTMARTA.DLL: 77690000 00021000
WLDAP32.dll: 76f60000 0002c000
SAMLIB.dll: 71bf0000 00013000
adobe_epic.dll: 02eb0000 00061000
OLEACC.dll: 74c80000 0002c000
MSVCP60.dll: 76080000 00065000
adobe_eula.dll: 02f60000 00059000
adobe_personalization.dll: 02ff0000 0005a000
AdobeLM_libFNP.dll: 03080000 00275000
iphlpapi.dll: 76d60000 00019000
snmpapi.dll: 71f60000 00008000
rsaenh.dll: 0ffd0000 00028000
mswsock.dll: 71a50000 0003f000
DNSAPI.dll: 76f20000 00027000
WINTRUST.dll: 76c30000 0002e000
CRYPT32.dll: 77a80000 00094000
MSASN1.

Sheila's reply seems to be the answer except that I was unable to save the .mif file as a .fm file. I created another .fm file and copied the text and graphics from the .mif into the new fm, which I was then able to rename to replace the corrupt .fm (which I had renamed to something else in the meantime).
I would be nice to know what causes this kind of corruption in case it is something I can avoid in the future.

Internal Error: 8004, 7074840, 7076383, 6297905

Has anyone encountered this error, and do you have a fix or workaround? It's not in the knowledgebase. Symptoms are: FM 8.0 p277, creating PDF using Distill Professional 8.1.2; FM crashes when you try to build a PDF out of a book in one file. I have sent this fileset and the log to Adobe.

Jack, better late than never.... We had the very same internal error also running FM 8.0p277. Our problem wasn't with printing to PDF though, we got the error just trying to open FM files. It turned out to be some weird special characters in the user.dct. We cleaned it up and that solved the problem. Of course if you're not bothered about the 'learned' words in your spelling checker you can just delete the file. Open the user.dct in Frame (under XP it's in C:\Documents and Settings\<username>\Application Data\Adobe\FrameMaker\8.0\user.dct). Select 'Treat each Line As a Paragraph'. Select 'Encoding' as required. Read. Remove any odd looking characters. Save as 'Text only'. Select 'Put a Carriage Return: Only between Paragraphs'. Save. Delete the user.dct file. Open any FM file and 'learn' a new word in the spelling checker to create a new user.dct file. In the spelling checker under 'Dictionaries' select 'Personal Dictionary - Merge from File' and select the cleaned up text file. Apparently the user.dct can be very sneakily responsible for a number of instability issues - Derek Fosberry had this problem with FM 7.1: http://www.adobeforums.com/webx/.59b80c14/3 Your mileage may vary but it worked for us. All the best from Switzerland, De Brit

Internal Error: 8004, 6345644, 8487696, 0 when attempting to Save as PDF

I keep getting this error every time I create a PDF after crashing with a particular book. Now it looks like the PDF creation is corrupted. I have tried creating PDF's from books I had no problems with but I have had no luck without crashing FrameMaker with this exact error. I am using v8.0p277 on Vista Ultimate SP1 with and AMD.
This all started when I opened an older book created in 6.0 and updated in 7.0 and now when I opened it in 8.0 and created a PDF some images were randomly missing from one chapter. They appeared grayed out in the PDF. I opened the chapter and attempted to recreate the PDF and different images were grayed out in the PDF. Next attempt crashed with this error and now it does this every time regardless of the file or book. It appears to do this when it attempts to write the TPS file and access Distiller. I can open Distiller separately with no problems.
I can continue to use FrameMaker but I can't create a PDF using the Save Book As PDF. Is there a way to "Recover" the application without re-installing it?

Aha -- that's very likely the problem. I believe that the XPS Document writer is a "competitor" of sorts to Distiller, so it doesn't surprise me that it wouldn't create an output that Distiller could process.
FM is particularly sensitive to which default printer is used, and the best of all results are generally obtained by 1) having the Acrobat printer instance, or 2) as second best, having a Postscript printer of any sort, set as the default. FM used to specify that it must have a PS printer installed, I believe that's still the case with FM8].
That's one of the reasons that FM comes with a setup for Acrobat Distiller and that it installs Distiller as a printer on the system. [caveat: I'm an XP user, not Vista, so some of the names may be different on Vista]
So, if you do have a printer called "Adobe PDF" or similar, set that as your default printer before you open FM. Also, be sure that you set up Distiller so that it knows where your fonts are located.
There's a great freebie called SetPrint that will automatically set the Acrobat printer as the default for FM opens, here: http://www.sundorne.com
Please let us know if this resolves your problem making PDFs --

Starting fm8 produces: Internal Error: 8004, 7074840, 7076383, 6297905

Hi folks, I know fm8 is OLD, we have fm11 in plan for this year... That said, I have one colleague who can no longer launch fm8, its abends with the subject error msg. I search around and found talk about the user.dct file. Unfortunately she does not have that file. We have tried uninstalling and reinstalling with no luck. I have vague recollections of a simliar problem a few years back where I thought the solution was renaming a folder that fm recreated at startup - was it linguistics or something like that? Bottom line, help! Please?:) Additional info - she was messing around with printer drivers yesterday, however I had her set her default driver to adobe pdf... Any ideas?
Mike

Mike,
FYI, a user.dct or site.dct file is just a text file where entries can also be manually added. However, if there isn't a hyphenation mark for an entry, then FM will crash, Non-hyphenated words must have the hyphen as the leading character, e.g. "-fail", to indicate that no hyphenation should take place. It's possible that this file was incorrectly editied or corrupted.
There are more details on dictionaries and the differences between the older version (FM8 and earlier) vs. the newer ones (FM9 and on) in this blog:
http://blogs.adobe.com/techcomm/2009/12/dictionaries_in_fm9.html

Error while creating SC: Internal Error - termination type TH_RES_FREE

Hi I encountered this error while creating a SC. All attributes for this user are maintained and the "check user" transaction does not give any error.
Amol Mate
Error when processing your request
What has happened?
The URL http://punhjwsapsrm:8000/sap/bc/gui/sap/its/bbpsc02/! was not called due to an error.
Note
The following error text was processed in the system SSS : Internal Error
The error occurred on the application server PUNHJWSAPSRM_SSS_00 and in the work process 1 .
The termination type was: TH_RES_FREE
The ABAP call stack was:
Function: B40B_READ_TABLE of program SAPLBBP_BD_DRIVER_40B
Function: META_READ_TABLE of program SAPLBBP_BD_META_BAPIS
Form: LOCATIONS_READ of program SAPLBBP_ATTR_F4
Function: BBP_ATTR_F4_SLOC_PPOMA of program SAPLBBP_ATTR_F4
Form: STG_LOC_GET_FOR_LOCATION of program SAPLBBP_SC_APP
Form: STG_LOC_GET of program SAPLBBP_SC_APP
Form: LOCATION_STG_LOC_GET of program SAPLBBP_SC_APP
Form: USER_ATTRIBUTES_GET of program SAPLBBP_SC_APP
Form: SC_INIT of program SAPLBBP_SC_APP
Function: BBP_SC_APP_EVENT_DISPATCHER of program SAPLBBP_SC_APP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SSS in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server PUNHJWSAPSRM_SSS_00 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server PUNHJWSAPSRM_SSS_00 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http-c:100-u:PTEST -l:E-s:SSS-i:PUNHJWSAPSRM_SSS_00 -w:1-d:20051121-t:171904-v: TH_RES_FREE-e:Internal Error
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team

Hi Amol,
First of all the sicf transaction is to be used only if you use the internal ITS.
Now you have to put an external breakpoint in the source code of the ABAP Program or FM you want to debug , one of these in your case :
Function: B40B_READ_TABLE of program SAPLBBP_BD_DRIVER_40B
Function: META_READ_TABLE of program SAPLBBP_BD_META_BAPIS
Form: LOCATIONS_READ of program SAPLBBP_ATTR_F4
Function: BBP_ATTR_F4_SLOC_PPOMA of program SAPLBBP_ATTR_F4
Form: STG_LOC_GET_FOR_LOCATION of program SAPLBBP_SC_APP
Form: STG_LOC_GET of program SAPLBBP_SC_APP
Form: LOCATION_STG_LOC_GET of program SAPLBBP_SC_APP
Form: USER_ATTRIBUTES_GET of program SAPLBBP_SC_APP
Then launch the transaction in IE, once the program reaches a breakpoint, you'll get the ABAP debuger in IE.
Regards.
PS: if it doesn't work, put the parameter ~generatedynpro in BBPGLOBAL service to have it applied to all BBP transactions
Vadim

Internal error occurs in background job scheduling

Hi Experts,
We are facing an error message "Internal error occurs in background job scheduling" while trying to execute a custom report(Z report) in background in SA38.
Please find the following observation on our side on this message.
1) This message is not coming for only one report not for others.
2) SU53 screen shot shows that SE38 check is failed, but the weird thing is not happening for other report.
3) Persons having SE38 auhtorization are able to run this report.
Please advise.
Thanks in advance,
Viven

What is the message ID and number? Have you tried OSS search and debugging?
What does this program do, in a nutshell?

Internal error while overwriting a charecteristic value in a class

Hi,
I am overwriting a charecteristic value in a class with a change master.
In CL02 I entered the class and the chnage number and entered in edit mode.
Then I selected the charecteristic view and selected the specific charectristic which value I need to overwrite and then clicked on "Overwrite Value" button.
Now the system has found an internal error: the required characteristic data was not found in characteristics maintenance.
Charecteristic data not found: Internal Error
Please tell me how can I get out of this error.

hi,
Please check whether the overwriting indicator check box in character tab is select or not.
It should be flagged.
Thanks & regards
Reddiy.

ORA-00600: internal error code, arguments: [ktsircinfo_num1]

While taking export of a table received EXP error and while dropping/selecting the same gor ora-600 errors.
. . exporting table TEST4
EXP-00003: no storage definition found for segment(29, 371385)
SQL >Drop table test4 cascade;
ORA-00600: internal error code, arguments: [ktsircinfo_num1], [29], [29], [371385], [], [], [], []
sql> Desc test4;
ORA-00600: internal error code, arguments: [ktsircinfo_num1], [29], [29], [371385], [], [], [], []
I dont want to log TAR with oracle right now... I tried dropping and recreating Undo tablespace but still did not help much . Database version is 9204

hi
read metalink ID - 153788.1
CHeers

Error while transporting objects:Internal error during pvc call: Parameter

Dear all,
We are facing the following error while transporting the individual configuration objects from our PI development system.
Export failed: Internal error during pvc call: Parameter versionSpecifier or version has the invalid value null .
However, it works fine when the complete configuration scenario is transported.
We tried to transport the objects with different user id's, even then the issue still exists.
Any inputs to resolve this will be highly helpful.
Thank you,
Younus

Hi Mohammed,
Answer is inside this oss [Note 1554387 - Error during export from Integration Directory|https://service.sap.com/sap/support/notes/1554387]. In this oss note, solution is to apply a patch (just a patch, not a SP). as it's a litle sap bug...
Note: your issue is also explained with picture in this one "1550549 - PI transport: Internal error during pvc call" (sorry for this one I cannot insert a link)
regards
Mickael
Edited by: Mickael Huchet on Jan 26, 2012 2:50 PM

Internal Error: 8004, 4331081, 4339064, 4341927

Similar Messages

Maybe you are looking for