.msg to pdf conversion issue - incompatible unit types

GroupDocs.Conversion Product Family
1

Hello,

I am experiencing the below error when trying to convert a specific .msg file to PDF. The issue is present version 25.8

Incompatible unit types.

I can send the sample file but due to it’s nature I can’t upload it to a public open forum. Please can you provide me with an e-mail address or something to send the file.

Thanks

2

@rthomas95

It appears you are encountering an “incompatible unit types” error while converting a .msg file to PDF using GroupDocs.Conversion. This issue can occur due to various factors, including unsupported content or formatting within the .msg file.

Here are some steps you can take to troubleshoot the issue:

  1. File Integrity: Verify that the .msg file is not corrupted by opening it in Outlook and checking its contents.
  2. Update Library: Ensure you are using the latest version of the GroupDocs.Conversion library, as updates may resolve bugs and enhance compatibility.
  3. Simplify Content: If feasible, simplify the content of the .msg file by removing complex formatting or attachments, and then attempt the conversion again.

If the issue persists after trying these steps, consider seeking assistance from the GroupDocs support forum for more specific guidance.

3
  1. The file opens correctly in Outlook.
  2. Issues exists in both 25.6 and 25.8 (latest)
  3. I have been able to get a successful conversion by doing this, but this is not a long-term solution as my users pull these documents from third party document stores.
4

Hello @rthomas95 ,

We are sorry to hear that you have encountered this issue. Please send your file to evgen.efimov@aspose.com and include a sample of the conversion code you used to help speed up our investigation. We will await your details.

5

Thank you. I have emailed the details requested.

6

@rthomas95 ,

Yes, we received your email and were able to reproduce this issue on our side. We have logged it in our tracking system under the ID CONVERSIONNET-7977. As soon as the bug is fixed and included in a release, we will notify you immediately.

Note: In the meantime, we’d like to suggest a small workaround until this issue is resolved. If you try loading the .eml document not through EmailLoadOptions but through WordProcessingLoadOptions, you should be able to obtain the result in .pdf. Unfortunately, the existing properties of WordProcessingLoadOptions differ from EmailLoadOptions, and the property you are using (PreserveOriginalDate) is not available. However, even without it, we were able to get a decent result after conversion.

      public static LoadOptions GetLoadOptions(LoadContext context)
        {
            var loadOptions = new WordProcessingLoadOptions()
            {
                ConvertOwned = false
            };
            return loadOptions;
        }

Could you please also try this on your side and share your feedback? On our side, we will do our best to fix the original issue as quickly as possible.