Question Re: .NET Runtime Error! on shutdown in Technology Q&A

.NET Runtime Error! on shutdown

Former Member — Tue, 18 Mar 2008 18:44:35 GMT

Post Author: Hanika

CA Forum: .NET

Hello,

I have a Windows form application that refuses to shutdown. The Windows application has a single form. The form contains a report viewer control that loads a report that uses an XML file as a datasource.

I am running VS 2005 on Vista. Just upgraded to CR2008. My test windows forms were working great. I recently upgraded to the latest patch that was available and from then on, my applications fail to close. If I enable the VS hosting environment I get a u2018Runtime Error!u2019 message. If I disable it, my program just stays open, as if in a loop on shutdown.

The Error Message reads:

Title: Microsoft Visual C++ Runtime Library

Runtime Error!

Program: u2026\TestReport.vshost.exe

This application has requested the Runtime to terminate it in an unusual way.

Please contact the applicationu2019s support team for more info.

Is this happening to anyone else?

Hanika

Re: .NET Runtime Error! on shutdown

Former Member — Wed, 19 Mar 2008 13:24:31 GMT

Post Author: MalcolmK

CA Forum: .NET

See call 3782 from torlinian 6-June-2007 11:04pm - ".NETT app not shutting down".

It's happening to me too with VS2005 on XP with CRXI rel2 (sp3).

Looks like a known problem (without a solution yet).

Re: .NET Runtime Error! on shutdown

Former Member — Wed, 19 Mar 2008 20:50:33 GMT

Post Author: Argan

CA Forum: .NET

The problem is with using the crdb_xml.dll for designing your reports (ie. during the design wizard, scrolling down and selecting XML for the connection type). This dll calls java.exe and uses it in the background. .NET can not elegantly close out the jvm and either hangs or causes this error. There is no fix for this and most likely will not be as the xml dll is a java dll. You need to use the ADO.NET (XML) selection for designing your reports (the crdb_adoplus.dll).

Re: .NET Runtime Error! on shutdown

Former Member — Thu, 20 Mar 2008 16:49:52 GMT

Post Author: MalcolmK

CA Forum: .NET

Argan, thanks for the info and advice.

Re: .NET Runtime Error! on shutdown

Former Member — Mon, 24 Mar 2008 13:54:52 GMT

Post Author: rptuser

CA Forum: .NET

The problem is with using the crdb_xml.dll for designing your reports

(ie. during the design wizard, scrolling down and selecting XML for the

connection type). This dll calls java.exe and uses it in the

background. .NET can not elegantly close out the jvm and either hangs

or causes this error. There is no fix for this and most likely will

not be as the xml dll is a java dll. You need to use the ADO.NET (XML)

selection for designing your reports (the crdb_adoplus.dll).Thanks for explaining this. One of the major problems is, Crystal Reports 2008 sample reports get this problem. It only happens if you refresh the report, not just on loading it. The Crystal Report designer doesn't get this error, so there must be a work around. Does any .Net guru know a way around this? Also, for people searching, I'll post my full error message:Application Error The exception unknown software exception (0xe06d7363) occured in the application at location...

Re: .NET Runtime Error! on shutdown

Former Member — Mon, 24 Mar 2008 18:30:19 GMT

Post Author: Argan

CA Forum: .NET

The designer is run by crw32.exe, not .NET.

There may be a work around to get it to shut down nicely, but I do not know what it would be.

Re: .NET Runtime Error! on shutdown

Former Member — Fri, 18 Apr 2008 21:53:19 GMT

Post Author: Ted Ueda

CA Forum: .NET

This issue has been given the internal tracking number ADAPT00831070, and is currently being investigated. If resolved, the tracking number will appear in a Service Pack README file.Sincerely,Ted Ueda

Re: .NET Runtime Error! on shutdown

Former Member — Mon, 30 Jun 2008 12:33:09 GMT

Ted,

Has there been any progress on this?

How do I use the tracking number to find out about updates?

Thanks.

Tim

Re: .NET Runtime Error! on shutdown

Former Member — Wed, 11 Nov 2009 18:17:56 GMT

A fix for this issue is scheduled to be released in SP 3 for CR 2008. SP 3 will release about May 2010.

Ludek