Windows Remoting Service Periodically Crashes.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am developing a three tiered Windows Service application using remoting.
The Server portion of the program runs on a Windows Server 2k3 machine and
intermittently crashes. The event log contains the following error message
corresponding with each crash:

####################################################

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.2032- rwcarewarebusinesstier.exe - Common Language
Runtime Debugging Services: Application has generated an exception that could
not be handled.

Process id=0xac4 (2756), Thread id=0x718 (1816).

Click OK to terminate the application.

#####################################################

Any known issues that could cause this? It seemed to run without incident on
a machine with Windows 2000 server although the application has changed since
then.
 
The problem might be some where in the changed code. Try trapping the
UnhandledException event of the AppDomain and log the exception info
returned by the event. That might help you to track down if the error
is thrown by an invalid action in your code or by the runtime.
 
Thanks for the advice. I tried what you suggested but somehow the exception
is still not caught.

The application is structured like this:

The class with the main sub adds a handler for the
appdomain.currentDomain.UnhandledException Event Then configures remoting for
my remote server object.

The remote server object runs for a few hours and handles client requests
and then shuts down with only the original error message in the event log. Is
there something else I would need to do in order to catch the unhandled
exception event.

Any help would be greatly appreciated.
 
I'm having the same issue, have you found a work around for this? Does anyone
have any suggestions?
 
Back
Top