Document conversion causing IIS timeout

We’re using Aspose.Words 11.3.0.0 under .NET 3.5 to convert Word documents to PDFs for display on ASP.NET websites.

We’ve hit a problem where a 240Kb .doc file is causing IIS to timeout on a call to Aspose.Words.Document.Save(stream As System.IO.Stream, saveFormat As Aspose.Words.SaveFormat)

(It’s purely text, 30 pages, there are no images that I’m aware of.)

It contains masses of personal information (it’s a CV that’s been submitted to one of our sites) and therefore I am not particularly happy to submit it to you for examination.

Do you have any sort of privacy policy that would allow us to submit this information to you, with the knowledge that it is secure and will not be used for any other purpose than discover why Aspose.Words is failing?

EDIT:

I have downloaded the 14.1.0 DLL to test with, and that has “worked” on the document.

However, that is not a true test, as the “evaluation” mode only converts the first 5 pages and places the evaluation warning banner. There is no way of knowing if the document would work with the fully licensed version of the DLL.

Cheers,
Tom

Hi Tom,


Thanks for your inquiry. We always encourage our customers to use the latest version of Aspose.Words as it contains newly introduced features, enhancements and fixes to the issues that were reported earlier. So, I would suggest you please upgrade to the latest version of Aspose.Words for .NET (14.1.0). You can download it from the following link:
http://www.aspose.com/community/files/51/.net-components/aspose.words-for-.net/default.aspx

Also, we welcome you to evaluate the official release of Aspose.Words 14.1.0. Please read the following article for more details:

In case the problem still remains, please attach your Word document, you’re getting this problem with, here for testing. We will investigate the issue on our end and provide you more information.

Best regards,

Hi Awais,

Thanks for your response, which basically boils down to this…

"We’re not willing to fix the issue that exists in the software you have already paid us a LOT of money for.
Instead, if you want a WORKING version of the software, please pay us a LOT MORE money."

The question is, after I paid you lots more money - will the new version even work?

And will you actually answer the question I original asked, which is what you privacy policy is - as the document is a CV of a client, and therefore contains huge quantities of sensitive information.

And therefore I will definitely NOT attach it to this public forum. Can you please give me an email address that I can sent to?

Cheers,
Tom

Hi Tom,

Thanks for your inquiry. You can make this thread private by clicking on the "Make Private" button. Unfortunately, it is difficult to say what the problem is without the document. We need your document to reproduce the same problem on our end.
Please note that it is safe to attach files in the forum. If you attach your document here, only you and Aspose staff members can download it. You can also send the file to my e-mail as described here:
http://www.aspose.com/corporate/purchase/faqs/send-license-to-aspose-staff.aspx
Best regards,

Hi Tom,


Thanks for sending your document via email. I tested your .doc with licensed version of Aspose.Words for .NET 14.1.0 on my side and had successfully managed to convert all 30 pages to PDF format. So, please upgrade to the latest version.

Please let us know if we can be of any further assistance.

Best regards,

Do you actually read anything I say?

Did you test it against v11.3 to prove that there is a problem with that version of your component?

Unless you do that, how can you justify saying that we need to upgrade?

Yes, we could upgrade (FOR A LOT OF MONEY) to fix a problem that is in the software (THAT WE PAID A LOT OF MONEY FOR) to find that it still doesn’t work in our system, because of something unrelated.

Unless it’s not obvious from what I’m saying, I’m not impressed that we need to pay you money to fix a fault that is stopping our system from working correctly.




Hi Tom,


I apologize for the inconvenience. Yes, I did check with 11.3.0 version and can confirm that this was a bug in old version of Aspose.Words. Please note that this issue is no longer reproducible in latest versions e.g. 14.1.0. Please let me know if I can be of any further assistance.

Best regards,