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.

Försläpp av Windows

Via Windows Update och även direkt från Start finns en lättillgänglig möjlighet att klicka på Check for updates men man bör vara restriktiv med att göra det. Ska man göra det bör det först ha utvärderats i en testmiljö. På Windows Blogs skriver Microsoft om hur de hanterar uppdateringar och varför att klicka på Check for updates i praktiken motsvarar testning.

Att aktivt leta efter uppdateringar betraktar Microsoft inte som att man vill säkerställa att man har senaste stable release utan som att man vill ta del av färska ändringar, prova på det senaste, mao man anmäler sig till testning av försläpp. De kallar releaserna C och D och som jämförelse kommer några benämningar på vad den sortens releaser kallas; preview releases, nightly build, pre-release, release-candidate eller beta. Inget fel med försläpp som sådant men sättet det presenteras mot användaren är missvisande. Skulle man ha något problem är det självfallet bra med early access till åtgärd och det är i ett sådant läge är det idé att använda Check for updates.

Most users are familiar with what is commonly referred to as “Patch Tuesday” or Update Tuesday.  These updates are published on the second Tuesday of each month, known as the “B” release (“B” refers to the second week in the month), and are the only regular monthly releases that include both new security fixes and previously released security and non-security fixes. […]
We also release optional updates in the third and fourth weeks of the month, respectively known as “C” and “D” releases. These are preview releases, primarily for commercial customers and advanced users “seeking” updates.  These updates have only non-security fixes. The intent of these releases is to provide visibility into, and enable testing of, the non-security fixes that will be included in the next Update Tuesday release.

För att ta del av senaste stable release behöver man bara avvakta att datorn vill starta om onsdag morgon den andra veckan i månaden. Undantaget om er IT har egen styrning på när uppdateringar distribueras.

Windows 10 version 1809

After updating Windows 10 to version 1809 there have been reports that AutoCAD can no longer be run. Affected AutoCAD versions are 2018 and 2019.

Upon start AutoCAD crashes with the following error message: “VLISP internal error”, “Unhandled exception on init”

To resolve the problem restore back to previous Windows version 1803.

It seems the 1809 update have been retracted for now. Should the update offer itself it is currently wise to postpone/decline.