I created a C# application and installed it on my test box. My app works perfect on my dev box, but when I install in on a different machine it crashes in the Main(). I get the EventType: CLR20r3
here is the Event Message
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: logfileviewer.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 4f356c9c
Problem Signature 04: LogFileViewer
Problem Signature 05: 1.0.0.0
Problem Signature 06: 4f356c9c
Problem Signature 07: 94
Problem Signature 08: 44
Problem Signature 09: System.IO.FileNotFoundException
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I used the details and looked up the error code in IL Disassembler and cam back with the following...
Method #5 (06000094)
-------------------------------------------------------
MethodName: .ctor (06000094)
Flags : [Public] [HideBySig] [ReuseSlot] [SpecialName] [RTSpecialName] [.ctor] (00001886)
RVA : 0x000081d0
ImplFlags : [IL] [Managed] (00000000)
CallCnvntn: [DEFAULT]
hasThis
ReturnType: Void
No arguments.
.NET 4.0 has been uninstalled and re installed on the system and did not change anything. I have searched all over the net and everyone with the same problem do not seem to have a solution. I have now spent a day and a half on this problem. I would hate to miss my deadline do to not being able to launch the application.
This is the only code in my Main()
static void Main()
{
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
Application.Run(new frmMain());
}
Here are the details from the Event Viewer
Application: LogFileViewer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
Stack:
at LogFileViewer.frmMain.InitializeComponent()
at LogFileViewer.frmMain..ctor()
at LogFileViewer.Program.Main()
EventData
Application: LogFileViewer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
Stack: at LogFileViewer.frmMain.InitializeComponent() at LogFileViewer.frmMain..ctor() at LogFileViewer.Program.Main()
Not sure how the designer can have a FileNotFound Exception. I am using the DotNetBar.dll and I am referencing it out of the install directory, so that should be good. I can post my designer if you want, but there is quite a bit there.
I've seen this same problem when my application depended on a referenced assembly that was not present on the deployment machine. I'm not sure what you mean by "referencing DotNetBar out of the install directory" - make sure it's set to CopyLocal=true in your project, or exists at the same full path on both your development and production machine.
I encountered the same problem when I built an application on a Windows 7 box that had previously been maintained on an XP machine.
The program ran fine when built for Debug, but failed with this error when built for Release. I found the answer on the project's Properties page. Go to the "Build" tab and try changing the Platform Target from "Any CPU" to "x86".
.NET has two CLRs 2.0 and 4.0. CLR 2.0 works till .NET framework 3.5. CLR 4.0 works from .NET 4.0 onwards. Its possible that your solution is using a different CLR than your reference assemblies. In your local development environment, you might have both the CLRs and hence you did not faced any problem. However when you moved to deployment environments, they might have a single CLR only and you got this error.
Have been fighting this all morning and now have it solved and why it happened. Posting with the hope it helps others
I installed the Krypton.Toolkit which added the tools to the Visual studio toolbox automatically. I then added the tools to the designer, which automatically added the dll to the projrect references, however the toolkit was marked as CopyLocal=false
I built an installer, using all dlls in the release build folder (of course the above dll wasn't there).
Setting copylocal=true, then rebuilding the installer, everything worked fine.
To solve CLR20r3 problem set - Local User Policy \ Computer Configuration \ Windows Settings \ Security Settings \ Local Policies \ Security Options - System cryptography: Use FIPS 140 compliant cryptographic algorithms, including encryption, hashing and signing - Disable
Related
I´m receiving the following logs from the system events. I have no idea why this only happens on some machines:
Level: Information; Source: Windows Error Reporting
Detail: 756021398 30 CLR20r3 Not available 0 DayZ Ambient Launcher.exe 1.0.0.0 59d3d3b2 System.Windows.Forms 4.7.2558.0 59d4145b 63d 36 PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
C:\Users\kevo1414\AppData\Local\Temp\WERAA52.tmp.WERInternalMetadata.xml C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DayZ Ambient Lau_4e74decfa163bcb1cc9a3fc7dd961b8b6b975b8_108bafbf
0 093ea276-bf39-11e7-b709-902b345e4b59 0
Level: Error Source: Application Error
Detail:
DayZ Ambient Launcher.exe 1.0.0.0 59d3d3b2 KERNELBASE.dll 6.1.7601.23915 59b94abb e0434352 0000c54f 1498 01d35345cae21649 C:\Users\kevo1414\Downloads\DayZ Ambient Launcher 1.1 [eXWoLL,Cobblest0ne]\DayZ Ambient Launcher.exe C:\Windows\syswow64\KERNELBASE.dll 093ea276-bf39-11e7-b709-902b345e4b59
Level: Error Source: .NET Runtime
Detail:
Application: DayZ Ambient Launcher.exe Framework Version: v4.0.30319 >Description: The process was terminated due to an unhandled exception. Exception Info: System.Runtime.InteropServices.COMException at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(System.Guid ByRef, System.Object, Int32, System.Guid ByRef) at System.Windows.Forms.AxHost.CreateWithLicense(System.String, System.Guid) at System.Windows.Forms.AxHost.CreateInstanceCore(System.Guid) at System.Windows.Forms.AxHost.CreateInstance() at System.Windows.Forms.AxHost.GetOcxCreate() at System.Windows.Forms.AxHost.TransitionUpTo(Int32) at System.Windows.Forms.AxHost.CreateHandle() at System.Windows.Forms.Control.CreateControl(Boolean) at System.Windows.Forms.Control.CreateControl(Boolean) at System.Windows.Forms.AxHost.EndInit() at dayz64.Form1.InitializeComponent() at dayz64.Form1..ctor() at dayz64.Program.Main()
There are two possible causes that I can see: operating system mismatch, or .NET installation mismatch.
Windows 7 was around right when x64 was being introduced, so there are some installations that either use x32 or x64, and going between them can result in issues if you don't install the right version of the application.
If you're going to run this application on a Windows 7 computer, then open the Start Menu, right click on Computer, and click on properties. You can see the specs of the operating system you're running from there.
The second possible issue is a .NET installation issue - maybe you have an outdated version of .NET installed, or the application relies on a legacy version of .NET and can't run on the newer frameworks, in which case you would need to look up the specifications of the product and the version you're using.
Hope this helped!
I have built an application in Visual Studio 2012 Express, on C# .NET 4.5 on Windows Server 2008R2 64 bit. When I compiled, I made sure in build properties, platform target is set to x86.
When I copy the files from Release folder to my Windows 7 32, it crashes.
Here is error my system is throwing:
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: fileupload.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 53b63c5a
Problem Signature 04: FileUpload
Problem Signature 05: 1.0.0.0
Problem Signature 06: 53b63c5a
Problem Signature 07: c
Problem Signature 08: 6
Problem Signature 09: System.IO.FileNotFoundException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
It is a file-not-found exception, could be as simple as forgetting to copy a file or not specifying the full path name.
Don't guess at this, implement a handler for the AppDomain.CurrentDomain.UnhandledException event and log or display the value of e.ExceptionObject.ToString(). It tells you where your code bombed.
I managed to find a work around for this problem. Went into References in the Solution Explorer and for each of the items, I made sure I set "Copy Local" property to True. I ended up with a lot of DLL files in the Release folder, but it ran in Windows 7.
Hy, I am trying to publish my first application. In the debugging mode everything works fine, on my computer it also works without a problem, but on the other computer I can't get it to work. When I try to run it I get the message ""application" has stopped working" . When I click on view problem details I get this:
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: robnoknjigovodstvo.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 51cac5f7
Problem Signature 04: System.Data
Problem Signature 05: 4.0.30319.17929
Problem Signature 06: 4ffa5def
Problem Signature 07: 1de2
Problem Signature 08: 5f
Problem Signature 09: System.InvalidOperationException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1050
Additional Information 1: aa76
Additional Information 2: aa76315143599a541a5fa1df4fbde453
Additional Information 3: 0709
Additional Information 4: 0709e632ea855b8ded4d7d20096b20d8
On the computer I developed the application I have 32 bit windows, and on the other one is 64bit version and I tried to change platform target but it didn't help
Check this out: Debugging "Application.exe has stopped working" with .NET.
Check if you have permissions to write or read if you are accessing the file system.
Also, make sure the other system has the adequate .NET framework installed.
Change the target to Any CPU.
Also, a good idea would be to wrap your code in a try-catch block and write the error to disk (on a location for which you have write permissions).
maybe , you did not included all dll in your project
I created a pretty simple c# application using visual studio 2010 on windows xp. It compiles, runs and debugs fine on my machine. I even built it for release and ran the .exe on my machine and another windows xp machine perfectly fine. When I send the release folder with the .exe file and they open it, nothing happens! No errors or anything, just blank!
.NET version 4 framework installed
It is a windows form application.
UPDATE: Details from OP's comments given to one of the answers below:
Hey everyone, thanks for the ideas. I
copied what I found on my friends
windows 7 machine event log and this
is what it said:
Application: ePrescribing.exe Framework Version: v4.0.30319
Description: The process was
terminated due to an unhandled
exception. Exception Info:
System.IO.FileNotFoundException Stack:
at
ePrescribing.frmApp.InitializeComponent()
at ePrescribing.frmApp..ctor() at
ePrescribing.Program.Main()
Faulting application name: ePrescribing.exe, version: 1.0.0.0,
time stamp: 0x4d61e693 Faulting module
name: KERNELBASE.dll, version:
6.1.7600.16385, time stamp: 0x4a5bdbdf Exception code: 0xe0434352 Fault
offset: 0x0000b727 Faulting process
id: 0xb38 Faulting application start
time: 0x01cbe1dbe6d4ba2d Faulting
application path:
C:\Users\Duane\Downloads\ePrescribing.exe
Faulting module path:
C:\Windows\syswow64\KERNELBASE.dll
Report Id:
266adc61-4dcf-11e0-8438-e0cb4e197cde –
Fault bucket , type 0 Event Name: CLR20r3 Response: Not available
Cab Id: 0 Problem signature: P1:
eprescribing.exe P2: 1.0.0.0 P3:
4d61e693 P4: ePrescribing P5: 1.0.0.0
P6: 4d61e693 P7: 28 P8: e P9:
System.IO.FileNotFoundException P10: –
I removed the only area where I
thought there would be a file load
(for the picturebox loading
profile.jpg) and still got the same
error. Any ideas?
First, you might try checking the Event Viewer for any relevant errors messages (as stated above).
Next, make sure they have .NET installed (as stated above).
Then, try adding an UnhandledExceptionEventHandler to your application and in that handler, try to at least write a simple log/text file containing the exception that caused your application to exit.
Make sure the latest .NET framework is installed.
Check .NET framework installed on win7 computer equal your application framework target.
Check in the process explorer that it's running but didn't show you anything.
Check event log for crash reports.
Try to add logging to your application in different places and add unhandled error handlers.
Additionly to other answers I would also check whether your app compiled against x86/x64 runtime
Have you included a manifest file?
Take a look at this.
Or this...
Are you accessing any folders via static paths instead of environment variables? That could cause issues between these versions of Windows.
You should check if all other third party assemblies can be found either in GAC or app folder
Referenced assembly may be missing from target computer. Please set Copy Local=True for all referenced library. This may solve your issue.
My WPF application works fine on a number of machines, but now I get a report about this error on a user machine:
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: mysoftware.exe
Problem Signature 02: 1.0.0.1
Problem Signature 03: 4bbcd9d9
Problem Signature 04: PresentationFramework
Problem Signature 05: 3.0.0.0
Problem Signature 06: 4a174fbc
Problem Signature 07: 624f
Problem Signature 08: e1
Problem Signature 09: System.Windows.Markup.XamlParse
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
I was trying to catch Exception using Application DispatcherUnhandledException but this didn't help. And warping Window1 constructor in try/catch block too.
.NET Framework 3.5 is installed on that machine.
How can I figure out the reason of crashing: log this error, debug, ...?
Just verify you have installed .Net Framework 3.5sp1.
The fact that there is a mention of XAML parsing would lead me to check whether the XAML is corrupt on that particular machine. The easiest way to check it is well formed is to rename it to .xml and open it with Internet Explorer. (Even if it is well formed it could still have a problem of some sort.)
If it is a ClickOnce deployed app, I would suggest clearing the local cache of the application and relaunching to see if this clears the problem up.
I think the main issue is the fact that the XAML file cannot be loaded.
That can stem from several problems:
Is the file meant to be deployed alongside the dll? Is it present
Is the client using a different UI culture than the others? Are there any satellite assemblies?
What version of the .Net framework is installed? Is it perchance a Client Profile only install?
Cheers!