On occasion the Remoting DataPortal fails with the above message (in the Subject).
Checking the event log it's clear that an unhandled exception has occurred somewhere in the DataPortal or the code it is running. Heres' the message.
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.2300- w3wp.exe - Common Language Runtime Debugging Services: Application has generated an exception that could not be handled.
Process id=0x15cc (5580), Thread id=0x13d4 (5076).
Click OK to terminate the application.
Click CANCEL to debug the application..
We have to restart the IIS Admin and WWW Publishing services to get the DataPortal responding again to client requests.
Now, while we are checking we've got exception handling everywhere within our code that might get executed on the portal side, has anyone else come across this problem at all? Could it be something else causing the problem?
We are IIS6, W2K3, CSLA 1.5x
In terms of clues, we did have one client trying an operation where a known bug was occurring - the ado connection was closed and then an attempt to close it again was causing an exception to be thrown and caught in our exception handling block. Maybe the IIS and/or DataPortal just freaked out as they repeatedly generated errors here? We've had this twice now over a period of 2 months so it's a rare but "stops everyone" kind of bug.
Thanks for any hints or advice.
Richard.
Copyright (c) Marimer LLC