Geek Answers Handbook

Why does a WCF service named pipe reject Windows client services?

On Windows 7 and .NET 4, I get very strange effects from WCF called pipe transport when my WCF client is a Windows service.

My WCF service is hosted in a user-mode application and displayed by a named pipe binding.

My WCF client is a Windows service that works as a network service (I get the same result if it works as a local system).

If my user mode application (that is, the WCF service) works as a domain administrator, then it works fine, but if the user application is a regular user (or local administrator), then the connection is rejected using CommunicationObjectFaultedException.

I saw a few questions here regarding UAC involvement, but I did not see a real solution anywhere that just makes the named pipe work properly. Is this just an irreversible structural error?

+5
source share
1 answer

From a Christian Weyer blog entry Working with OS Privilege Issues in WCF Namespace Scenarios :

If my WCF server process using a Named Pipe-based endpoint does not have privileges to create a global kernel object, it automatically fails and creates a local one that will not be visible to processes outside of its session.

, (WCF ), , - .

, , , , , IPC. MS IPC WCF, .

, , .NET .NET tray . ... , .

- IPC?

+4

More articles:


All Articles