Problem converting a pptx to PDF on Windows Server 2003

Hello,


ich have a problem converting a pptx file to PDF on Windows Server 2003. Gets successfully converted on my Windows XP machine.
On Windows Server 2003, the resulting PDF is just blank, there is now exception. Aspose Slides 5.0.0.

I attached both files.

Microsoft .NET 4 Client Profile and Extended is installed on both machines.

I tried installing Visual Studio on Windows Server 2003 and built my code there but it didn’t solve the problem.

Here the code I use for the conversion:
PresentationEx presentation = new PresentationEx(file);
presentation.Save(file.Replace(".pptx", “.pdf”), Aspose.Slides.Export.SaveFormat.Pdf);

Any help appreciated!


Hi Stephan,



I have worked with the shared presentation and have been able to
successfully generate PDF using Aspose.Slides for .NET 5.0.0. Please
use try catch block in your code and try to regenerate PDF file. If your code throws any exception then please share that exception with us. For your kind reference, the
generated PDF is also attached.

Please
let us know if you are still facing problem.



Hello,


I have a try catch a la
try {


} catch (Exception e) {

}

around everything that is in my main method. The hole program doesn’t do anything more than converting office files into PDFs, just a few lines. When I misspell the file name of the office file, I see an exception, so I do not think that I’m missing an exception here.

It would be very kind of you to test the conversion on Windows Server 2003 like I did, because with the example pptx provided, I’m also able to generate working PDFs on my Windows XP client - but not on Windows Server 2003. I’ve done it like 10 times and it is 100% reproducible. I will set-up a second Windows Server 2003 today and test it there also.

I attached a screen shot showing the .NET related software that is installed.


I have the same problem on a second Windows Server 2003 Standard Edition Service Pack 2 System.

I cannot get it to run on Windows Server 2008 either.

Here’s what I do:

  • Install either Windows Server 2003 or Windows Server 2008 from Disc

  • Download and install the latest .net 4

from here https://www.microsoft.com/de-de/download/details.aspx?id=17718

  • Download and install the latest Acrobat Reader

  • Copy my compiled file with the necessary dll files onto the system, execute it to create a PDF from the pptx file with the two lines pasted above.

-> It only shows an empty page. The file also is smaller than on the XP system.

Any help would be greatly appreciated! Thank you

I just found out that the PDF that is created on Windows Server 2003 shows with a minor bug (missing background picture) in the Preview application on Mac OS X, while still not showing anything in Adobe Acrobat X.


Maybe somebody has experienced something like that before and knows why it happens.

Hi Stephan,

Please accept my apology for late response. I have successfully generated PDF file form shared presentation file by using Windows 7 with .NET framework 2.0, 3.5 and 4.0.

Can you please test this issue with .NET framework 3.5/2.0 and let me know if you are still facing problem? However, Please give me some time so that I can reproduce the issue at Windows Server 2003 with .NET framework 4.0.

We are sorry for your inconvenience.

Hello,


I just tested with Windows 7 and it works fine, same set up as with Windows Server 2003 and Windows Server 2008.

I will try with .NET framework 3.5 next.

Thank you very much!

It does not work on Windows Server 2008 either, when I choose 3.5 as target framework in Visual Studio and Install .NET 3.5.1 as a server role on Windows Server 2008, I’ll test on Windows 2003 now.

Hi Stephan,

Thanks for your patience.

I have successfully generated the PDF files at Windows Server 2003 Service Pack 2 System with .NET framework 3.5 and 4.0. Please find the generated files in attachment. Please elaborate your issue in detail so that we can investigate it.

Hello,


thank you for support.

I looked into the properties of your generated PDF, and it says that you’re using Aspose Slides for .NET 5.0.1.0, the version I’m using is 5.0.0.0.

To ensure that we’re testing the same thing, it would be very kind of you to test with version 5.0.0.0, or provide me with version 5.0.1.0 - because I cannot find that version in your download area.

I can offer to record a screen cast that I could try to make as short as possible, where I demonstrate that there is nothing more than a few lines of code and a fresh installed windows with the .NET framework from the link I provided - which works on Windows XP and 7.

There also are four 2003 machines not operated by me where we tried this and it didn’t work.


Hi Stephan,

Please download Aspose.Slides for .NET 5.0.1.0 and try to generate PDF with this latest version. The heading text is Aspose.Slides for .NET 5.0.0 but the DLL files are for Aspose.Slides for .NET 5.0.1.0. We are sorry for this inconvenience.

Please let me know if you face any problems after using the Aspose.Slides for .NET 5.0.1.0.

The problem remains in my test environment when I upgrade to Aspose Slides 5.0.1.0.

Hi Stephan,



Please generate the PDF file again at Windows Server 2003 and share that PDF file with us. I have noticed that the generated PDF file takes some time to open. Please open the generated PDF file and wait for at least 10 seconds and then check either PDF is blank or not.





Hello,


thank you for your reply.

I’m afraid that even after 15 minutes, the Adobe PDF reader still displays a blank page.
I attached the pdf again for you.

Thank you very much for your support!

Hi Stephan,

Please accept my apology for late response.

I have successfully generated the PDF files by using Aspose.Slides for .NET 5.0.1.0 at Windows Server 2003 Service Pack 2 System with .NET framework 3.5 and 4.0. Please use the attached solution file of Visual Studio 2010 and us feed back for further investigation.

If you still face problem then please share complete detail about platform and environment along with the code (Visual Studio solution) for necessary investigation. We are really keen to help you but need further details from your side.

We are sorry for your inconvenience.