"Object reference not set" when adding net.pipe binding in IIS

Question

I have WCF service hosted locally that I want to use named pipes for. I have done this before on my work machine running Windows 7, but trying the same at home on Windows 8 I can't add the net.pipe binding - I simply get an "Object reference not set to an instance of an object" error when adding any non-http binding (other than https).

I have taken the following steps:

Enabled the "Windows Communication Foundation Non-HTTP Activation" feature in .Net Framework 3.5, and the "Named Pipe Activation" feature under .Net Framework 4.5 Advanced Services. I have had each activated on its own, and had both activated together.
Ensured that the Net.Pipe Listener Adapter service is running locally.
Added the "net.pipe" protocol to the site under Advanced Settings.
Restarted my machine, reset IIS, reset the site, recycled the application pool, rebooted the universe and everything in it.

Has anyone come across this before? Could it be a quirk of Windows 8?

Maloric · Accepted Answer · 2013-12-24 09:49:56Z

5

I managed to get the binding working using the command line but would still be interested to find out why the IIS interface didn't accomplish the same thing. The command I used was:

C:\Windows\System32\inetsrv\appcmd.exe set site "MYSITENAME" -+bindings.[protocol='net.pipe',bindingInformation='MYSITEADDRESS']

answered Dec 24, 2013 at 9:49

Maloric

5,6253 gold badges35 silver badges46 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

digitalmy · Accepted Answer · 2017-08-05 17:30:14Z

3

Actually for PS4 format was changed

appcmd set site "sitename" /bindings:"net.pipe/*"

keep in mind that this command removes the other bindings

edited Aug 5, 2017 at 17:30

answered Feb 28, 2014 at 6:12

digitalmy

313 bronze badges

2 Comments

Johann Blais Over a year ago

+1, but you should mention that this command removes the other bindings.

Amogh Natu Over a year ago

Exactly. This command replaces all other existing bindings. Had to add them all over again. Anyway, I'm still wondering why the IIS interface did not allow me to do the same thing.!

max · Accepted Answer · 2015-02-20 18:54:26Z

0

There is a minor typo in there. It should be:

C:\Windows\System32\inetsrv\appcmd.exe set site "MYSITENAME" /+bindings.[protocol='net.pipe',bindingInformation='MYSITEADDRESS']

answered Feb 20, 2015 at 18:54

max

10.6k17 gold badges98 silver badges154 bronze badges

Collectives™ on Stack Overflow

"Object reference not set" when adding net.pipe binding in IIS

3 Answers 3

Comments

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related