@uaprogrammer,
We managed to replicate the problem of validation failure on the Preflight. We have logged tickets in our bug tracking system as follows:
File name: 1728_input.pdf
PDFNET-43472: PDF to PDF/A-1b - the output PDF does not pass validation
File name: 1741_input.pdf
PDFNET-43473: PDF to PDF/A-1b - the output PDF does not pass validation
We have linked your post to these tickets and will keep you informed regarding any available updates.
I had the same problem, and now with version 19.10 it works. But now I have another problem because when I digitally sign the document with infocert, the PDF contained in the generated p7m file does not appear to be compliant.
For example on the PTT portal (Processo Tributario Telematico (PTT) - SIGIT - Giustizia Tributaria) the PDF/A-1b extracted from p7m File, does not pass validation.Documentazione.zip (4.7 MB)
Would you please elaborate the steps to reproduce this issue with Aspose.PDF for .NET API and how are you testing the validation so that we may investigate further.
The original file not PDF/A is "1 - ExampleFilePDF.pdf"
Through the Aspose.PDF library for .NET 19.10 we get the file “2- ExampleFilePDF.pdf” in PDF / A 1b valid for PTT Portal (https://www.giustiziatributaria.gov.it/gt/web/guest/processo-tributario -telematico-pTT-sigit)
Through the INFOCERT API we sign the document and get file "3 - ExampleFilePDF.pdf.p7m"
Through the Dike GoSign program we extract the signed PDF file and obtain the file "4 - ExampleFilePDF.pdf"
The file “4 - ExampleFilePDF.pdf” does not appear to be compliant as PDF / A on the PTT portal (https://www.giustiziatributaria.gov.it/gt/web/guest/processo-tributario-telematico-ptt-sigit).
Would you please help us narrow down the problem as the problem can be related to PDF only if the PDF/A1b generated at second step is not valid. So kindly share if 2- ExampleFilePDF.pdf is PDF/A compliant or not? Please also share the code snippet you are using for this conversion.
Since the file generated at step 2 with Aspose.PDF for .NET API is PDF/A compliant, and further modifications are made be 3rd party tools. So probably the reason lies with those tools because Aspose.PDF API is related until secong step. Moreover, you may also test the same with a PDF/A file generated by Adobe Acrobat and then notice if issue reproduces or not.
Hi,
I tried to do the same operations starting from a PDF / A generated by a word file (save as PDF, options PDF / A). In this case, the PDF extracted from the P7M file, is PDF/A compliant. I attach the P7M files generated one starting from a PDF / A created with Aspose and one starting from a PDF / A generated by a word file.
We have logged a ticket with ID PDFNET-47199 in our issue management system for further investigation and resolution. The ticket ID has been linked with this thread so that you will receive notification as soon as the ticket is resolved.
Please note that PDFNET-47199 has been logged few weeks ago under free support model and will be investigated on first come first serve basis. Therefore, it may take some months to resolve. As soon as we have some definite updates regarding ticket resolution, we will let you know.
Furthermore, we also offer paid support model where issues are resolved on urgent basis and have priority over the issues logged under free support model. You may check our Paid Support options for your reference.
Regretfully the issue is not yet resolved due to other high priority issues in the queue. However, we will surely let you know as soon as there is some update in this regard. Please spare us some time.
We are sad to inform you that the tickets PDFNET-43472 and PDFNET-47199 are not yet resolved and their investigation is not yet done. We will inform you within this forum thread as soon as we have some updates in this regard. Please give us some time.
We are afraid that we do not have any update regarding resolution of the issues i.e. PDFNET-43472 and PDFNET-47199. However, we will let you know in this forum thread as soon as they are fixed. We highly appreciate your patience in this regard.
We really regret to share that both ticket have not been yet resolved. However, we already have noticed your concerns and logged them along with the tickets. You will surely be notified as soon as some definite progress is made towards tickets resolution.
We apologize for your inconvenience.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
Enables storage, such as cookies, related to analytics.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.