SCSM 2016 / SCOM 2016 – SCOM 2016 Console Crashes After SCSM 2016 Console Installation

Have you ever installed System Center Service Manager 2016 and System Center Operations Manager 2016 console on the same system? Depending on the installation order, the SCOM console will crash with multiple errors like this…

…and the console will appear empty or crash totally. We had the case, that the SCOM console was installed first and the SCSM console afterwards. It is a known issue and MVP Eric Berg as blogged about it in German, check his post here.

Because this error has massive impact and I was also affected by this nasty bug I will re-write it in English and pimp this post with some nice screenshots :).

The problem is the Analysis Management Objects (AMO) 2014 package which is being installed by the SCSM 2016 console installation. What you could do, is uninstalling the Analysis Management Objects (AMO) 2014 package and run a repair installation of the SCOM console.

A better workaround is the following (taken from Eric Berg’s blog)…

First, add an environment variable called DEVPATH and value C:\Program Files\Microsoft System Center 2016\Operations Manager\Console\SDK Binaries…

Next, go to the C:\Program Files\Microsoft System Center 2016\Operations Manager\Console\ directory and edit the Microsoft.EnterpriseManagement.Monitoring.Console.exe.config file…

…add the line at the end of the file,  like below <developmentMode developerInstallation=”true” /> and save the file.

There is no need to restart the system, just close and open the consoles. Voilà, now everything works as expected. As I mentioned, Microsoft is aware of this bug and will fix it soon. Until then, there is just this workaround available. Hope this helps!