We have a server application that occasionally reports SEHExceptions
(only in a production environment of course) when calling a third party
dll. Unfortunately, the exception doesn't seem to report anything
except that an exception has occurred. After a bit of Googling, I found
an explanation of SEHExceptions at
http://blogs.msdn.com/cbrumme/archive/2003/04/15/51332.aspx.

Unfortunately, it seems that unrecognized exceptions are literally
turned into a single SEHException that carries no information about the
original error (except, I guess, that it wasn't one of the exceptions
on some (unpublished) list).

I've used the Debugging Tools for Windows to take a full user
application dump. The call stacks in the dumps I examined contain the
address RPCRT4!rpcRaiseException+0x03c. This is in a remote procedure
call library that's part of COM.

Would anyone know of a way to determine what exception is being raised?
I assume the exception is either being reported by the remove server or
that COM is having communications problems with the remote server.

Is there a better way to troubleshoot this? It seems amazing to me that
the CLR doesn't pass any information on the original exception to the
managed code.

Thanks

Mike