Named Pipe Activation

Few customers have come upon that a Windows setting that used to default active have been switched off in connection with patching .NET Framework 4.7 or installing Windows updates. Communication in between our applications use netpipe and as a result the product suite will not operate properly as the support is inactivated.

If you encounter behaviour out of the ordinary after uppdating your system make certain that .NET Framework > WCF Services > Named Pipe Activation is still checked, in other words activated.

Named Pipe Activation must be Enabled

Edit: Note that this screenshot is taken from a machine with IIS installed which is why HTTP-Activation is supported despite the .Net feature is not enabled.

Edit: Same applies if .Net Framework 4.8 is installed.