Pdf to Pdf/A conversion fails

admin.aspose.solarpl · July 11, 2016, 5:48am

Hi!

We have problem with certain Pdf's that fails to be converted to Pdf/a.

It takes up a lot of memory (must run in x64) and then we get an exception with "Index was outside the bounds of the array.". The following log is also written:

1.0

2016-07-11 12:04:20

The catalog entry OCProperties is prohibited

ExtGState 'ca' value shall be 1.0

Object is compressed

My code is as follows:

using System;

using System.IO;

using Aspose.Pdf;

namespace Pdf2PdfA

{

static class Program

{

static void Main(string[] args)

{

try

{

new License().SetLicense("Aspose.Total.lic");

using (FileStream fs = new FileStream(args[0], FileMode.Open, FileAccess.Read, FileShare.Read))

using (Document pdfDocument = new Document(fs))

using (FileStream fsLog = new FileStream("PdfConv.log", FileMode.Create, FileAccess.Write, FileShare.None))

{

pdfDocument.Convert(fsLog, PdfFormat.PDF_A_1B, ConvertErrorAction.Delete);

}

catch (Exception exception)

{

Console.WriteLine(exception.Message);

}

We are using Aspose.pdf version 11.8.0.0

tilal.ahmad · July 13, 2016, 10:49am

Hi Cary,

Thanks for your inquiry. I have tested your scenario with shared document using Aspose.Pdf for .NET 11.8.0 and managed to observe the reported exception. For further investigation, I have logged an issue in our issue tracking system as PDFNET-41131 and also linked your request to it. We will keep you updated via this thread regarding the issue status.

We are sorry for the inconvenience caused.

admin.aspose.solarpl · December 16, 2016, 3:08am

Hi!

Are there any updates regarding this issue?

I just tested the case with more recent releases of Aspose.pdf and the problem still exists.

We have a customer who haven’t been able to use parts of our application due to this error for 6 months and we must soon resolve this issue in some way.

BR

Henrik Sämfors

tilal.ahmad · December 19, 2016, 3:43am

Hi Henrik,

Thanks for your feedback. I am afraid your issue is still not resolved, it is pending for investigation in the queue with other issues reported earlier. However we have recorded your concern and asked our product team to complete the issue investigation and share an update as soon as possible. We will notify you as soon some update is available.

We are sorry for the inconvenience.

Best Regards,

aspose.notifier · September 14, 2024, 7:23pm

The issues you have found earlier (filed as PDFNET-41131) have been fixed in Aspose.PDF for .NET 24.9.