MBR IT/.NET 247 : Problem calling an VB.NET Enterprise Service component on microsoft.public.dotnet.framework.remoting

Problem calling an VB.NET Enterprise Service component

Messages

Related Types

This message was discovered on microsoft.public.dotnet.framework.remoting.
Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions.

Post a new message to this list...

Anders via .NET 247 (VIP)

Hi all,

I have a component developed in VB.NET that I have registered in COM+ and installed in the GAC.

I have another VS.NET project where I have a reference to the assembly and tries to call the methods in my registered component...but I recieve the following error message:

"This remoting proxy has no channel sink which means either the server has no reg
istered server channels that are listening, or this application has no suitable
client channel to talk to the server."

Why do I get this message and what does it really mean?

some code:

The component that I have registered looks like this:

<Transaction(TransactionOption.Supported), JustInTimeActivation(True), ObjectPooling(Enabled:=True, MinPoolSize:=2, MaxPoolSize:=10)> _
Public Class SqlHelper
Inherits ServicedComponent

<AutoCompete(True)>Public Function Echo(ByVal input As String) as String
Return input
End Function
End Class

Greatfull for any suggestions

//Anders =)

-----------------------
Posted by a user from .NET 247 (http://www.dotnet247.com/)

<Id>4NyFcXNUG0S5CK8h2BXPBw==</Id>

Reply to this message...

K. Vijay Anand

Hi

I tried working out an example on remoting for my company and some
applications are working fine. I hope this helps.

Since it is a Service Component, a lazy registration occurs. The Component
will be Registered in Com + (in the name of Remoting,. that is what i have
given as the name in the assembly info file)

(There are two types of registeration one is lazy and another one is manual.
Since the .Net itself registers there is no need for us to manual
registeration)

You have Client, Server, ShareDLL

If you want to test it out in your system itself then Run the Server
Component First (Server\bin\debug\server.exe)

Then Run the Client (Client\bin\Debug\Client.exe). It takes sometime to
Register and then displays "Hello world".

If you want to test it from different system then move the server
application to the different system and run the server.exe

Before that you need to modify the client to point to the server name
( class1.cs string url = "tcp://localhost:8675/RemoteObjectURI";) then
build and launch the exe. Now the remoting component will be created from
that server and the information is accessed.

The sample application that i sent to you is working fine. If you have any
problems please let me know.

Anyway i have big application conversion that i am doing to remoting. I will
let u know once it get successed.

If you come acorss any information on this topic please let me know.

Thanks

Vijay Anand Kannan

"Anders via .NET 247" <Click here to reveal e-mail address> wrote in message
news:Click here to reveal e-mail address...
[Original message clipped]

following error message:
[Original message clipped]

Reply to this message...

	System.EnterpriseServices.ServicedComponent
	System.EnterpriseServices.TransactionOption

MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

	Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
	Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com