My C application is returning 0xE0434352 to Windows Task Scheduler but it is not crashing

Question

I have written a few C  apps that I have running via windows task scheduler  They are running successfully  as I can see from the log files that they are writing   but windows task scheduler shows them returning a last run result of 0xE0434352  Is there something I need to do in my C  application so that it returns a success code to the windows task scheduler

User · Answer

I got the same error but I have fixed it by changing the file reading path from "ConfigFile.xml" to AppDomain.CurrentDomain.BaseDirectory.ToString() + "ConfigFile.xml"

In my case, this error due to file path error because task manager starts program from "System32" as initial path but the folder we thought.

User · Answer

Hans Passant was correct  I added a handler for AppDomain CurrentDomain UnhandledException as described here http   msdn microsoft com en-us library system appdomain unhandledexception v vs 71  aspx I was able to find the exception that was occurring and corrected it

User · Answer

In my case it was because I had message boxes  Once I commented that code out  it started working  I remembered that could be a problem when I looked at the event log as suggested in this thread  Thank you everyone

User · Answer

In case it helps others  I got this error when the service the task was running at didn t have write permission to the executable location   It was attempting to write a log file there

User · Answer

I was getting the same message message within dotNet Core 2 2 using MVC 5  however nothing was being logged to the Windows Event Viewer   I found that I had changed the Project sdk from Microsoft NET Sdk Web to Microsoft NET Sdk Razor  seen within the projects csproj file   I changed this back and it worked fine

User · Answer

I had this issue and it was due to the  Net framework version  I had upgraded the build to framework 4 0 but this seemed to affect some comms dlls the application was using  I rolled back to framework 3 5 and it worked fine

User · Answer

Another option is to simply use the Application log accessible via the Windows Event Viewer   The  Net error will be recorded to the Application log   You can see these events here   Event Viewer  Local    Windows Logs   Application

User · Answer

When setup a job in new windows you have two fields  program script  and  Start in Optional    Put program name in first and program location in second  If you will not do that and your program start not in directory with exe  it will not find files that are located in it

User · Answer

I was referencing a mapped drive and I found that the mapped drives are not always available to the user account that is running the scheduled task so I used   IPADDRESS instead of MAPDRIVELETTER  and I am up and running

User · Answer

I encountered this problem when working with COM objects  Under certain circumstances  my fault   I destroyed an external  EXE process  in a parallel thread  a variable tried to access the com interface app method and a COM-level crash occurred  Task Scheduler noticed this and shut down the app  But if you run the app in the console and don t handle the exception  the app will continue to work     Please note that if you use unmanaged code or external objects  AD  Socket  COM       you need to monitor them

User · Answer

It is permission issue in my case the task scheduler has a user which doesn t have permission on the server in which the database is present

[c#] My C# application is returning 0xE0434352 to Windows Task Scheduler but it is not crashing

Examples related to c#

Examples related to .net

Examples related to scheduled-tasks

Examples related to task