Geek Answers Handbook

Getting EndpointNotFoundException using NetNamedPipeBinding in C #; The need to create a global named pipe

I am starting a Windows service to which I am sending messages through NetNamedPipeBinding. Messages are sent from a client application that is launched by a GPO. I just installed the service and client on a new server and I get the following message:

System.ServiceModel.EndpointNotFoundException: 
There was no endpoint listening at 
net.pipe://localhost/VOXAServices/VOXADefaultPipe that could accept the
message. This is often caused by an incorrect address or SOAP action.
See InnerException, if present, for more details.

There is no internal exception. If I run the client application by double-clicking the icon on the desktop, it will work without problems. I manage the code for both the Windows service and the client application, so I can change everything I need. But so far I’m quite sure that the binding, contract and address are correct (since everything works fine when it starts from the desktop). I believe that the problem should be that the client application starts from the GPO. But I can’t think of why this might cause this error.

UPDATE:

I read this on the Microsoft website:

Windows, , . .

WCF , , , . , , Windows, Windows, .

( , )

() UAC . , , , ?

# 2:

, , ( Windows) Named Pipes. , Windows , , . ( , sysinternals "Process Explorer", , ). , (, , ), (#). ?

+5
1

, WCF WCF- NetNamedPipe , , , . , Global, . , . WCF , Global kernel, Windows, SeCreateGlobalPrivilege. , , , , , .

:

  • ACL, , . , NETWORK USERS (SID S-1-5-2). WCF .

  • Vista , ( - - )

, , , , .

+3

More articles:


All Articles