cancel
Showing results for 
Search instead for 
Did you mean: 

ReportDocument.Close fatal

Former Member
0 Kudos

With Crystal Reports 2008, CrystalReportViewer.ReportSource = ReportClass or ReportDocument, the ReportDocument.Close method would take about 2 minutes to finish and leave the application not responding. I've found the time involved by adding log statements and running at the customer site. I dont' think the code has changed in years and runs at many customer sites. I am suspicious of a report viewer and an accounting package using Crystal on the same machine. I found a related post here:

http://www.tek-tips.com/viewthread.cfm?qid=1442691&page=14:

where uninstalling the other products "resolved" the problem. Any suggestions?

Accepted Solutions (1)

Accepted Solutions (1)

former_member183750
Active Contributor
0 Kudos

I'd be very, very suspicious that uninstalling CR 8.5 actually resolved the issue. CR 2008 has not a clue that any other version of CR would exist on that computer... E.g.; I'd call it a red herring.

In your case, before you go uninstalling all kinds of apps, I'd use the [Modules|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] utility and compare the CR dlls loading on the computer where you see the slow performance and a "normal" performance.

Also, make sure you are using SP3 runtime.

SP 3 msi:

https://smpdl.sap-ag.de/~sapidp/012002523100007123592010E/cr2008sp3_redist.zip

SP 3 msm:

https://smpdl.sap-ag.de/~sapidp/012002523100007123582010E/cr2008sp3_mm.zip

Ludek

Follow us on Twitter http://twitter.com/SAPCRNetSup

Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

0 Kudos

One issue that may be the cause is CR 8.5 was not side by side compatible. 8.5 and older CR copied crpe32.dll into the \Windows\system folder and if it's there it can cause problems with newer versions of CR. Also, having a folder called \windows\crystal can also cause issues, CR still looks in that old legacy folder for UFL's and other dependencies like database drivers so their app may be loading a legacy DB driver which can also cause delays.

Only work around is not have any app's that use 8.5 or lower version with a new version 9 or above on the same PC.

Thank you

Don

Answers (2)

Answers (2)

Former Member
0 Kudos

'presume the old software must be removed or upgraded

0 Kudos

Correct, 8.5 can not be on the same as the new software.

That dll is COM dll that needs to registered using regsvr32.exe. It should work in your app also but hard to say for sure because who knows what it is doing...

Don

Former Member
0 Kudos

Using input from both Ludek and Don, 'found that our application was loading c:\program files\aftech\reportviewer\cruflaft.dll, Version 1.01.0010 from November 2006. Being allowed to uninstall the Aftech Report Viewer our application runs fine. Can these be made to co-exist or the old Report Viewer must be upgraded?