Posts

HTTP-Activation

A recent Windows Update in regard to .Net have disabled a setting that used to be enabled per default and is required for the product suite to run properly. If you experience strange behavior probably already at initializing the product there is reason to suspect you might have received this update.

Solution is to reconfigure your system so that required feature is Enabled.

 

.Net > WCF > HTTP-Activation

This setting must be enabled.

Note that up to date single license users do not need to rectify this as systems that have Internet Information Services (IIS) installed support HTTP-Activation even if the feature is disabled.

In case your version of Windows does not show this feature in the Windows-features dialogue one can use PowerShell to check if it is enabled with a command such as the following.

Get-WindowsOptionalFeature -online -featurename *http-activation* | format-table -AutoSize

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

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.

July 2018 .NET Framework Updates

Multiple customers have reported that elMaster Design would not load correctly after installing security updates of Microsoft .NET Framework. Startup of elMaster Design would fail with an empty error dialogue. This problem and other similar problems in other software is the reason Microsoft have stopped distributing the .NET Framework July 2018 updates on Windows Update and are actively working on fixing and re-shipping this month’s updates. Further reading available at Microsoft MSDN Blog.

In future releases elMaster Design will detect this kind of problem loading resources and present a better error message.

If you experience negative behaviour Microsoft referr to the .NET Framework August 2018 Update. It resolves this advisory for all supported Windows versions.