Hi Everyone,
One of my reports is giving me grief, it was created in 13.0.2, however I've tried updating to 13.0.6 without any luck.
I'm getting the usual not responding crash that kills the service, without any exception information. This happens when generating the report via the report viewer, and separately using a call to ExportToDisk with the PDF option.
I have managed to export it to RPT format, however it kills Visual Studio if I try and preview the report. I've also tried opening it in CR XI R2 SP6 with the hope of getting a more helpful error message, but no joy.
Would anyone be able to point me in right direction for getting more information out of this crash?
It appears this is not a platform dependant issue as this is repeatable on many different machines (WinXP, Win7, 64-bit, etc.).
Just a bit more info from the Windows application log...
Faulting application name: devenv.exe, version: 10.0.40219.1, time stamp: 0x4d5f2a73
Faulting module name: craxddrt.dll, version: 13.0.6.1027, time stamp: 0x519caed7
Exception code: 0xc0000005
Fault offset: 0x00274542
Faulting process id: 0x2938
Faulting application start time: 0x01ceaa0e5126fc03
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
Faulting module path: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\craxddrt.dll
Report Id: c929753a-160a-11e3-b071-d4bed9a6f3a9
Last but not least, after a lot of time spent investigating into it further, it appears to be something data related. The underlying database within the report has an accident.location field which appears to be the source of the issue. Removing that field from the report cures the problem (this clearly isn't a solution), also reducing the amount of data within that field seems to cure it too (not a solution either). The field is a simple text string, nothing fancy.
I have attached the generated report with the embedded data (renamed to .txt).
Anyone have any ideas?!
Thanks,
Chris.