Author: JamesABCD
Subject: Result Disconnect and Result Network Error
Posted: 22 December 2017 at 11:07am
We’ve an .Net application running in an RDP Session that crashes
• sometimes with Problem Event Name: APPCRASH, Exception Code: c0000006
• sometimes with Problem Event Name: InPageError Exception Code: c000020c
The application is shut down immediately, so there’s no chance to catch an exception.
The application location is accessible via a network share.
We have investigated the crash using Process Monitor (SysInternals/ Microsoft). There’s issue while reading some other .Net dlls. The dll files involved can be read when you start the application. But after doing some certain steps they seem to be not accessible anymore and application crashes. In the protocol there are 2 suspicious types of entries that occur when trying to read other .Net dll files:
• Operation: Read File, Result: Network Error
• Operation: ReadFile, Result: Disconnected
Can anybody explain the meaning of these results?
I’d like to be sure
• if these results both are “real hard” errors and
• if they are caused by infrastructure (hardware, network, Windows etc.) or by the application itself
(For an explanation of result Network Error see here
https://forum.sysinternals.com/network-error-with-file-access_topic24186.html
)
(There is also a question for result Disconnection but unfortunately no reply.
https://forum.sysinternals.com/what-does-disconnected-mean-for-readfile_topic26880.html)
Subject: Result Disconnect and Result Network Error
Posted: 22 December 2017 at 11:07am
We’ve an .Net application running in an RDP Session that crashes
• sometimes with Problem Event Name: APPCRASH, Exception Code: c0000006
• sometimes with Problem Event Name: InPageError Exception Code: c000020c
The application is shut down immediately, so there’s no chance to catch an exception.
The application location is accessible via a network share.
We have investigated the crash using Process Monitor (SysInternals/ Microsoft). There’s issue while reading some other .Net dlls. The dll files involved can be read when you start the application. But after doing some certain steps they seem to be not accessible anymore and application crashes. In the protocol there are 2 suspicious types of entries that occur when trying to read other .Net dll files:
• Operation: Read File, Result: Network Error
• Operation: ReadFile, Result: Disconnected
Can anybody explain the meaning of these results?
I’d like to be sure
• if these results both are “real hard” errors and
• if they are caused by infrastructure (hardware, network, Windows etc.) or by the application itself
(For an explanation of result Network Error see here
https://forum.sysinternals.com/network-error-with-file-access_topic24186.html
)
(There is also a question for result Disconnection but unfortunately no reply.
https://forum.sysinternals.com/what-does-disconnected-mean-for-readfile_topic26880.html)
Dax1792 wrote: