Skip to Content
author's profile photo Former Member
Former Member

Runtime crash, 13.0.4.705

Hi, I'm using VS2010 on 64 bit Windows 7, but developing using the 32 bit libraries specifying CPU type x86 and targeting the .NET 3.5 runtime. Everything works fine on my PC, but I'm experiencing runtime crashes on our Windows Terminal Server 2003 machines. I've put together a very simple WinForm application to investigate matters - based on the template project but using ReportDocument. In the Windows Application event log I'm seeing: Faulting application crystalreportstest.exe, version 1.0.0.0, stamp 50114c0d, faulting module ntdll.dll, version 5.2.3790.4937, stamp 4ecbcdd1, debug? 0, fault address 0x00010968. The event source is .NET Runtime 2 Error Reporting. Some reports will display OK, but many don't and result in the application crashing (in these instances we see nothing). Initially all the reports were created in the Crystal Reports 2008 Developer, but some of the report instances may have been created by the ReportDocument.exportToDisk() method after having their data refreshed. All reports open OK in the CR2008 developer. I've zipped the project, renamed to CrystalReportsTest.txt and attached it. I've also zipped the 2 reports and attached them (temp.txt). That didn't work - I got a "The content type of this attachment is not allowed". Please let me know if there's a way I can paste these examples. When the app crashes, I noticed that files are created under the users local settings and dw20 (?) runs. For example: so61 {C1205402-6AD3-4F94-B483-A84E72FDC561}.rpt {49EFC8C4-5933-4E7D-9322-12FDABADE413}.rptConMgrCache get created (not attached here). Any help greatly appreciated. Many thanks, Darran Smith
Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Jul 26, 2012 at 03:32 PM

    Hello Darran

    How was the CR runtime deployed (also please let me know the name of the file used)

    It may be worthwhile to run Process Monitor and see what it tells you. This being Windows Terminal Server 2003 I suspect some sort of permissions may be the issue here and ProcMon logs will help.

    - Ludek

    Follow us on Twitter

    Got Enhancement ideas? Try the SAP Idea Place

    Share Your Knowledge in SCN Topic Spaces

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.