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

Free Support Forum - aspose.com

PDF Export in C# Is Different on Development Server and Production Server

We have a solution where we generate a powerpoint which we than converts to a PDF. The PDF export looks fine on dev server but not on production server.
But it has been working on live, seems like that PDF stopped being good without any reason…
What is impacting the conversion? Why does it look different?

Thank you for contacting support.

Please check your results using the latest version of Aspose.Slides. If the issue persists, please share the following data and information:

  • presentation file
  • output PDF file
  • description of the problem
  • code example that reproduces the problem
  • OS version on which the problem occurs
  • Aspose.Slides version you used
  • any additional information about the environment on your production server

VOR 2022_test_FR_pdf.zip (888.9 KB)
VOR 2022_test_FR_pptx.zip (4.3 MB)

In the PDF, slide 25 looks very diffrently compared to pptx.
We are using Windows Server 2012 r2
We are using latest version of Apsose slides 23.1 which I published today, it seemed to work for a few hours until it reverted back to generate bad looking pdfs.
Code example:

public MemoryStream ConvertToPDF(MemoryStream m)
    License _license = new License();
    var licensePath = HttpContext.Current.Server.MapPath(ConfigurationManager.AppSettings["AsposeLicense"]);

    m.Position = 0;

    var presentation = new Aspose.Slides.Presentation(m);
    m = null;
    m = new MemoryStream();
    presentation.Save(m, Aspose.Slides.Export.SaveFormat.Pdf);

    return m;

The problem is that the PDF export looks bad, but also the same input gives different output. But mostly bad results on production server.

Thank you for the additional data and information.

We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): 
SLIDESNET-43765 (Position of tables is wrong when converting PPTX to PDF)
SLIDESNET-43766 (Chart data labels are not displayed correctly when converting PPTX to PDF)
SLIDESNET-43767 (Chart columns are not displayed correctly when converting PPTX to PDF)

You can obtain Paid Support services if you need support on a priority basis, along with the direct access to our Paid Support management team.

Please also share the version of .NET target platform in your app.

We are using .NET Framework 4.8
Just to clarify, the issue seems to come and go. Sometime it works and sometime it doesn’t, with same input.


Thank you for the information. I’ve forwarded it to our developers.

Could you clarify if you are using multithreading to convert presentations to PDF documents?

We are doing the conversion from pptx to pdf singlethreaded, but the application runs as a webserver which serve multiple users at the same time. So in theory multiple conversions can be run at the same time.
I would guess as a maximum just a few conversion for different users at the same time.

Thank you for the explanation. I’ve forwarded it to our developers.

Update, additional information: the problem was recreated on dev, as well production servers, and seems to be related to concurrent users requesting use of the component at the same time.

And if the component failed, it will continue to fail for any user after that, even though they are not concurrent. Only a restart of the web, or re publish of the code will reset the issue. Any idea what this may relate to?

Could you please share a sample project that reproduces the problem?

Hi Andrey, we’ve not been able to produce a sample code, but we’ve identified that it was still working in version 22.8, and in 22.9 the problem was introduced and is still an issue.

We simply engage the Slides component, generate results, fill objects in charts, save it to a memory stream, convert it to pdf and push it to the user. While we call the method (5 people at the same time) the charts are not aligned correctly.

Thank you for the additional information. I forwarded it to our developers.