cancel
Showing results for 
Search instead for 
Did you mean: 

Invalid export DLL or export format - Revisited

anders_gustafsson
Participant
0 Kudos

I know that there are tons of threads on this, but all archived, but I finally had the time to investigate this.

The problem is that everything works, except export to XLS. This happens when CR is installed with InstallShield (2018R2) using the CR supplied merge modules (13_0_23). It has beed this way for a long time, at least 2 years. The fix is to download the separate runtime installer and run it. Not very pretty.

The core problem is that when you install, using the MSM, it never installs the XSL export DLLs so the fis is to copy crxf_xls.dll and the needed language DLLs (crxf_xls_res_en.dll, crxf_xls_res_sv.dll...) to C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86. I will now add this kludge to our installer, but can you pretty please fix the MSM?

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi Anders,

Interesting, I looked in the MSM package using Orca and the dll is there.

Have you asked InstallShield to figure out what is missing in that version that would allow it to be installed?

Possible a flag is not set or something like that.

Can you enable install Logging and see if it generates an error when copying that file to the system?

You can send me the log file, zip it up first.

Thanks

Don

PS - for CR for VS questions post to this tag -

https://answers.sap.com/tags/01200615320800001270

Answers (1)

Answers (1)

anders_gustafsson
Participant
0 Kudos

Thanks! I wil try to remember that tag in the future. If I select the merge module and rightclick "Configure" then there are flags I can set, and yes U2FPDF is 1 while U2FXLS is 0. The defaults are indeed 1 for all so this is possibly a mistake made way back. Thanks for pointing me in the right direction.

A follow-up if I may. Since we distribute a yearly update and then QuickPatches and they rely on the original installer, then I guess we are stuck with this until next year's yearly update. I know, really a question for InstallShield, but I thought you might know.