My C# Application Is Returning 0Xe0434352 to Windows Task Scheduler But It Is Not Crashing

Is There Such A Thinig As a C# Application Link Map Or Something Equivalent?

in .Net the assemblies are self-describing. A debug database file is useful, but not necessary to describe the objects and how the code is structured. So I would not think a link map are relevant for .net assemblies.

You might want to take a look at dnSpy, this is a combined de-compiler, debugger and assembly editor. It is often useful when trying to debug errors. It is however limited to managed code, so it will probably be less useful if the error is in native code.

How do I fix a .NET windows application crashing at startup with Exception code: 0xE0434352?

0xE0434352 is the exception code for all .NET exceptions so that won't tell you much. How did you got this exception code? The event log?

Your best bet is to use a debugger to get more information. If the Visual Studio debugger won't help you, then you might need to check out WinDbg with SOS. See here and here for an introduction. Let it break on the exception, and see if you can get more information on the why.

If you suspect it is an issue when loading assemblies you might want to check out the Fusion Log.

program crashes when called by task scheduler

Thanks for the try-catch suggestion, lordkain.

The error was thrown when trying to access an external icon file. The fix was as simple as adding the appropriate file path to the "Start In:" field in task scheduler.

KERNELBASE.dll Exception 0xe0434352 offset 0x000000000000a49d

0xe0434352 is the SEH code for a CLR exception. If you don't understand what that means, stop and read A Crash Course on the Depths of Win32™ Structured Exception Handling. So your process is not handling a CLR exception. Don't shoot the messenger, KERNELBASE.DLL is just the unfortunate victim. The perpetrator is MyApp.exe.

There should be a minidump of the crash in DrWatson folders with a full stack, it will contain everything you need to root cause the issue.

I suggest you wire up, in your myapp.exe code, AppDomain.UnhandledException and Application.ThreadException, as appropriate.

Error after stopping service through Task Scheduler

Can you repeat the error when you run / stop service by hand? Can you find the line, where this happens?

Cannot read keys when either application does not have a console or when console input has been redirected from a file. Try Console.Read.

This is a wild guess, but you have Console.ReadKey() somewhere in your service.

c# console application stays on status running in task scheduler windows 2016

According to this discussion on TechNet, it may help to wrap your exe in a batch file.

In my experience however, the Task Scheduler view must be actively refreshed, for example by pressing F5. This workaround is also the solution for a similar question on SuperUser.