Problem with Aspose.word: System.AccessViolationException

/* Posted March 19th, 2008 at 9:22am */
/* Filed under C#, PC, PDF */
/* */

We were using aspose.PDF + aspose.wordÂ on our local dev computers and everything worked fine (windows 2k3 server 32bit)Â We then deployed to our test server Windows 2k3 64bit and the site blew up.

Description:System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.Â Â at á’‹.á‘ª.á–§(BinaryReader àµˆ)Â Â at á‘‡.á‘¢.á„‰(Stream Ùƒ, String Ø¡)Â Â at á‘‡.á‘†..ctor(Stream stream, String password, Document doc)Â Â at Aspose.Words.Document.à ¾(Stream Ùƒ, LoadFormat à ¿, String Ø¡)

Â Â at Aspose.Words.Document..ctor(Stream stream)

Well it turns out it is a known issue.Â The version of Aspose.word we where using was 5.0.2.Â Don’t let that version fool you though, as even though its newer, it wont work on the 64 OS.Â Their temporary solution right now is do downgrade your product to 5.0.0

Â http://www.aspose.com/community/files/51/file-format-components/aspose.words/entry112260.aspx

One Response to “Problem with Aspose.word: System.AccessViolationException”

Comment from romank

/* April 1, 2008 at 7:10 pm */

Aspose.Words 5.1 is now out that definitely does not have this problem.

Basically a third party obfuscation tool was at fault. It would produce some builds that would run on 64bit and some that would fail.

When we’ve released 5.0.2 we didn’t test the release on 64bit (like we did with 5.0 and now with 5.1). Now we have resolved the obfuscation problem and will also run every release on 64bit too.

This is the 5.1 release post http://www.aspose.com/community/blogs/aspose.words/archive/2008/03/28/aspose-words-5-1-0-released.aspx

Reply to this comment