Error inExportToDisk method for Excel (nvalid export DLL or export format)

[Former Member]

Hi,

I'm new to Crystal Reports and facing a problem with its ExportToDisk method. I'm using Crystal Reports 2008 with MS .Net v3.5 SP1. I get the below error while trying to export to a Excel file. The Datasource is a dataset. Could you please help me out?

-Stack Trace

at CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException(Exception e)

at CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)

at CrystalDecisions.CrystalReports.Engine.FormatEngine.ExportToStream(ExportRequestContext reqContext)

at CrystalDecisions.CrystalReports.Engine.FormatEngine.Export(ExportRequestContext reqContext)

at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToDisk(ExportFormatType formatType, String fileName)

-Error message

Error in File stdiface {3C162A12-5142-4F2C-8709-154FDD0843DB}.rpt:

Invalid export DLL or export format.

-Exception source

CrystalDecisions.ReportAppServer.DataSetConversion

-Error ID

InvalidExportOptions

Any help will be appreciated!

Thank You!

[former_member183750 · Accepted solution]

Can provide the code used?

Are you able to export from the CR Designer?

Are you able to export from the viewer at runtime?

Ludek

[Former Member · Accepted solution]

Hi Ludek,

I've narrowed down the problem to this.

1) I checked the value of HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Crystal Reports\Path :-

E:\program files\business objects\businessobjects enterprise 12.0\win32_x86

2)I added this value to the beginning of the Path variable in Environment variables

Both these solutions haven't helped.

Further, what I have noticed is, within my application, if I do an Excel export (or any other format) it works just fine. However, if I run a windows service, and do a export report within that, it gives the error. I guess it can't export within the Local System Account context.

Let me know your thoughts on this.

Thanks!

[Former Member · Accepted solution]

Further, our application has recently upgraded to Crystal Reports 2008, and this problem wasn't observed on any of the previous versions.

Let me summarize the findings as follows:-

1)When I install my application on a clean XP machine, (which installs Crystal Reports 2008) as a prerequisite, the window service which uses the ExportToDisk method of Crystal Report engine works without a hitch. The report is successfully generated.

2)However, if I install my application on a machine which had previous version of my application installed (which used Crystal Reports 10) it gives me a problem with the ExportToDisk method (Invalid export DLL or export format) when it's called through a windows service.

Let me know if you need any additional information.

Do help!

Thanks!

[former_member183750 · Accepted solution]

Lets take a look at what Process Monitor tells us. ProcMon is here;

http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx

Look for Access denied on files, folders and reg entries.

Ludek

[Former Member · Accepted solution]

Hi,

Adding the path at the beginning of the Path variable in environment variables helped. I guess I didn't restart the machine the last time around..I can't seem to recollect.

Anyway, what I'd really like to know is, why is the below behavior seen:-

1) When I do an export from the windows service in Local User account context (without having the path variable modified to contain E:\program files\business objects\businessobjects enterprise 12.0\win32_x86), i get this error

2)However, if I run the windows service with another account (eg. my domain User Account) it runs without any problem. (I still haven modified the path variable)

What could be the reason for this discrepancy?

I used process monitor, but I couldn't see any access denied messages.

[former_member183750 · Accepted solution]

Its probably due to User environment variables vs System environment variables

Under the local domain account (probably used to install CR runtime) your user settings probably know where to look for our runtime (environment path variable or an HKCU setting rather than HKLM). Its possible the runtime was not installed for u201CALL_USERSu201D and its only accessible to you and not the local system account.

Make sure the path is in the System Environment variables and not just the User Environment variables.

Ludek