Problem in Crystal Report when export to excel

[Former Member]

Dear All

I am using crystal report in my web application developed in Asp.net 2003 and sql server 2000.Report are working fine in my local PC but when I trying same thing in server then, PDF reports are working fine but excel reports are showing following Error:

"## Error in File C:\WINDOWS\TEMP\temp_b80d89a4-560d-48a4-923d-7f1d541ccf16.rpt:Error detected by export DLL: ##"

Please help me ASAP.

Thanks

With Regards

Vivek

[Former Member · Accepted solution]

Hello Vivek,

Check the existing thread:

I think your problem is the same than mine. Try the many suggestions in that thread and see if it helps. If if doesn't, comment the thread in order to make it visible that this common problem is affecting many people.

And yes, I had not got a solution until now but others in the thread were able to solve their problem.

[Former Member]

CR Gurus,

I have essentially the same error except mine occurs in a Windows forms application and the error only occurs AFTER the user installs Windows XP Service Pack 3. The error is resolved by simply rolling back service pack 3. While this is a workaround, that is not the long-term answer. Exporting to any other format (PDF, RTF) seems to work fine. Only exporting to excel is affected.

The error is exactly what is reported by users doing this on the web.

Information:

Windows Forms Applciation (framework 1.1)

Occurs when user exports CR report to excel.

Windows XP Service pack 2 computers are unaffected.

Windows XP Service pack 3 causes the error to appear.

Any help is greatly appreciated.

[former_member183750]

