An error has occurred

Aspose.Slides Product Family
1

When attempting to access any Aspose.Slides resource for a specific PPTX file stored in S3, I received an error response with “An error has occurred”. Other PPTX files stored in the same S3 bucket work fine, and I’ve verified that the file in question is not corrupt. The problem appears to be on the Aspose side.


It’s a 32MB file, that I’d prefer not to attach here. Can an Aspose support rep help me? I’m fine with sending the file via private message or email directly to a support rep.

Thanks.
2

Hi Geoff,

Please share the file with us via some third party file sharing server like dropbox and also share the sample code with us which is causing the problem at your end. We will check it and get back to you.

Thanks & Regards,

3

File:

https://knowledgetree.box.com/s/4rmvy1wuqeep0akz6cvkzh4k3qihq2lq

Code:

curl -v -k "https://api.aspose.com/v1.1/slides/REDACTED.pptx?storage=s3&folder=/REDACTED&appSID=REDACTED&signature=REDACTED"

> GET /v1.1/slides/REDACTED.pptx?storage=s3&folder=/REDACTED&appSID=REDACTED&signature=REDACTED HTTP/1.1

> User-Agent: curl/7.37.1

> Host: api.aspose.com

> Accept: */*

>

< HTTP/1.1 500 Internal Server Error

< Cache-Control: no-cache

< Content-Type: application/json; charset=utf-8

< Date: Wed, 18 Feb 2015 13:10:15 GMT

< Expires: -1

< Pragma: no-cache

< Server: Microsoft-IIS/8.0

< X-AspNet-Version: 4.0.30319

< X-Powered-By: ASP.NET

< Content-Length: 36

< Connection: keep-alive

<

{"Message":"An error has occurred."}
4

Hi Geoff,

Thank you for sharing the file.

I am checking your issue and will get back to you with the test results.

Thanks & Regards,

5

Hi Geoff,

Please accept my apology for the delayed response.

I have downloaded the presentation file shared by you on my end and have tried loading that using Aspose.Slides for .NET API to verify if there is any issue with Aspose.Slides while loading the presentation. The presentation does seem to exhibit the issue. I request you to please perform the presentation loading on your end once again to see if the issue is still prevailing or not.

We are sorry for your inconvenience,