We are trying to use the .msi you provided to install Crystal Reports XI runtime files on the Windows XP machines, but in testing this, we have run into a problem: at runtime, the Crystal Reports XI export function crashes our Visual Basic 6 program when running on an XP machine.
Windows XP, Crystal 9- viewing ok, export ok
Windows XP, Crystal XI- viewing ok, export crashes program (at runtime only)
Windows 7, Crystal 9- viewing ok export ok
Windows 7, Crystal XI- viewing ok, export ok
Is there a problem with the export function when running the Crystal 9 runtime side-by-side with the Crystal XI runtime?
Aloha,
Without knowing exactly what the error message or the conditions of the crash, I could only guess (and it would not be a good one) .
What exactly happened on XP to make it crash? Since it works on Windows 7; I assume that it has something to do with a registered dll that may not be the one expected.
In XP, the report viewer displays the report just fine. When I click the Export button, the Export dialog box never appears, and after a few seconds the VB6 application ends with no error message at all.
There is one way to track down just what the issue is. If you are familiar with Process Monitor by System Internals (Now owned by Microsoft), you can run this program and filter out any unwanted tracking aside from the vb6.exe and run your program until it gets to the place where it crashes then clear the capture screen then press the button to export.
Process Monitor will show all the registry and dlls the vb6.exe program access. You can then stop capturing and then see what vb6 was attempting to do when your app crashed.
This should narrow down the location to look to remedy the problem. My guess is that your program is accessing a non 32bit dll or an old dll in XP. I am assuming that your Windows 7 is 64bit.
Thanks- I'll try that.
I downloaded Process Monitor and ran it per your instructions- great suggestion! I'm attaching .csv files of one bad run (where the export box never appeared and our program crashed) and one good run - the ONLY good run, where it still crashed our program, but not until after the export selection box appeared and we selected some options.
There were other bad runs that crashed in the same place, just after line 2304 where it does a ReadFile on C:\Program Files\Business Objects\Common\3.5\bin\crxf_pdf.dll. Is this dll the problem? The following link has a fix for an access violation error caused by that dll, but it's not mentioning Crystal XI: http://support.cyriouswiki.com/Access Violation in module crxf_pdf.dll when exporting to PDF (http://support.cyriouswiki.com/Access%20Violation%20in%20module%20crxf_pdf.dll%20when%20exporting%20to%20PDF)
Thanks for your help on this!
Yes, it seems that the crxf_pdf.dll is the problem of the crash. The document you referenced refers to CR 8.5 and you are using CR9 which does have some of the same dlls. Check the version, if 32bit and sizes of the one that worked with the one that did not. That is a great starting place, then apply the update from the reference you sent then see if that solves the problem. If so then you will need to apply this fix to your installation.
NOTE: the export function dlls may not have changed from 8.5 to CR XI...