When trying to convert a word document to PDF that is password protected, if you specify an invalid password a “GroupDocs.Conversion.Exceptions.CorruptOrDamagedFileException” is thrown.
This exception has a base exception type of “Aspose.Words.IncorrectPasswordException”
However I would expect to just see a “GroupDocs.Conversion.Exceptions.IncorrectPasswordException”
As the file is not corrupt or damaged.
Is there a reason the expected exception type is not being used?
It seems that you are encountering an issue where an incorrect password for a password-protected Word document results in a GroupDocs.Conversion.Exceptions.CorruptOrDamagedFileException being thrown, instead of the expected GroupDocs.Conversion.Exceptions.IncorrectPasswordException. This can be confusing, especially since the file is not actually corrupt or damaged.
This issue has been recognized, and there has been an investigation logged to address the exception details for password-protected file conversions. While there is no direct solution provided in the current context, it indicates that the development team is aware of the problem and is working on a fix.
For now, you may want to keep an eye on updates from the GroupDocs team regarding this issue. If you have further questions or need assistance with other aspects of document conversion, feel free to ask!
Sources:
[1]: How to convert a password protected Spreadsheet to PDF in C#
This a new and separate issue to the one linked above.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): CONVERSIONNET-7345
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
I can see the linked issue has been closed, has this been fixed? Is it due in this months release?
This issue is fixed in API version 24.12, which will be released soon. Once the release is available for download, we will notify you.
The issues you have found earlier (filed as CONVERSIONNET-7345) have been fixed in this update. This message was posted using Bugs notification tool by nikola.yankov