Reproduced bug "Invalid export DLL or export format"

Question

Hi!
I hope this post is not against forum guidelines, as it is a new post relating to a sticky post; if it is i apologize in advance and feel free to delete this
I was able to reproduce the "Invalid export DLL or export format" bug that have been plagueing several of our customers for some time now, and posted the steps to reproduce and an example project in the sticky thread ["Invalid export DLL or export format" with Crystal Reports 2008;
However, this was over 3 weeks ago and it seems nobody noticed ...
I was just wondering if  anyone had seen it, and if you have been able to forward it to testers/developers and if there are plans to fix this bug in any future release?
- Hans Olav Jensen

Answer 1

The error only occured for those of our customers using Oracle as the database backend for our product. After further examination it seems that the "Invalid export DLL or export format" error is triggered just by having an active Oracle database connection.
I have created a small console application project that reproduces the bug.
using System.Data.Common;
namespace CrystalReportsBugRepro
    class Program
        static void Main(string[] args)
            ReportDocument reportDoc = new ReportDocument();
            DiskFileDestinationOptions diskDestOptions;
            ExportOptions exportOptions;
            if ((args.Length >= 1) && (args[0] == "/triggerBug")) {               
                DbProviderFactory factory = DbProviderFactories.GetFactory("System.Data.OracleClient");
                DbConnection connection = factory.CreateConnection();
                try
                    connection.ConnectionString = "Data Source=foo;User ID=foo;Password=foo;Persist Security Info=False;";
                    connection.Open();                   
                catch (Exception e)
                    // Ignore error, we just want the assembly to load
            reportDoc.Load("HelloWorldReport.rpt");
            diskDestOptions = ExportOptions.CreateDiskFileDestinationOptions();
            diskDestOptions.DiskFileName = "ExportedHelloWorldReport.xls";
            exportOptions = reportDoc.ExportOptions;
            exportOptions.ExportFormatType = ExportFormatType.Excel;
            exportOptions.ExportFormatOptions = ExportOptions.CreateExcelFormatOptions();
            exportOptions.ExportDestinationType = ExportDestinationType.DiskFile;
            exportOptions.ExportDestinationOptions = diskDestOptions;
            reportDoc.Export(exportOptions);
Run the above code as a console application and if the /triggerBug flag is set, the application fails when trying to export to excel, without /triggerBug it succeeds.
Link to download the project with everything you need to reproduce the bug: [http://www.mediafire.com/?sharekey=0060d2d3559e49ffaf924764f9977b1de04e75f6e8ebb871]
Edited by: Hans Olav Jensen on Oct 29, 2009 6:40 PM
Edited by: Hans Olav Jensen on Oct 29, 2009 6:45 PM