none
.Net Application Launched with Psexec crashes with exit code -1073741819 and application event log shows eventID 1023 with message CLR Fatal execution error RRS feed

  • Question

  • In a distributed environment , I am using psexec to run the application on remote system in interactive mode. the application is  a C# application compiled on .Net 3.5 , from the .Net application , calling C++ executable(nativeapp.exe compiled x86, I dont have source code) . Below is the command to run the application on remote.PsExec.exe \\xx.xx.xx.xx -u domain\user -p password -i csharpApp.exe

    Once the application starts the execution on the remote, when the call to the C++ executable the C# application exits with exit code -1073741819 (upon looking the information on exit code, found that it is related to access violation) . I am running the app on XP 64 and it is specific to XP 64.

    what is the difference in running in console and interactive ? how to fix the access violation error ? 

    The event viewer shows the error below :

    On win7 it runs properly. If the same application is run in console mode using psexec, it runs with out any issues.

    command: psexec.exe \\xx.xx.xx.xx -u domain\user -p password cmd /c csharpapp.exe ( works properly like running in console mode)

    The problem to run in console mode is, I will not be able to capture the exit code from the application hence I need to run in interactive mode to capture the exit code from the application. And also  the exception is not caught from  application, I added unhandled exception handler in the application as below but still the exception is not caught.

    AppDomain

    .CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);

    what  is the difference in running console vs interactive mode which is causing the access violation error?

    I used adplus to get a dump file for analyzing the crash and here is the stack information. it is pointing to ntdll.      

                                                                                                                                                                                                                                  # Child-SP          RetAddr           : Args to Child                                                           : Call Site
    00 00000000`0012e518 00000000`6b006866 : 00000000`002cfae4 00000000`002cfd7c 00000000`002cfe90 00000000`fffdb000 : ntdll!NtTerminateProcess+0xa
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\wow64cpu.dll -
    01 00000000`0012e520 00000000`78b83c7d : 00000000`002cfa0c 00000000`776bc28c 00000000`00000000 00000000`7d61cbf1 : wow64!Wow64SystemServiceEx+0xd6
    02 00000000`0012ede0 00000000`6b006a5a : 00000000`fffdf000 00000000`00140001 00000000`00000000 00000000`00000000 : wow64cpu!TurboDispatchJumpAddressEnd+0x28
    03 00000000`0012ee70 00000000`6b005e0d : 00000000`00000000 00000000`0012f1b0 00000000`0012fab0 00000000`00000000 : wow64!Wow64SystemServiceEx+0x2ca
    04 00000000`0012eea0 00000000`77ed7a00 : 00000000`001432f0 00000000`00000000 00000000`0012fab0 00000000`00000003 : wow64!Wow64LdrpInitialize+0x2ed
    05 00000000`0012f6d0 00000000`77ed519f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlSetBits+0x170
    06 00000000`0012f9d0 00000000`77ef2af5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!CsrCaptureMessageBuffer+0x46f
    07 00000000`0012fab0 00000000`77d59670 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!KiUserApcDispatcher+0x15 (TrapFrame @ 00000000`0012fe18)
    08 00000000`0012ffa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77d59670

    Creating c:\dumps\20130227_044916_Crash_Mode\FULLDUMP_FirstChance_epr_Process_Shut_Down_nativeapp.exe.exe__0334_2013-02-27_04-50-06-359_05e8.dmp - mini user dump

    Monday, March 18, 2013 1:22 PM

All replies

  • Cross posted here.
    Monday, March 18, 2013 2:00 PM
  • Cross posted here.

    No they are the same.

    Ghost,
    Call me ghost for short, Thanks
    To get the better answer, it should be a better question.

    Tuesday, March 19, 2013 12:01 PM
  • If interactive and console mode work as the same then why does my scenario work in console and break in Interactive?
    Tuesday, March 19, 2013 1:05 PM
  • Hi RupaS,

    I don't think the interactive and console mode is the same.

    The interactive is no user operation, but not console.

    Have a nice day.


    Ghost,
    Call me ghost for short, Thanks
    To get the better answer, it should be a better question.

    Wednesday, March 20, 2013 4:44 AM