We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

PDF/A validation error!

Dear Support Team,

The Online-PDF/A-Testtool (http://www.pdf-tools.com/pdf/validate-pdfa-online.aspx) gives back Info-/Errormessages, when the attached Aspose-PDF/A-File in its Attachment check on integration/validation.

Can you please check this and help us to solve it? It is a production issue, so please give this more priority. Please let me know asap!. Attached you will find an example.


Thorsten on behalf of Mohamed

ASPOSE PDF-A Feedback:<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Validating file "00_0000_SB20130529V0007033_102209893_262_0002.eflo..." for conformance level pdfa-2u

dc:description/*[0] :: Missing language qualifier.

dc:title/*[0] :: Missing language qualifier.

The XMP property 'pdfaid:part' has the invalid value '1'. Required is '2'.

The XMP property 'pdfaid:conformance' has the invalid value 'B'. Required is 'A or U'.

The XMP property 'dc:title' is not synchronized with the document information entry 'Title'.

The XMP property 'dc:description' is not synchronized with the document information entry 'Subject'.

The value of the key N is 4 but must be 3.

The key F is required but missing.

A device-specific color space (DeviceRGB) without an appropriate output intent is used.

The document does not conform to the requested standard.

The document doesn't conform to the PDF reference (missing required entries, wrong value types, etc.).

The document contains device-specific color spaces.

The document contains hidden, invisible, non-viewable or non-printable annotations.

The document's meta data is either missing or inconsistent or corrupt.


Hi there,

Thanks for your inquiry. Can you please share your sample code and source document here? So we will test the scenario at our end and will provide you more information accordingly.

Moreover, currently Aspose.Pdf supports PDF to PDFA_1B conversion only. Whereas as per your post it seems you are verifying PDFA-2u compliance.

Sorry for the inconvenience faced.

Best Regards,

Dear Support Team,

attached, you will find the sample code. In the Ticket Attachment, there is the sample document, which you can test and verify on. Please keep us updated.

public void Convert2PdfA(string pdfFile) {

Aspose.Pdf.Document doc = new Aspose.Pdf.Document(pdfFile);

string log =
Path.GetTempPath() + “\log.txt”;

Aspose.Pdf.PdfFormat.PDF_A_1B, Aspose.Pdf.ConvertErrorAction.Delete);



Hi Adnan,

Thanks for contacting support.

I have tested the scenario and I am able to
notice the same problem. For the sake of correction, I have logged this issue
as PDFNEWNET-35464 in our issue tracking system. We will
further look into the details of this problem and will keep you updated on the
status of correction. Please be patient and spare us little time. We are sorry
for this inconvenience.

<!–[if gte mso 9]>
<m:mathFont m:val=“Cambria Math”/>
<m:brkBin m:val=“before”/>
<m:brkBinSub m:val="–"/>
<m:smallFrac m:val=“off”/>
<m:lMargin m:val=“0”/>
<m:rMargin m:val=“0”/>
<m:defJc m:val=“centerGroup”/>
<m:wrapIndent m:val=“1440”/>
<m:intLim m:val=“subSup”/>
<m:naryLim m:val=“undOvr”/>
<![endif]–><!–[if gte mso 10]>

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}


The issues you have found earlier (filed as PDFNEWNET-35464) have been fixed in Aspose.Pdf for .NET 8.2.0.

This message was posted using Notification2Forum from Downloads module by Aspose Notifier.