views:

309

answers:

3

Hi I have a problem with following scenario:

There is a windows service running which spawns several processes. These processes open a WCF service host over a named pipe binding. Now the parent windows service tries to ping (connect) to the child processes using the wcf proxy over the well known named pipe. This, however fails saying: "Endpoint not found"

If I run the parent process as a console application it works fine.

Any ideas? I was thinking about permissions but the child processes should inherit the permission of the service, besides they are in the same session as well.

thanks, Christoph

A: 

"Endpoint not found" could be that it cannot find the endpoint. Or it could be that it cannot find the configuration for the endpoint.

My best guess is that you are missing the client side configuration for the endpoint.

Shiraz Bhaiji
A: 

I don't have a solution, but the problem is that the service runs with elevated privileges, and therefore the client needs to be elevated too.

Jason Coyne
A: 

I am in the same situation. the same code open a named pipe and consume by client just fine if it is a console app. If I port those code to a windows service, named pipe not found.