Windows Server

Unable to install SQL Server 2019 – SQL Install Error: The MOF compiler could not connect with the WMI server

The other day I was doing K2 5.5 installation on top of Windows Server 2019 and somehow that install beat all the records in terms of weird issues I run into, and even after re-provisioning server and starting from scratch I had to do resolve quite a few of them. One of those errors (not Unable to install SQL Server 2019 – SQL Install Error: The MOF compiler could not connect with the WMI server

Unable to run SharePoint 2019 installer when Office 365 is installed on the same machine

I recently spend some days having fun with good old on premise software and it really makes one appreciate infra as a code and provisioning everything in the cloud, fast. 🙂 The problem is that most of the vendors of on prem software have more focus on introducing their cloud offerings and do not want Unable to run SharePoint 2019 installer when Office 365 is installed on the same machine

Windows Server 2016: CDPUserSvc has stopped working

You may observe the following error on Windows Server 2016 immediately after OS startup: This “has stopped working” part tells us that some unhandled exception occurred, so we can switch over to Event Viewer to find some more details about it: Exception details are the following: Faulting application name: svchost.exe_CDPUserSvc_65df7, version: 10.0.14393.0, time stamp: 0x57899b1c Windows Server 2016: CDPUserSvc has stopped working

GAC folders

I keep forgetting exact GAC folders’ locations and whenever I try to Google this information it is always buried under some layers of misunderstanding and confused discussions. This steams from the fact that there are different locations depending on .NET version and bitness of your assemblies. So I’m just jotting down all the locations here GAC folders