Skip to main content
D
Darquise12-Amethyst
12-Amethyst
June 1, 2011
Question

Upgrade PE 5.4 M090 - getting errors

  • June 1, 2011
  • 1 reply
  • 2632 views

hello all,

I'm not to familiar with configurations of Publishing Engine. I just upgraded to 5.4 M090 (from 5.3m050). The PE works and my url is working. However, when I open my custom document, I get some errors which i have no idea what they mean. Can anyone help?

<Division date="Wed Jun 01 09:40:47 2011" millis="1306935647">
<Heading>Compose Aclasta-fr.xml for preview.</Heading>
<Record date="Wed Jun 01 09:40:49 2011" millis="1306935649" msgid="A20965" severity="info" suppress="1">
<Level>MESSAGE</Level>
<Message>Asynchronous operation started using PE server.</Message>
</Record>
</Division><Division date="Wed Jun 01 09:40:50 2011" millis="1306935650">
<Heading>Asynchronous Composition Result</Heading>
<Record date="Wed Jun 01 09:40:50 2011" millis="1306935650" msgid="A11460" severity="error" suppress="0">
<Level>ERROR</Level>
<Message>Formatter error on page -1.! Not a letter.Since context rules are off, this error may be due to an improperlystructured document. This error may not happen if your documentsatisfies context rules. Try setting context rules on.</Message>
</Record>
<Record date="Wed Jun 01 09:40:50 2011" millis="1306935650" severity="error" suppress="0">
<Level>ERROR</Level>
<Message>Runtime error formatting document: main::Error='[A11460] Formatter error on page -1. ! Not a letter. Since context rules are off, this error may be due to an improperly structured document. This error may not happen if your document satisfies context rules. Try setting context rules on. '.</Message>
</Record>
<Record date="Wed Jun 01 09:40:50 2011" millis="1306935650" msgid="A20232" severity="error" suppress="0">
<Level>ERROR</Level>
<Message>Failure post-processing for composer type pdf.</Message>
</Record>
<Record date="Wed Jun 01 09:40:50 2011" millis="1306935650" severity="fatal" suppress="0">
<Level>FATAL ERROR</Level>
<Message>Operation terminated.</Message>
<?Pub Caret -1?>

</Record>
</Division><Division date="Wed Jun 01 09:40:50 2011" millis="1306935650">
<Heading>Asynchronous Composition Error</Heading>
<Record date="Wed Jun 01 09:40:50 2011" millis="1306935650" severity="error" suppress="0">
<Level>ERROR</Level>
<Message>Error response from e3: message = 'Error return '0' from ACL DVI generator.'.</Message>
</Record>
</Division>

    1 reply

    A
    Anonymous
    June 3, 2011

    I can't determine what is going wrong, but I know that if you login to Publishing Engine and start PE Interactive (this is an Editor-like instance of Publishing Engine) and turn off peservices (issue "set peservices=off" from PE Interactive's command line) and open your XML instance and attempt a Compose PDF request you might see more useful error reporting. Give that a shot and see what you find.

    D
    Darquise12-AmethystAuthor
    12-Amethyst
    June 7, 2011

    It turns out it was a hypenation problem. Here is the response from PTC:

    "I successfully identified the cause of the previewing errors. It’s because of the hyphenation files in your application. In 5.4 F000 we changed the way these files get handled. They now need to be in UTF-8 format. The current files are not in that format. You need to convert them so they can be used in 5.4 M090. It’s pretty easy to do, but it simply has to be done. Instructions for converting the files is found in the release notes for 5.4 F000. I looked in release notes for 5.4 M090 and did not find the information. You can locate 5.4 F000 release notes at this link:

    https://www.ptc.com/appserver/cs/doc/refdoc.jsp

    Search for Product=Arbortext Editor, Reported Release=5.4, Document Notes. Pick the document for 5.4 F000. Look at the bottom of page 61 in the PDF. All the instructions are there."

    Terms & ConditionsAccessibility statement