Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Winsbs 2003 - .net Runtime Errors

  • Please log in to reply
2 replies to this topic

#1 Aldark


  • Members
  • 7 posts
  • Local time:09:46 AM

Posted 06 September 2007 - 01:24 PM

For the past several days I've been getting a .NET runtime error that I cannot solve.

Source: .NET Runtime
Category: None
Type: Error
Event ID: 0

The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: .NET Runtime version 1.1.4322.2407- ourapp.exe - Common Language Runtime Debugging Services: Application has generated an exception that could not be handled.

I've read http://support.microsoft.com/kb/312216 - though it still shows.

I don't have a lot of server experience (ok - practically none) before this job.

Any thoughts?

- Scott

BC AdBot (Login to Remove)


#2 RandomUser


  • Members
  • 518 posts
  • Gender:Male
  • Local time:09:46 AM

Posted 07 September 2007 - 08:17 PM

OK I'm not an expert in this area, but you can get the information you need to resolve the issue by what you have at your fingertips.

It's possible that some program from a server or another PC is causing the issue. It could be a program on the working computer also, where you see the nonsense message. the best way to discern this problem would be to ask what software is being loaded over the network instead of the Local computer. If you can find the Source of the problem, the event log on that PC should be more in depth regarding the message.

That much you already know based up the KB Article on microsoft.com

what you mey want to due further is download process explorer from:


and note the processes running on the local machine and the remote server to determine the cause of the issue. This can be an exhaustive process unless you have strong networking know-how and in depth understanding of system internals. It doesn't hurt to know some scripting with WMI as well.

WMI = Windows Management Instrumentation

Again, if you know of some programs which operate heavily over the network, you'll want to place special attention to those areas and make certain that remote registry service is running on the remote machine.

That's all I've got b/c I'm not and internals specialist by any means. Doing it the way I mentioned is that "hard way" to do this. If I knew the easy way, I'd be making a lot more money.

#3 Aldark

  • Topic Starter

  • Members
  • 7 posts
  • Local time:09:46 AM

Posted 13 September 2007 - 08:39 AM

Thanks RandomUser... I did dig deeper and yes it was/is tedious and tiresome...

However, I believe this is my problem:

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 9/11/2007
Time: 2:08:23 PM
User: N/A
Application popup: OurApplication.exe - Common Language Runtime Debugging Services : Application has generated an exception that could not be handled.
Process id=0x12d8 (4824), Thread id=0x1d60 (7520).
Click OK to terminate the application.
Click CANCEL to debug the application

One of our web apps delivers a lot of email through SMTP to our users and those who we support. We use email templates and just fill in the necessary data from our SQL server to send out. We have an archive of all the emails being sent out and we're finding that a % of them are showing as "blank" (empty). So now I'm trying to figure out is if every time this error pops up, is it when the system is trying to send email and one or two during the send are getting whacked and the rest are getting out; or, is there something specific to these "blank" emails that is the trigger. I don't think it is the latter, because it isn't consistently one person vs another person.

It seems that this might be related to a .NET compatibility error with a recent Windows 2003 SBS security patch.

(Of course this happens when I'm trying to put together quarterly report data and getting ready for vacation!!!)

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users