Have you encountered this?

[byteArray]

Hi,

I would just like to ask if anybody has encounter a situation like this:

client -> ComApp1 -> ComApp2

In this case client calls ComApp1, and ComApp1 calls ComApp2.
By the way, ComApp1 and ComApp2 are COM+ library applications. ComApp2 throws an exception so ComApp1 will catch that exception and so with client.

The big problem here is that the exception that was catch in the client is different exception from the original exception that was thrown in ComApp2.

I would gladly thank anyone who could give similar instance to this.

Thanks in advance.

-byteArray

[Magiaus]

I haven't but if I could I would add a GetLastError to ComApp2 and ComApp1 and when they get an exception set the internal err. I assume it is an API error because those tend to be jumpy. I haven't done much with Com or Com+ in .net, but I know when you DllImport you can tell it that the function will SetLastError and that helps get the "RIGHT" error back to you.....

[byteArray]

Hi,

Thanks for replying and for the solution that you've presented. I really appreciate it. But the thing is what we are looking for for now is the exact situation when it occur. One of us encountered it but we cant reproduce the same instance anymore. That's why we're asking if other developers have experienced that kind of situation.

Again thanks and hopefully someone could tell us the scenario when it happen.

-byteArray