How can I fix a Windows.NET application when starting with exception code: 0xE0434352?

Question

I created the .NET Windows Forms application in Visual Studio 2010. I also created the appropriate installation / installation package through Visual Studio 2010. It is built as a 32-bit (x86) application. (We use third-party Windows Forms controls that are only 32-bit).

I can run the installation package and successfully deploy to other 64-bit Windows environments and 7-bit and 32-bit Windows XP. The installed application works fine for them.

However, when I try to start Windows Server 2008 R2 - 64 bit, the application crashes at startup. It is successfully installed through the installer without any errors.

When the application loads, it crashes. I put the message box as the first line in the application to find out if it passed after loading. The message box is not displayed, so I assume that it occurs during application loading / initialization.

So far, I have not found much to continue. From the details, I see the following:

Exception Code: E0434352 

I fished / googled to see if there was something obvious, but I didn’t see anything. I saw some links to a possible stack overflow in

Answer 1

0xE0434352 exception code for all .NET exceptions , so you won’t talk much. How did you get this exception code? The event log?

It is best to use a debugger for more information. If the Visual Studio debugger does not help you, you may need to check out WinDbg SOS . See here and here for an introduction. Let him break the exception and see if you can get more information about the reasons.

If you suspect that this is a problem loading the assemblies, you can check the Fusion Log .

Answer 2

If you get this error from the Event Viewer, you should see another error event (at least one) from the ".NET Runtime" source. Look at this error message as it will contain Exception information.

Answer 3

A brief description for 0xE0434352 is in the blog post. Why do I keep getting the e0434352 exception code? , as well as directions for debugging through WinDbg and cdb .

Answer 4

I struggled with this all day, asking my users to run debug versions of the software. Because it looked as if the first line did not start. Just an accident without information.

Then I realized that the error was inside the InitializeComponent form.

The way to get the exception was to delete this line (or comment on it):

 System.Diagnostics.DebuggerStepThrough() 

Once you get rid of the string, you will get a normal exception.

Answer 5

I was getting this when the application was deployed. In my case, I selected "This is a full trust application" on the project security tab and fixed it.

Answer 6

This error 0xe0434352 seems to apply to a number of different errors.

In case this helps someone, I encountered this error when I tried to install the application on a new installation of Windows 10. It worked on other machines and looked like as soon as the application starts for a moment before death. After much trial and error, the problem was that the application required DirectX9. Although a later version of DirectX was present, it should have been version 9. Hope this saves someone from disappointment.

Answer 7

To fix this problem for me (since a number of applications suddenly threw this exception, for example, CorelDraw X6 was one of them), I removed the .NET 4.5 runtime and installed the .NET 4 runtime. Two versions cannot be installed next to each other different, but they use the same version numbers in the GAC . This causes problems as some of the features were discounted in 4.5.

DLL Hell is back ...

Answer 8

We proceed to this error if the connection string to our database is incorrect. The key to figuring this out was starting dotnet blah.dll, which provided stacktrace showing us that the specified instance of the SQL server was not found. Hope this helps someone.

Answer 9

So, I noticed in the event viewer that this failure corresponds to the error "System.IO.FileNotFoundException".

So, I released ProcMon and noticed that one of the DLL programs does not load vcruntime140. So I just installed reds and vs15.

Answer 10

I'm not sure if this will help anyone or not, but since it was my problem, I find it worth mentioning:

I was getting this error and it turned out to be a problem with the platform for which the EXE was created. We had this for x86, and it was supposed to be x64 due to the Oracle link in the project. When we made this change, the problem disappeared. So, see if you have similar conflicts.