Question : Crystal Reports 2008 Basic Runtime on Windows 2008 x64

I have a deployment that is driving me crazy.

We use Crystal Reports and generate a report that is exported to a PDF file and renders in the user's browser. Everything works fine in development, on our staging servers. (Windows Server 2008/IIS 7, 32 bit).

The problem occurs on the new production environment. The exception:

System.Runtime.InteropServices.COMException: Not implemented.Failed to export the report.
Error in File C:\Windows\TEMP\EmergencyViewReport {53F32351-AF95-4E3F-8C53-3CA02507983D}.rpt:
Operation not yet implemented.

Stack Trace:

[COMException (0x800003e7): Not implemented.
Failed to export the report.

Error in File C:\Windows\TEMP\EmergencyViewReport {53F32351-AF95-4E3F-8C53-3CA02507983D}.rpt:
Operation not yet implemented.]
   CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.Export(ExportOptions pExportOptions, RequestContext pRequestContext) +0
   CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext) +347

[InternalException: Not implemented.
Failed to export the report.

Error in File C:\Windows\TEMP\EmergencyViewReport {53F32351-AF95-4E3F-8C53-3CA02507983D}.rpt:
Operation not yet implemented.]
   CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException(Exception e) +789
   CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext) +478
   CrystalDecisions.CrystalReports.Engine.FormatEngine.ExportToStream(ExportRequestContext reqContext) +779
   CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToStream(ExportOptions options) +142
   CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToStream(ExportFormatType formatType) +113

The CRRedist2008_x64.msi was installed.
Visual Studio 2008 was used, Any CPU compilation.

I just don't get it. Doesn't the x64 runtime work in an x64 environment?

Answer : Crystal Reports 2008 Basic Runtime on Windows 2008 x64

mlmcc...it was compiled with the AnyCPU configuration.

Actually, I just now FOUND the solution. It is so simple I cannot believe it.

I just needed to reboot the server!!!

After reviewing the error message and looking at the managed assemblies I noticed that it appeared to be a wrapper around existing (even though they are 64 bit) dlls.