|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
[App-name] has encountered a problem and needs to close. We...Hi
Under what circumstances do this dialog box apper in a .Net 2.0 application? I have never noticed this dialog box before I installed the KB924895 fix for ..Net framework 2.0. Hello Daniel,
Which behavior leads to this dialog box? Do u have the latest updates installed? DC> Under what circumstances do this dialog box apper in a .Net 2.0 DC> application? I have never noticed this dialog box before I installed DC> the KB924895 fix for .Net framework 2.0. --- WBR, Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour "The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it" (c) Michelangelo Hello Michael!
My application simply crashes and this dialog box pops up. The application crashes now and then, for no specific reson. There is no obviuos connection between some functionallity in the application and when the application crashes. What do you meen by "the latest udates"?? I have installed a KB-fix as described below. Thanks, Daniel Carlson Show quote "Michael Nemtsev" wrote: > Hello Daniel, > > Which behavior leads to this dialog box? > Do u have the latest updates installed? > > DC> Under what circumstances do this dialog box apper in a .Net 2.0 > DC> application? I have never noticed this dialog box before I installed > DC> the KB924895 fix for .Net framework 2.0. > > --- > WBR, > Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour > > "The greatest danger for most of us is not that our aim is too high and we > miss it, but that it is too low and we reach it" (c) Michelangelo > > > Hello Daniel,
DC> My application simply crashes and this dialog box pops up. The DC> application crashes now and then, for no specific reson. There is no DC> obviuos connection between some functionallity in the application DC> and when the application crashes. So, you need to find this connection. The reason is somewhere there :) Which compiled version gives u such an error? Debug or Release? I recommend to check the EvenLog for any records. BTW, try to run in debug mode in step into the code to check where this error is arised. DC> What do you meen by "the latest udates"?? I have installed a KB-fix DC> as described below. I meant that u need to install app possible updates. Do you have VS2005 SP1 installed? --- WBR, Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour "The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it" (c) Michelangelo Hello again!
Both bebug and release give this error and there is no information in the event log. The application is in fact a sequence of actions that is performed. I log this actions to a file but the error occures at diferent places all the time. Mu guess is that our friendly garbage collector is causing this error for some reson. No, I have not installed SP1 for VS2005. I can try this, but because the error occures when I am not running in VS I beleive this is not the cause. Thanks, for you reply! Regards Daniel Show quote "Michael Nemtsev" wrote: > Hello Daniel, > > DC> My application simply crashes and this dialog box pops up. The > DC> application crashes now and then, for no specific reson. There is no > DC> obviuos connection between some functionallity in the application > DC> and when the application crashes. > > So, you need to find this connection. The reason is somewhere there :) > Which compiled version gives u such an error? Debug or Release? > I recommend to check the EvenLog for any records. > BTW, try to run in debug mode in step into the code to check where this error > is arised. > > DC> What do you meen by "the latest udates"?? I have installed a KB-fix > DC> as described below. > > I meant that u need to install app possible updates. > Do you have VS2005 SP1 installed? > > --- > WBR, > Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour > > "The greatest danger for most of us is not that our aim is too high and we > miss it, but that it is too low and we reach it" (c) Michelangelo > > > Hello Daniel,
DC> Mu guess is that our friendly garbage collector is causing this DC> error for some reson. What makes you think so?! This behaviour only with single app, not the all ..net apps? --- WBR, Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour "The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it" (c) Michelangelo Hello!
I have only encountered this problem in one of my applications. The application is used every five minutes between 6 am to 11 pm and the problem only occures now and then. Sometimes it occures with an interval of e.g. 15 minutes, sometimes e.g. 1 day. This is why I think the garbage collector is the casue... Show quote "Michael Nemtsev" wrote: > Hello Daniel, > > DC> Mu guess is that our friendly garbage collector is causing this > DC> error for some reson. > > What makes you think so?! This behaviour only with single app, not the all > ..net apps? > > --- > WBR, > Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour > > "The greatest danger for most of us is not that our aim is too high and we > miss it, but that it is too low and we reach it" (c) Michelangelo > > > > Daniel,
This is at least the 2nd time you've asked this question - someone tried helping you the last time you asked and you've not bothered to reply to them. Basically I'd say that something in your code (again, I'm guessing that this is a program that you've written) is doing something unexpected and quitting. You need to run the program in the debugger and find out where, at which point people will be able to help you further. Regards, - Paul. Show quote "Daniel Carlson" <DanielCarl***@discussions.microsoft.com> wrote in message news:07047B6A-B0E7-4949-AE42-7284B6132BA8@microsoft.com... > Hi > > Under what circumstances do this dialog box apper in a .Net 2.0 > application? > I have never noticed this dialog box before I installed the KB924895 fix > for > .Net framework 2.0. Hello Paul!
You are right, this is the 2:nd time I ask this question. I am working on the reply i got then, so I have not yet answered to that, I am sorry for that. However this dialog box must be shown for a specific reson, and as I have got it one reson could be an access violation or something like that. What I wanted with this thread is to try to figure out more possible resons, and when this dialog box was introduced. Regards Daniel Carlson Show quote "Paul Hadfield" wrote: > Daniel, > > This is at least the 2nd time you've asked this question - someone tried > helping you the last time you asked and you've not bothered to reply to > them. Basically I'd say that something in your code (again, I'm guessing > that this is a program that you've written) is doing something unexpected > and quitting. You need to run the program in the debugger and find out > where, at which point people will be able to help you further. > > Regards, > > - Paul. > > "Daniel Carlson" <DanielCarl***@discussions.microsoft.com> wrote in message > news:07047B6A-B0E7-4949-AE42-7284B6132BA8@microsoft.com... > > Hi > > > > Under what circumstances do this dialog box apper in a .Net 2.0 > > application? > > I have never noticed this dialog box before I installed the KB924895 fix > > for > > .Net framework 2.0. > > > What does the debugger say?
It's very easy to crach an application - .Net or no .Net. Here's how: int divisor = 0; int result = 5 / divisor; Voila, it'll crash. Ashot Show quote "Daniel Carlson" <DanielCarl***@discussions.microsoft.com> wrote in message news:07047B6A-B0E7-4949-AE42-7284B6132BA8@microsoft.com... > Hi > > Under what circumstances do this dialog box apper in a .Net 2.0 > application? > I have never noticed this dialog box before I installed the KB924895 fix > for > .Net framework 2.0. Hello Ashot
Please se my reply to Chris Mullins below Regards Daniel Show quote "Ashot Geodakov" wrote: > What does the debugger say? > > It's very easy to crach an application - .Net or no .Net. > > Here's how: > > int divisor = 0; > > int result = 5 / divisor; > > > Voila, it'll crash. > > Ashot > > "Daniel Carlson" <DanielCarl***@discussions.microsoft.com> wrote in message > news:07047B6A-B0E7-4949-AE42-7284B6132BA8@microsoft.com... > > Hi > > > > Under what circumstances do this dialog box apper in a .Net 2.0 > > application? > > I have never noticed this dialog box before I installed the KB924895 fix > > for > > .Net framework 2.0. > > > "Daniel Carlson" <DanielCarl***@discussions.microsoft.com> wrote This typically means you've got an unhandled exception. It's meant that > Under what circumstances do this dialog box apper in a .Net 2.0 > application? > I have never noticed this dialog box before I installed the KB924895 fix > for > .Net framework 2.0. since the earliest days of .Net development. Put an event on the AppDomain.UnhandledException and see if it hits. Alternativly, attach a debugger and see the exception. This is actually the behavior you WANT to have happen, so that you can track things down.
Show quote
"Chris Mullins [MVP]" wrote: Hello Chris!> "Daniel Carlson" <DanielCarl***@discussions.microsoft.com> wrote > > Under what circumstances do this dialog box apper in a .Net 2.0 > > application? > > I have never noticed this dialog box before I installed the KB924895 fix > > for > > .Net framework 2.0. > > This typically means you've got an unhandled exception. It's meant that > since the earliest days of .Net development. > > Put an event on the AppDomain.UnhandledException and see if it hits. > Alternativly, attach a debugger and see the exception. > > This is actually the behavior you WANT to have happen, so that you can track > things down. > I have an event handler connected to AppDomain.UnhandledException but this is never trigged. Is this a guarantee that no unhandled exception is thrown? Another thing: I have built two diferent test applications, one in Fw1.1 and one in Fw2.0, that throws an unhandled exception. the one bulit in 1.1 does only show a dialog saying: "An unhandled exception has occ..." and the one bulit in 2.0 generates the dialog this thread is all about. The difference between the dialog that my test application generates is that this one has generated an "error report". Mine does not...! Thanks for you reply! Regards Daniel Carlson Finally I have recieved some data in the Event Viewer!!! Everytime the
application crashes the following two items appears in the Application Log: Source: .Net Runtime Time: 17:35:47 Type: .NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A05E2B3) (80131506) Source: .Net Runtime 2.0 Error Reporting Time: 1735:49 Type: Faulting application mec.exe, version 2.0.0.21154, stamp 455c4134, faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333e7ec, debug? 0, fault address 0x000a163b. (Where Mec.exe is my application) I hope anyone can help me further. Regards Daniel Carlson That's not the exception you wanted to see.
Along with "Out of Memory", "Thread Abort" and "Stack Overflow" exceptions, that's one that you really can't do much about. I would suggest using ADPlus to capture the exception, and then poke at the resulting dump file. That should tell you quite a bit more about what's going on. Information on how to do (most) of this can be found at: http://www.coversant.net/Default.aspx?tabid=88&EntryID=28 I added the "debugging" group to this post, as that's where it's going to end up. Show quote "Daniel Carlson" <DanielCarl***@discussions.microsoft.com> wrote in message news:AB23BBE7-934A-4673-9A38-E14098358D18@microsoft.com... > Finally I have recieved some data in the Event Viewer!!! Everytime the > application crashes the following two items appears in the Application > Log: > > Source: .Net Runtime > Time: 17:35:47 > Type: .NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error > (7A05E2B3) (80131506) > > Source: .Net Runtime 2.0 Error Reporting > Time: 1735:49 > Type: Faulting application mec.exe, version 2.0.0.21154, stamp 455c4134, > faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333e7ec, debug? > 0, > fault address 0x000a163b. > > (Where Mec.exe is my application) > > I hope anyone can help me further. > > Regards Daniel Carlson > > That's not the exception you wanted to see.
Along with "Out of Memory", "Thread Abort" and "Stack Overflow" exceptions, that's one that you really can't do much about. I would suggest using ADPlus to capture the exception, and then poke at the resulting dump file. That should tell you quite a bit more about what's going on. Information on how to do (most) of this can be found at: http://www.coversant.net/Default.aspx?tabid=88&EntryID=28 I added the "debugging" group to this post, as that's where it's going to end up. Show quote "Daniel Carlson" <DanielCarl***@discussions.microsoft.com> wrote in message news:AB23BBE7-934A-4673-9A38-E14098358D18@microsoft.com... > Finally I have recieved some data in the Event Viewer!!! Everytime the > application crashes the following two items appears in the Application > Log: > > Source: .Net Runtime > Time: 17:35:47 > Type: .NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error > (7A05E2B3) (80131506) > > Source: .Net Runtime 2.0 Error Reporting > Time: 1735:49 > Type: Faulting application mec.exe, version 2.0.0.21154, stamp 455c4134, > faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333e7ec, debug? > 0, > fault address 0x000a163b. > > (Where Mec.exe is my application) > > I hope anyone can help me further. > > Regards Daniel Carlson > > I know that this is not the exception I weanted to see :-/ Howerver this is
the cause of my problems, like it or not... My theory is as follows: The event viewer tells us that "faulting module" is mscorwks.dll. The KB924895 fix I have installed that handles the issue of "applications that unexpectedly quits" includes a newer version or this file. Therefor I think that the cause of my problem was a bug in that file!?!? Since I installed this fix, I have not got one single crash! Also, I used ADPlus without any positive result, no exceptions was thrown at that time. Thanks for the advise though. Regards, Daniel Carlson Show quote "Chris Mullins [MVP]" wrote: > That's not the exception you wanted to see. > > Along with "Out of Memory", "Thread Abort" and "Stack Overflow" exceptions, > that's one that you really can't do much about. > > I would suggest using ADPlus to capture the exception, and then poke at the > resulting dump file. That should tell you quite a bit more about what's > going on. Information on how to do (most) of this can be found at: > http://www.coversant.net/Default.aspx?tabid=88&EntryID=28 > > I added the "debugging" group to this post, as that's where it's going to > end up. > > -- > Chris Mullins, MCSD.NET, MCPD:Enterprise, MVP C# > http://www.coversant.net/blogs/cmullins > > "Daniel Carlson" <DanielCarl***@discussions.microsoft.com> wrote in message > news:AB23BBE7-934A-4673-9A38-E14098358D18@microsoft.com... > > Finally I have recieved some data in the Event Viewer!!! Everytime the > > application crashes the following two items appears in the Application > > Log: > > > > Source: .Net Runtime > > Time: 17:35:47 > > Type: .NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error > > (7A05E2B3) (80131506) > > > > Source: .Net Runtime 2.0 Error Reporting > > Time: 1735:49 > > Type: Faulting application mec.exe, version 2.0.0.21154, stamp 455c4134, > > faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333e7ec, debug? > > 0, > > fault address 0x000a163b. > > > > (Where Mec.exe is my application) > > > > I hope anyone can help me further. > > > > Regards Daniel Carlson > > > > > > > I know that this is not the exception I weanted to see :-/ Howerver this is
the cause of my problems, like it or not... My theory is as follows: The event viewer tells us that "faulting module" is mscorwks.dll. The KB924895 fix I have installed that handles the issue of "applications that unexpectedly quits" includes a newer version or this file. Therefor I think that the cause of my problem was a bug in that file!?!? Since I installed this fix, I have not got one single crash! Also, I used ADPlus without any positive result, no exceptions was thrown at that time. Thanks for the advise though. Regards, Daniel Carlson Show quote "Chris Mullins [MVP]" wrote: > That's not the exception you wanted to see. > > Along with "Out of Memory", "Thread Abort" and "Stack Overflow" exceptions, > that's one that you really can't do much about. > > I would suggest using ADPlus to capture the exception, and then poke at the > resulting dump file. That should tell you quite a bit more about what's > going on. Information on how to do (most) of this can be found at: > http://www.coversant.net/Default.aspx?tabid=88&EntryID=28 > > I added the "debugging" group to this post, as that's where it's going to > end up. > > -- > Chris Mullins, MCSD.NET, MCPD:Enterprise, MVP C# > http://www.coversant.net/blogs/cmullins > > "Daniel Carlson" <DanielCarl***@discussions.microsoft.com> wrote in message > news:AB23BBE7-934A-4673-9A38-E14098358D18@microsoft.com... > > Finally I have recieved some data in the Event Viewer!!! Everytime the > > application crashes the following two items appears in the Application > > Log: > > > > Source: .Net Runtime > > Time: 17:35:47 > > Type: .NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error > > (7A05E2B3) (80131506) > > > > Source: .Net Runtime 2.0 Error Reporting > > Time: 1735:49 > > Type: Faulting application mec.exe, version 2.0.0.21154, stamp 455c4134, > > faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333e7ec, debug? > > 0, > > fault address 0x000a163b. > > > > (Where Mec.exe is my application) > > > > I hope anyone can help me further. > > > > Regards Daniel Carlson > > > > > > >  |
|||||||||||||||||||||||
Other interesting topics