PAH got corrupted after editing the Text

Hi

our PAH recently got corrupted after I changed the language.  This is the First time I run into this issue. can someone help me with this?

There was end error while parsing the PDF file. The PDF is likely corrupt or invalid. at ceTe.DynamicPDF.Merger.PdfDocument.e()
at ceTe.DynamicPDF.Merger.PdfDocument..ctor(fv A_0, String A_1)
at ceTe.DynamicPDF.Merger.MergeDocument.Append(String filePath, MergeOptions options)
at Tessitura.ProcessingService.Pdf.GenerateTicket(Tickets tickets)
at Tessitura.ProcessingService.OrderService.PrintOrder(Tickets tickets, Int32 orderNumber, Int32 eaddress_no, String email, DateTime orderDate, Int32 customerNumber, Int32 totalCount, Int32 currentCount, PrintAtHomeSettings htOrgSettings)
at Tessitura.ProcessingService.OrderService.Process(Boolean receipt)

Unable to cast object of type 'zz93.m' to type 'zz93.m2'.
at zz93.eo..ctor(ji A_0)
at ceTe.DynamicPDF.Merger.Forms.PdfFormField..ctor(jp A_0, PdfForm A_1, Int32 A_2, PdfFormField A_3, ml A_4)
at ceTe.DynamicPDF.Merger.Forms.PdfTextField..ctor(jp A_0, PdfForm A_1, Int32 A_2, PdfFormField A_3, ml A_4)
at ceTe.DynamicPDF.Merger.Forms.PdfFormField.a(jp A_0, PdfForm A_1, Int32 A_2, PdfFormField A_3, ml A_4)
at zz93.nx.a(m A_0, PdfForm A_1, PdfFormField A_2, jp A_3)
at ceTe.DynamicPDF.Merger.Forms.PdfFormFieldList.a(jp A_0, PdfForm A_1, PdfFormField A_2, m A_3)
at ceTe.DynamicPDF.Merger.Forms.PdfFormFieldList..ctor(jp A_0, PdfForm A_1, PdfFormField A_2, ji A_3)
at ceTe.DynamicPDF.Merger.Forms.PdfForm..ctor(jp A_0, ml A_1)
at ceTe.DynamicPDF.Merger.PdfDocument.b(jp A_0)
at ceTe.DynamicPDF.Merger.PdfDocument.e()

Parents
  • How nice to get an actual error message!  At best we get "Object reference not found", and frequently not even that.  We've been told, however, that the template PDFs can become corrupted, at least in some fashion invisible to Adobe but critical to TPS, and that the only solution is to rebuild the template from scratch.  The corruption that effects us is limited to the form fields used to import ticket elements, so the base design of the template is generally safe, but when it happens we just start with a base design and then re-add all of the form elements.

Reply
  • How nice to get an actual error message!  At best we get "Object reference not found", and frequently not even that.  We've been told, however, that the template PDFs can become corrupted, at least in some fashion invisible to Adobe but critical to TPS, and that the only solution is to rebuild the template from scratch.  The corruption that effects us is limited to the form fields used to import ticket elements, so the base design of the template is generally safe, but when it happens we just start with a base design and then re-add all of the form elements.

Children