Failed to render OpenOffice Impress doc

Attached OpenOffice Impressed failed to load and convert to PDF with Apose.Slides.

This is the stacktrace from our app:

[4296] [2013/01/07 16:21:21 P10C8 T005 e 7db65749-9c73-48ff-a1a0-282001b6d981:RenderWorker] The ‘Open Office Document’ document render has failed.
[4296] Exception: Not a Open Office presentation.
[4296] Type: UnsupportedFormatException
[4296] StackTrace: at ??].??]…ctor(Stream stream)
[4296] at Aspose.Slides.Pptx.PresentationEx.?(Stream stream)
[4296] at Aspose.Slides.Pptx.PresentationEx.(Stream stream)
[4296] at Aspose.Slides.Pptx.PresentationEx…ctor(Stream stream, LoadOptions loadOptions)
[4296] at Aspose.Slides.Pptx.PresentationEx…ctor(Stream stream)
[4296] at MobilePrint.Plugin.DocumentRenderer.OpenOfficeRenderer.RenderODP(String inFile, String outFile)
[4296] at MobilePrint.Plugin.DocumentRenderer.OpenOfficeRenderer.PerformRender(String inFile, String outFile, String extension, PaperSize defaultPaperSize)
[4296] Exception: Error reading “content.xml” xml part
[4296] Type: OdpReadException
[4296] StackTrace: at ??].??].(XmlDocument document, String fileName, XmlSchemaCollection schemaCollection, Boolean hideConditionalComments)
[4296] at ??].??].()
[4296] at ??].??]…ctor(Stream stream)
[4296] Exception: Input string was not in a correct format.
[4296] Type: FormatException
[4296] StackTrace: at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
[4296] at ??].??].?(??] source, String AttributeName)
[4296] at ??].??].()
[4296] at ??].??].()
[4296] at ??].??].()
[4296] at ??].??].()
[4296] at ??].[?].()
[4296] at ??].??].(XmlDocument document, String fileName, XmlSchemaCollection schemaCollection, Boolean hideConditionalComments)

Hi Peter,


I have tried accessing the presentation file shared and have been able to observe the issue specified. An issue with ID SLIDESNET-33926 has been created to further investigate and resolve the issue. This thread has been linked with the issue so that you may be automatically notified once the issue will be resolved.

We are sorry for your inconvenience,

The issues you have found earlier (filed as SLIDESNET-33926) have been fixed in this update.