Convert MHT to PDF fails

I am using the following code to convert MHT to PDF


private static void ConvertMhtmlDocumentToPdf(string sFileIn, string sFileOut)
{
Aspose.Pdf.MhtLoadOptions options = new Aspose.Pdf.MhtLoadOptions();

Aspose.Pdf.Document doc = new Aspose.Pdf.Document(sFileIn, options);

doc.Save(sFileOut);
}

I attached data.zip that contains the drop.mht file that I am tring to convert.

I get the following error when the bolded line is executed

System.ApplicationException was unhandled
HResult=-2146232832
Message=Absent or unexpected Content-Transfer-Encoding header’s value detected.
Source=Aspose.Pdf
StackTrace:
at . …ctor(String )
at . …ctor(String )
at . .UnpackMHT(Stream , String , Encoding )
at . . (Stream , Document , , MhtLoadOptions )
at Aspose.Pdf.Document. (Stream , LoadOptions )
at Aspose.Pdf.Document…ctor(String filename, LoadOptions options)
at ExtractingEmailHeaders.Program.ConvertMhtmlDocumentToPdf(String sFileIn, String sFileOut) in \opicko\vmshared\apps\CSharp\Program.cs:line 85
at ExtractingEmailHeaders.Program.SaveMailMessageBodyPDF(MailMessage mailMsg, String mhtFilename, String pdfFilename) in \opicko\vmshared\apps\CSharp\Program.cs:line 78
at ExtractingEmailHeaders.Program.Main(String[] args) in \opicko\vmshared\apps\CSharp\Program.cs:line 42
at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException:

Hi Thaddeus,


Thanks for contacting support.

I
have tested the scenario and I am able to reproduce the same problem. For the
sake of correction, I have logged it in our issue tracking system as PDFNEWNET-38675. We
will investigate this issue in details and will keep you updated on the status
of a correction. <o:p></o:p>

We apologize for your inconvenience.