Emailing Crystal Report in email body as HTML

Question

I'm having a problem sending emails in CR 2008 when the report is displayed as HTML in the body of the email. 
This code works in my development environment but it doesn't work in the testing environment when CR 2008 is installed using a .msi with CR merge modules:
ExportOptions crExportOptions = new ExportOptions();
crExportOptions.ExportDestinationType = ExportDestinationType.DiskFile;
crExportOptions.ExportFormatType = ExportFormatType.HTML40;
HTMLFormatOptions htmlOpts = ExportOptions.CreateHTMLFormatOptions();
htmlOpts.HTMLBaseFolderName = tempPath;
htmlOpts.HTMLFileName = fileName;
htmlOpts.HTMLEnableSeparatedPages = false;
htmlOpts.HTMLHasPageNavigator = false;
htmlOpts.UsePageRange = false;
crExportOptions.ExportFormatOptions = htmlOpts;
_reportDocument.Export(crExportOptions);
using (StreamReader r = File.OpenText(tempPath + "\\" + Path.GetFileNameWithoutExtension(_template.TemplateName) + "\\" + fileName))
     html = r.ReadToEnd();
When _reportDocument.Export(crExportOptions) is called this error is thrown:
Invalid export options.
I'm I doing something wrong with code, or do I need to do change something in my testing environment to get this to work?
Testing Environment:
Windows 2003 Server
2008 CR SP1 Merge Modules
.Net 3.5 SP1
Thanks in advance,
Dave

Answer 1

Since it works on your dev system then it is likely not a code issue. I suspect there is a runtime file difference between your dev and staging system. Use [Modules|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] to see if you can spot the difference. You'll need to run this on both systems while your app is running.
On your dev system, go through the procedure of exporting and emailing your report. Then run modules while the app is still running.
On your staging system, go through the same procedure until you get the error. Leave the error on the screen and run modules.
Finally, compare the two mdl log files using modules differences feature.