"Cannot find member name System.Data.SqlClient.SqlError" when calling the remote component

[Stan]

My webserver calls a component on another server through DCOM, the component
goes to SQL, SQL raises the exception and here is what the client gets:

"Cannot find member name System.Data.SqlClient.SqlError"

I believe the issue is related to the fact that webserver runs the framework
1.1 and the component server has the framework 1.0

There are a number of posting in the different ng on this topic, but I
cannot find a resolution.

One article mentions a security channge in 1.1 and recomends to set
typefilterlevel, but it is related to Remoting, which I don't use.

The sql simply raises an exception and the exception cannot make back to the
client...

Thanks!

-Stan

 

[Kevin Yu [MSFT]]

Hi Stan,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you receive exceptions when accessing
components on a remote server. If there is any misunderstanding, please
feel free to let me know.

Generally, in this senario, we use .NET remoting. If you use DCOM, there
will be much interop in it which might hit performance and will cause many
compatibility issues. Also, using different versions of .NET framework
might cause comapatibility issues, too. So could you please also install
.NET framework 1.1 on the component server and use .NET remoting instead?

HTH.

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

 

[Stan]

Kevin,

Using .Net Remoting is simply not realistic in this scenario since it
requires the massive code changes. Secondly, why should I even do that if it
is a bug?

Will installing 1.1 framework on the server sovle the problem withought
recompiling dlls in 1.1?

The setup is this:

Server: 1.0 serviced components, 1.0 framework
Client: 1.1 framework, ASP.NET

Thanks,

-Stan

 

[Kevin Yu [MSFT]]

Hi Stan,

It depends on which version of .net framework your application is build on.
Whether it will fix the problem depends on which method throws that
exception. However, I suggest you install .net framework 1.1 to have a try.
Because .NET framework can run side by side. Installing a 1.1 version will
not affect the applications on 1.0.

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