Crystal OCX viewer crashes internet explorer crviewer.dll

[Former Member]

Hi

We have a long-established web application using Crystal Reports 8 OCX control to display reports. The software has worked fine for several years on several different environments yet on our latest deployment, when the OCX loads in the client browser, the report data is never displayed and IE simply crashes / Dr Watson.

The OCX does appear to download correctly and is referenced in the crash as currently running in IE.

We have tried to upldate to crviewer 8.5 and the same issue still occurs.

We have run database traces and the database is being called correctly and returning data.

In IIS log I can see the call to the report is returning a 200 status so it all points to a client issue.

This has been tried on clients with elevated privs so indicates that security might not be the culprit.

Different versions of IE have also been tried with no avail.

The only logging that can be found on the machine is a message in the event log:

Faulting application iexplore.exe, version 7.0.6000.16827, faulting module crviewer.dll, version 8.5.0.217, fault address 0x000339f1.

Any ideas would be appreciated as we have several people pulling hair out right now.

Thanks kgmarsch

[Former Member · Accepted solution]

Version 8.5 is pretty old, so there won't be much we can do.

You do have the original version of the crviewer.dll, so you may want to try upgrading to the service packs for it.

https://smpdl.sap-ag.de/~sapidp/012002523100006251822008E/actxviewwin_en.zip

https://smpdl.sap-ag.de/~sapidp/012002523100005986522008E/cr85devwin_en.zip

Regards,

Jonathan

[Former Member · Accepted solution]

Will give this a go now thanks.

[Former Member · Accepted solution]

Unfortunately this has not resolved the problem.

Having established the comms to the environment and running this up on clients that do work elsewhere this is still an issue so my initial hunch of this being a client problem with installation of the OCX cannot be correct.

Any ideas what else could be throwing this out?

[Former Member · Accepted solution]

Consider this closed, the OCX error was a red-herring, the issue was actually in server-side asp page.