soap.tcp not available to non-admin users

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Keith Patrick - 25 Jun 2004 21:08 GMT

I tried opening a channel for a non-IIS-hosted app via new SoapSender(new
Uri("soap.tcp://MyService")), but I got a security error. Things went away
when I tried running it as an admin user. Is there a way to connect two
services in a messaging connection without running as an admin?
BTW: I'm trying using an http URI as well, but I'm getting a bit hung up
exposing things in IIS (it'd love to have http.sys right about now :) ) as
well, since my app is not built as a web service (at least not at this
layer), but I haven't done a whole lot of playing around with getting that
part to work.

Reply to this Message

Lucien - 25 Jun 2004 22:21 GMT

Which OS? Except for w2k3 you need to set ExclusiveAddressUse to false if
you want to run as non-admin. In your app add this:

<messaging>
<transports>
<add scheme="soap.tcp" >
<exclusiveAddressUse enabled="false" />
</add>
</transports>
</messaging>

There's no built-in HTTP messaging support but you could create your own
transport with the WSE 2 framework.

> I tried opening a channel for a non-IIS-hosted app via new SoapSender(new
> Uri("soap.tcp://MyService")), but I got a security error. Things went away
[quoted text clipped - 5 lines]
> layer), but I haven't done a whole lot of playing around with getting that
> part to work.

Reply to this Message

Keith Patrick - 26 Jun 2004 00:19 GMT

Did the trick! Many thanks.

Reply to this Message

soap.tcp not available to non-admin users

Free Magazines