WCF over named pipes

2
votes

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

2
wcfwindows-servicesnamed-pipes
are all those child processes using the same named pipe? – marc_s
I ask since you say "...over the well known named pipe" - almost sounds like you're trying to use a single named pipe for several child processes – marc_s
can you show us how such a child process is created, and how it created its WCF endpoint(s)? How does the parent attempt to call the child processes? – marc_s
No, each child process opens its own named pipe. Anyway the same code works fine if I run the parent process in the console and not as a service. So the problem must have to do with the fact that I run the parent process as a windows service under "Local System Account" – Christoph

2 Answers

0
votes

"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.

0
votes

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.