Skip to main content
P
ptc-9526051-Visitor
1-Visitor
September 26, 2012
Question

Error codes

  • September 26, 2012
  • 4 replies
  • 2765 views
Has anyone seen this error code and know what it means and how to fix it.

[cid:image001.png@01CD9BB4.799CF340]
Regards,
Annie Hartley
The Boeing Company
GSS-IT
ph: 480-891-2287



--
Daniel Glenn
PTC/USER
Director and Portal Support
Support, Educate, Advocate


    4 replies

    S
    SarahPrice10-Marble
    10-Marble
    September 26, 2012
    Yes. I have had this error many times.



    In my experience it has always been a bad piece of data. I would have to take out a section at a time until I found the section with the bad data and correct it.



    Sarah R. Price


    A
    AndyEsslinger1-Visitor
    1-Visitor
    September 26, 2012
    I think it means "open a case with tech support". I've never seen any of these codes defined.

    -Andy

    \ / Andy Esslinger LM Aero - Tech Order Data
    ______-/\-______ (817) 279-0442 1 Lockheed Blvd, MZ 4285
    \_\/_/ (817) 777-3047 Fort Worth, TX 76108-3916

    E
    ebenton1-Visitor
    1-Visitor
    September 26, 2012
    I believe that pubtex is part of the Print Composer process for making PDF. If you can run Print Preview, the Print Preview process may create a DVI file that is viewable up until the point of failure in the document. This may give you some insight into the markup or content that is causing the problem.

    Also, you can create a PUBTEX_FORCE_LOG environmental variable which is used to save formatting errors for later examination. Setting the value to yes will create a log file which can be supplied to PTC Technical Support<">http://127.0.0.1:65330/aeHelp/help7573.html> to troubleshoot formatting problems.
    N
    naglists1-Visitor
    1-Visitor
    September 26, 2012
    I can't remember whether any of the pubtex errors I saw were
    content-driven. I think they always required a fix or some sort of
    workaround provided by support.

    Even if it turns out that you have "bad" content that is somehow causing
    this error, PTC definitely does not like that sort of failure. So even if
    you are able to find a workaround or a fix by removing / fixing your input,
    PTC support (and ultimately the rest of the hive here 😉 would appreciate
    your opening a case with them so they can chase down the problem and fix it
    even if that just means a more graceful exit and providing a helpful error.


    Terms & ConditionsAccessibility statement