Hello:

We are now finishing a multi-tier project and have experienced problems in
some of our development machines.

Our project has been divided in three Solutions:

- 1st: DLL's (Business Façade, Business Logic, Data Access and
SystemFrameworks Layers)

- 2nd: Remoting Server (almost no code, basically it exposes through
remoting all the classes in the Business Façade of the 1st solution)

- 3rd: ASP.NET Solution, with all the web forms, that interacts through
the Remoting Server with the Business Façade.

The problem appears with only a few development computers but we need it to
work on them too.

In some cases we have chosen to let certain
"System.Data.OracleClient.OracleException" to propagate throw the Business
Componentes solution to the ASP.NET solution (catching them sometimes but
finally rethrowing them).

While debugging, just before the exception goes out of the scope of the 1st
solution (Business Components), the exception is a real
"System.Data.OracleClient.OracleException", but when we try to catch it in
the general "Application_Error" event of the "global.asax.vb" file in the
ASP.NET application, the exception has ben changed and now it is a
"SerializationException" like this:

System.Runtime.Serialization.SerializationExceptio n
Error Message: Member message was not found.

Although I've found a document in the MSDN that shows how to wrap the
exceptions just before having them passed through remoting, just creating a
new exception wrapper inheriting from "ApplicationException" and adding it a
constructor like this:

// Constructor needed for serialization
// when exception propagates from a remoting server to the client.
protected
InvalidDepartmentException(System.Runtime.Serializ ation.SerializationInfo
info,
System.Runtime.Serialization.StreamingContext context) {}

....we would like not to have to do it, mainly because now it is working fine
in our Production Environment, and we only have to fix it in some development
machines.

We are still wondering why this is happening.

Meanwhile I'll tell you that our configured channel for remoting
communication is "Http binary", checked in both the remoting server and the
remoting client.



Thank you very much for help in advance.

Hi JDCL,

Thanks for posting in the MSDN newsgroup.

From your description, I understand that you're using .net remoting as the
communication mechanism between your cilent app layer( ASP.NET) and the
intermediate business layer(remoting server). However, you found that some
of your test environment will through unexpected "SerializationException"
(instead of the OracleException you expected) when the remoting server
throw out some OracleExceptions , correct?

As for this issue, since you've mentioned that it works on most deployment
servers and only occurs on some certain test environment, I think it likely
a environment specific issue. Also, based on my researching, there does
used to exist an known issue of the OracleException class, in the original
RTM (without any service pack) of .net framework 1.1, the OracleException
class has some known issue (code mistake) in its
serialization/deserialization code which may result to the "Member message
not found..." exception. However, after the service pack1 or in the .net
framework 2.0, this problem should have been fixed. Therefore, I'm
wondering whether there is any difference on the .net frameworks' version
on those different test server machines in your environment. First, are
you using .net framework 1.1 or 2.0, and if you're using .net framework 1.1
on those machines, have you checked them to see whether each of them has
applied the latest servcie pack.

Here is a knowledge base article describing how to identitfy the .net
framework's version(include service pack):

#How to determine which versions of the .NET Framework are installed and
whether service packs have been applied
http://support.microsoft.com/kb/318785/en-us

Hope this helps some. If there is anything else we can help, please feel
free to post here.

Regards,

Steven Cheng

Microsoft MSDN Online Support Lead


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Thank you very much. That solved the problem.

Now that we know why this happened and how to solve it we are happier than
before.

Although we thought we had the Service Pack 1 for the .NET Framework 1.1
installed in all of our development computers, we finally realized there were
a few of them in wich it wasn't installed (exactly the same in wich we had
the problem).

Thank you again.





"Steven Cheng[MSFT]" wrote:

Thanks for your response.

I'm also very glad that this has helped you resolve the problem.

Have a good day!

Regards,

Steven Cheng
Microsoft MSDN Online Support Lead


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)