ansaurus

Question

Remoting Error: Requested Service Not Found

Answer 1

A:

Questions in SO normally contain a summary of the code that poses problem, not a link to a complete project.

As you're new, I have taken a look anyway.

I could reproduce the problem, but not being a .NET remoting expert, I do not know what should be fixed in the part of the config. An internet search returns a lot of samples that use the tag for registration.

If you replace your client config by:

        <client>
            <wellknown
            type="MyRemoteObject.Greetings,MyRemoteObject"
            url="tcp://localhost:8737/ComponentHost" />
        </client>

and the server config by:

  <service>
      <wellknown
      mode="Singleton"
      type="MyRemoteObject.Greetings,MyRemoteObject"
      objectUri="ComponentHost"/>
  </service>

It works fine.

Timores 2010-03-20 11:14:20

Thanks for the reply. But this would make my instance singleton where as I wanted it to be clientActivated.I did manage to resolve the issue with hit-and-trials by modifying client app.config from:<client url="tcp://localhost:8000/ComponentHost"> to <client url="tcp://localhost:8000/">Which resolved the issue. But in all samples I have read that applicationName as mentioned in App.config of server should be appended to URL in client's app.config.I didn't get how it got fixed and eager to know the logic behind this fix.Please help in understanding this!

enableDeepak 2010-03-20 18:27:58

ansaurus

tags:

views:

answers:

Remoting Error: Requested Service Not Found

related questions