.net Runtime 2.0 error due to mscorwks.dll on Windows Server 2003

Question

3.00/5 (1 vote)

See more:

I'm trying to test a c# application so I'm leaving it running as far as it can. The problem is that, radomly, it crashes without any exception on windows server 2003. When running it on windows 7, it works perfectly. No crash till now. On windows xp, it does not crash too. The only way to get a feed back is to look at the event viewer and I get the following error:

Event Type: Error
Event Source:   .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID:   1000
Date:       <date>
Time:       <date>
User:       N/A
Computer:   <machine name="">
Description:
Faulting application <application name="">, <application version="">, stamp 4ce54d0f, faulting module mscorwks.dll, version 2.0.50727.1433, stamp 471ef729, debug? 0, fault address 0x000f675b.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.</application></application></machine></date></date>

Is there anyone that encountered the problem?

Thanks in advance.

Posted 25-Nov-10 3:43am

Mehdi_S

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Not Active · Answer 1 · 2010-11-25T05:03:00

Solution 1

"The only way to get a feed back is to look at the event viewer"

This is incorrect. You wrote the code and are in complete control. There is nothing stopping you from adding instrumentation and/or logging to monitor conditions in your code. Like professionals develop software.

Also like professional software an application should handle exceptions, including UnhandledException, and not crash outright.

Posted 25-Nov-10 5:03am

Not Active

Comments

Mehdi_S 29-Nov-10 3:19am

Everything in my code is into a try/catch and I'm logging every exception ==> Nothing is written in log files.
I'm also subscribed to both "Application.ThreadException" and "AppDomain.CurrentDomain.UnhandledException" ==> No one was triggered.