Skip to main content
P
ptc-9539261-Visitor
1-Visitor
January 21, 2013
Question

PE interactive problem

  • January 21, 2013
  • 5 replies
  • 1379 views

Adepters:


I’ve got a strange problem with PE 5.3. I recently added an entirely new doctype to our custom DocTypes folder and an entry in the catalog file pointing to the new doctype. After restarting/rebooting the server, I’m able to successfully generate direct-to-PDF using our normal process for sending print jobs to PE. However, when I open the source XML file in PE Interactive (which opens the file without errors and points to the doctype in all session information variables) and try to Print Preview or Compose > PDF file, I get an error window with this message:


[A20448] Document type not installed on the PE server. Check the server’s catalog path setting.


Anyone know how to get past this? I can print preview and compose PDF with any of our previously existing doctypes – just not this new one.


Thanks,


Dave

    5 replies

    N
    naglists1-Visitor
    1-Visitor
    January 21, 2013
    Does setting peservices=off change behavior?


    P
    ptc-9539261-VisitorAuthor
    1-Visitor
    January 22, 2013

    Hmmm... That seemed to cure it. I don't understand why older doctypes worked with peservices set to on...

    N
    naglists1-Visitor
    1-Visitor
    January 22, 2013
    Not a lot of help predicting the next outcome ... but I have this vague
    recollection that different things are refreshed by an f=init call, a
    Tomcat restart, and an OS restart. I even more vaguely remembering some of
    those things differ between Arbortext versions.



    G
    GarethOakes16-Pearl
    16-Pearl
    January 22, 2013
    If you have a look at the "peserverurl" preference you will find which other PE server that your PE Interactive was trying to connect to when peservices=on ...

    -G
      A
      Anonymous
      January 22, 2013
      Were you able to open the PE Composition Information and see if this document type appeared?

      Another (long shot) issue... Did you define any composers (ccf files) in the DCF file? Should be a Composition element with one or more Composer children, and they correspond with the CCF files used for HTML, xsl-fo, PDF, web composition. You might be getting weird results if there are no composers defined.
      Terms & ConditionsAccessibility statement