Share via


Access Denied exception while registering a remoting IpcServerChannel

I have heard from quite a few folks running into an issue where the IpcServerChannel would throw trying to initialize after a restart.

IpcServerChannel by default creates pipes in exclusive mode (no other process can listen on the same pipe name). There is a known issue with pipes -- that if there is a client side handle open to a now defunct server pipe, no further server instances are possible till a timeout cleans up the client side handles.

You can work around this issue by setting exclusiveAddressUse="false" on the server channel config. Be aware of the implications though -- any other process can start listening on the same pipe as your server. Hopefully this issue will get resolved in future releases.