This is a know issue - with CR 9.1 - on WIN 2003 servers... (not sure if the solution will apply to WIN XP) But before we get to a solution, what version of CR are you using (or alternatively, what is the version of the crystaldecision.crystalreports.engine assembly?

Ludek

[Former Member]

I am using the 9.1.5000.0 version of CrystalDecisions.CrystalReports.Engine.

This may or may not be of interest. This filemon log taken while attempting to export to Excel shows the temp file being queried, deleted, and then attempt to be opened again. The result is an error.

1:52:55 PM CapitalProjects:2188 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_31de0c91-88ec-4ce7-b7e9-0b2ed55ee895.tmp SUCCESS FileAttributeTagInformation

1:52:55 PM CapitalProjects:2188 DELETE C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_31de0c91-88ec-4ce7-b7e9-0b2ed55ee895.tmp SUCCESS

1:52:55 PM CapitalProjects:2188 CLOSE C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_31de0c91-88ec-4ce7-b7e9-0b2ed55ee895.tmp SUCCESS

1:52:55 PM CapitalProjects:2188 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_31de0c91-88ec-4ce7-b7e9-0b2ed55ee895.tmp FILE NOT FOUND Attributes: Error

Could this be the source of the issue? Logs taken during an RTF export do not attempt to read the temp file after the delete.

Chris

Edited by: James Clements on Nov 7, 2008 8:53 PM

[former_member183750]

Well, I asked if the WIN2003 issue applied to XP - any SP, and apparently not to anyone's knowledge here...

Looking at the filemon log, I'm not sure that we have a problem there as the temp rpt file is read...

So, try this Service Pack:

https://smpdl.sap-ag.de/~sapidp/012002523100006007662008E/crnet11win_en.zip

Also, these are the latest msm files, so use those to distribute the runtime:

https://smpdl.sap-ag.de/~sapidp/012002523100006009302008E/cr_net_2003_mm_en.zip

Umm, I don't think you mention if this is a web or a win app. If this is a web app, try a simple win app. If the win app works, it's a permissions issue.

BTW., this note is for all that may read over this thread. While suggestions re. other possible solutions are always welcome from anyone, take these with a grain of salt if the suggested solution is for a different version of CR. Just because a lot of people have the same error with different versions of CR, does not mean that the underlying cause is the same. The trouble shooting steps always come down to basics:

Ludek

[Former Member]

Mr. Ludek,

Thanks for your response.

This is a windows forms application.

Also note in the log snippet I posted that the file is read; then the file is deleted by the export, then another attemp is made to read the file. This causes as error. No other export routine that I have tried (RTF, PDF) attempts to read the file again, after it is deleted.

All was well until the clients installed XP Service Pack 3 onto their individual machines.

Chris

[former_member183750]

Understood. However to me, the critical thing is that this is not a known issue on an XP SP 3 with CR 9.1 (certainly not if the CR 9.1 is patched). I can not duplicate the issue here on the same system.

Another question and a suggestion;

You are seeing this behavior on your development system?

Download this file:

https://smpdl.sap-ag.de/~sapidp/012002523100006252822008E/net_win_smpl.exe

The file contains a number of sample apps. Use vbnet_win_export to test the export to xls. In that way we will be using the same app, same version of CR, same OS, same version of .NET.

Ludek

[Former Member]

Mr. Ludek,

Again, thanks for your contined attention to this matter.

I have compiled and run the VB.NET examples you linked to. When attempting to export the report to excel from the Windows Forms Sample Application I receive the same error described above.

"Error in File C:\Doc...: Error detected by export DLL:

Furthermore I installed the patch which you provided a link to, and also applied crnet11win_en_sp2.exe which I found on the web. Nothing has resolved this issue.

I have taken side by side file monitor logs of the working (XP Sp2) and the broken (XP Sp3) . They are post below. You mentioned you did see any issue, but it is pretty obvious that once the file is deleted the SP 3 machine attempts to access the deleted file again. This doesn't happen in the SP 2 machine.

I apologize for the lenght of this post.

Service Pack 2 (WORKS GREAT)

8:55:24 AM CapitalProjects:2452 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_339e5ba0-5b20-4f59-a9ab-cf49fee47450.tmp SUCCESS FileInternalInformation

8:55:24 AM CapitalProjects:2452 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_339e5ba0-5b20-4f59-a9ab-cf49fee47450.tmp SUCCESS Length: 10752

8:55:24 AM CapitalProjects:2452 OPEN C:\Program Files\CITGO Petroleum Corp\Capital Projects\ SUCCESS Options: Open Directory Access: All

8:55:24 AM CapitalProjects:2452 DIRECTORY C:\Program Files\CITGO Petroleum Corp\Capital Projects\ SUCCESS FileDirectoryInformation: CapitalProjectsLoader.exe

8:55:24 AM CapitalProjects:2452 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_339e5ba0-5b20-4f59-a9ab-cf49fee47450.tmp SUCCESS Length: 10752

8:55:24 AM CapitalProjects:2452 READ C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_339e5ba0-5b20-4f59-a9ab-cf49fee47450.tmp SUCCESS Offset: 0 Length: 10752

8:55:24 AM CapitalProjects:2452 CLOSE C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_339e5ba0-5b20-4f59-a9ab-cf49fee47450.tmp SUCCESS

8:55:24 AM CapitalProjects:2452 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_339e5ba0-5b20-4f59-a9ab-cf49fee47450.tmp SUCCESS Attributes: A

8:55:24 AM CapitalProjects:2452 OPEN C:\ SUCCESS Options: Open Directory Access: All

8:55:24 AM CapitalProjects:2452 DIRECTORY C:\ SUCCESS FileBothDirectoryInformation: DOCUME~1

8:55:24 AM CapitalProjects:2452 CLOSE C:\ SUCCESS

8:55:24 AM CapitalProjects:2452 OPEN C:\DOCUME~1\ SUCCESS Options: Open Directory Access: All

8:55:24 AM CapitalProjects:2452 DIRECTORY C:\DOCUME~1\ SUCCESS FileBothDirectoryInformation: jcleme1

8:55:24 AM CapitalProjects:2452 CLOSE C:\DOCUME~1\ SUCCESS

8:55:24 AM CapitalProjects:2452 OPEN C:\DOCUME~1\jcleme1\ SUCCESS Options: Open Directory Access: All

8:55:24 AM CapitalProjects:2452 DIRECTORY C:\DOCUME_{1\jcleme1\ SUCCESS FileBothDirectoryInformation: LOCALS}1

8:55:24 AM CapitalProjects:2452 CLOSE C:\DOCUME~1\jcleme1\ SUCCESS

8:55:24 AM CapitalProjects:2452 OPEN C:\DOCUME_{1\jcleme1\LOCALS}1\ SUCCESS Options: Open Directory Access: All

8:55:24 AM CapitalProjects:2452 DIRECTORY C:\DOCUME_{1\jcleme1\LOCALS}1\ SUCCESS FileBothDirectoryInformation: Temp

8:55:24 AM CapitalProjects:2452 CLOSE C:\DOCUME_{1\jcleme1\LOCALS}1\ SUCCESS

8:55:24 AM CapitalProjects:2452 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_339e5ba0-5b20-4f59-a9ab-cf49fee47450.tmp SUCCESS Attributes: A

8:55:24 AM CapitalProjects:2452 OPEN C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_339e5ba0-5b20-4f59-a9ab-cf49fee47450.tmp SUCCESS Options: Open Access: All

8:55:24 AM CapitalProjects:2452 OPEN C:\Program Files\CITGO Petroleum Corp\Capital Projects\ SUCCESS Options: Open Directory Access: All

8:55:24 AM CapitalProjects:2452 DIRECTORY C:\Program Files\CITGO Petroleum Corp\Capital Projects\ SUCCESS FileDirectoryInformation: CapitalProjectsLoader.exe

8:55:24 AM CapitalProjects:2452 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_339e5ba0-5b20-4f59-a9ab-cf49fee47450.tmp SUCCESS FileAttributeTagInformation

8:55:24 AM CapitalProjects:2452 DELETE C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_339e5ba0-5b20-4f59-a9ab-cf49fee47450.tmp SUCCESS

8:55:24 AM CapitalProjects:2452 CLOSE C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_339e5ba0-5b20-4f59-a9ab-cf49fee47450.tmp SUCCESS

8:55:24 AM CapitalProjects:2452 CREATE C:\Documents and Settings\jcleme1\Desktop\test.xls SUCCESS Options: OverwriteIf Access: All

8:55:24 AM CapitalProjects:2452 OPEN C:\Documents and Settings\jcleme1\Desktop\ SUCCESS Options: Open Directory Access: 00000000

8:55:24 AM CapitalProjects:2452 WRITE C:\Documents and Settings\jcleme1\Desktop\test.xls SUCCESS Offset: 0 Length: 4096

Service Pack 3 (BROKEN)

8:52:18 AM CapitalProjects:5644 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_cff18f50-d27a-44b3-97aa-2bbacbb0e130.tmp SUCCESS FileBasicInformation

8:52:18 AM CapitalProjects:5644 OPEN C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_cff18f50-d27a-44b3-97aa-2bbacbb0e130.tmp SUCCESS Options: Open Access: All

8:52:18 AM CapitalProjects:5644 OPEN C:\VSSProjects\Capital Projects System\Capital Projects Solution\Capital Projects ET\Capital Projects Loader\bin\ SUCCESS Options: Open Directory Access: All

8:52:18 AM CapitalProjects:5644 DIRECTORY C:\VSSProjects\Capital Projects System\Capital Projects Solution\Capital Projects ET\Capital Projects Loader\bin\ SUCCESS FileDirectoryInformation: CapitalProjectsLoader.exe

8:52:18 AM CapitalProjects:5644 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_cff18f50-d27a-44b3-97aa-2bbacbb0e130.tmp SUCCESS FileAttributeTagInformation

*8:52:18 AM CapitalProjects:5644 DELETE C:\DOCUME~1\jcleme1\LOCALS~1\Temp\export_cff18f50-d27a-44b3-97aa-2bbacbb0e130.tmp SUCCESS *

*8:52:18 AM CapitalProjects:5644 CLOSE C:\DOCUME~1\jcleme1\LOCALS~1\Temp\export_cff18f50-d27a-44b3-97aa-2bbacbb0e130.tmp SUCCESS *

*8:52:18 AM CapitalProjects:5644 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_cff18f50-d27a-44b3-97aa-2bbacbb0e130.tmp FILE NOT FOUND Attributes: Error *8:52:18 AM CapitalProjects:5644 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp SUCCESS Attributes: D

8:52:18 AM CapitalProjects:5644 OPEN C:\ SUCCESS Options: Open Directory Access: All

8:52:18 AM CapitalProjects:5644 DIRECTORY C:\ SUCCESS FileBothDirectoryInformation: DOCUME~1

8:52:18 AM CapitalProjects:5644 CLOSE C:\ SUCCESS

8:52:18 AM CapitalProjects:5644 OPEN C:\DOCUME~1\ SUCCESS Options: Open Directory Access: All

8:52:18 AM CapitalProjects:5644 DIRECTORY C:\DOCUME~1\ SUCCESS FileBothDirectoryInformation: jcleme1

8:52:18 AM CapitalProjects:5644 CLOSE C:\DOCUME~1\ SUCCESS

8:52:18 AM CapitalProjects:5644 OPEN C:\DOCUME~1\jcleme1\ SUCCESS Options: Open Directory Access: All

8:52:18 AM CapitalProjects:5644 DIRECTORY C:\DOCUME_{1\jcleme1\ SUCCESS FileBothDirectoryInformation: LOCALS}1

8:52:18 AM CapitalProjects:5644 CLOSE C:\DOCUME~1\jcleme1\ SUCCESS

8:52:18 AM CapitalProjects:5644 OPEN C:\DOCUME_{1\jcleme1\LOCALS}1\ SUCCESS Options: Open Directory Access: All

8:52:18 AM CapitalProjects:5644 DIRECTORY C:\DOCUME_{1\jcleme1\LOCALS}1\ SUCCESS FileBothDirectoryInformation: Temp

8:52:18 AM CapitalProjects:5644 CLOSE C:\DOCUME_{1\jcleme1\LOCALS}1\ SUCCESS

8:52:18 AM CapitalProjects:5644 QUERY INFORMATION C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_cff18f50-d27a-44b3-97aa-2bbacbb0e130.tmp FILE NOT FOUND Attributes: Error

8:52:18 AM CapitalProjects:5644 OPEN C:\DOCUME_{1\jcleme1\LOCALS}1\Temp\export_cff18f50-d27a-44b3-97aa-2bbacbb0e130.tmp FILE NOT FOUND Options: Open Access: All

8:52:19 AM CapitalProjects:5644 CLOSE C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83 SUCCESS

[former_member183750]

I understand your suspicion as per the filemon logs. And I can not explain it. I do know that there are no reported issues exporting to xls on a WIN XP SP3 - other that your issue.

Something that did catch my eye:

In one of your posts you say:

I am using the 9.1.5000.0 version of CrystalDecisions.CrystalReports.Engine.

And in your last post you say:

"...also applied crnet11win_en_sp2.exe which I found on the web. "

Those two do not make sence as crnet11win_en_sp2.exe is a patch for crystal reports XI release 1. So, the question is; what is the version of the CR assembly crystaldecisins.crystalreports.engine.dll referenced in your project?

Also, what directory do the crpe32.dll and crxf_xls.dll load from?

Ludek

[Former Member]

Mr. Ludek,

The engine dll that is referenced in my application is 9.1.5000. Installing the SP was misguided and unrelated.

How can I be certain that I have the latest version of the CR libraries referenced? In Visual Studio 2003 the properties of the reference show version 9.1.5000 however the file version is shown as 9.1.9800.9 when I browse to the directory where the DLL resides.

[former_member183750]

Actually, check the version of the exportmodeller.dll. It should be 9.1.1.528 or higher.

And the crpe32.dll should be 9.1.9800.23

Ludek

Edited by: Ludek Uher on Nov 12, 2008 2:28 PM

[former_member183750]

See if this "hot fix" resolves the issue:

ftp://ftp1.businessobjects.com/outgoing/chf/crnet11win_en.zip

Ludek

[Former Member]

Mr. Ludek,

You have helped me to resolve my issue. It seems replacing the two DLLs you mentioned above with the DLLs installed as part of that update resolved my issue on all machines.

Thank you so much for sticking it out and helping me. I would mark this thread answered, but I highjacked it from another user.

Thanks again!

Chris Clements

[former_member183750]

Great news!

Good luck in your future projects,

Ludek

[Former Member]

The link for the hotfix provided does not seem to work any more, does any one have an alternative or can supply this version of the hotfix, that would be great.

[former_member183750]

This is the current link:

https://smpdl.sap-ag.de/~sapidp/012002523100006007662008E/crnet11win_en.zip

Ludek

[Former Member]

Much Appreciated.

[Former Member]

I have exactly the same problem as James but when i installed the hotfix and distributed the files as mentioned (ExportModeller.dll, crpe32.dll) to the PCs running the application i still recieved an error 'Load Report Failed'. If i just distribute the ExportModeller.dll i get the error 'Error in file 'C:\etc...' opertaion not yet implemented'. So i think the file versions i got as a result of installing the hotfix in the link above were incorrect, they are:

Previous:

ExportModeller.dll version 9.1.1.527

crpe32.dll version 9.1.2.1111

After Hotfix (tried to use these for export fix)

ExportModeller.dll version 10.0.5.667

crpe32.dll version 9.2.1.564

Do you think i am missing something or need different file versions ?

Thanks. JEff.

[Former Member]

Dude, Saw you have a problem exporpting (from a crystal report) to excel on XP SP3, but NOT XP SP2.

Did you ever find a resolution?

I have this problem in a deployed app. The only solution I can see is to roll back XP SP3, but that does not sound like a reasonable solution.

I do not understand why SAP/Crystal has not clearly documented this issue and the resolution.

Thanks,

[Former Member]

Dude, Saw you have a problem exporpting (from a crystal report) to excel on XP SP3, but NOT XP SP2.

Did you ever find a resolution?

I have this problem in a deployed app. The only solution I can see is to roll back XP SP3, but that does not sound like a reasonable solution.

I do not understand why SAP/Crystal has not clearly documented this issue and the resolution.

Thanks,

[former_member183750]

I think you'll be better off creating a new thread and also look at the [Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement]

Step 2 Asking Your Question; Provide Enough Information

E.g; provide as much info as possible. Giving the version of CR and .NET used as well as and SPs would be a good place to start.

Ludek

[Former Member]

It seems the solution to this problem was achieved in the thread:

and also on this one:

Solution: add "C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0win32_x86" to the PATH environment variable of your system.

Edited by: Paulo Nicau on Sep 16, 2008 12:48 PM

[former_member11696]

Hi all,

This is only a work around. By default Crystal uses the registry to get the location of our installed and root directories. By adding the location to the PATH statement indicates there is a permission issue on our folders.

Not sure how deep you want to investigate the problem but you can use regedt32 to check permissions on our registry keys. We don't support this part of modifying the registry so please do this ONLY on a test machine that can be discarded later. DO NOT ATTEMPT THIS ON PRODUCTION MACHINES OR CRITICAL in nature.

Thank you

Don

[Former Member]

Hi Vivek,

Try to give read permission to "C:\WINDOWS\TEMP\temp" folder for ASPNET and if machine has IIS6 than give permissions to IIS_WPG.

Hope it helps!!

Amit