EDIT: an unofficial fix is appended below 🙂
Fast publish…
So, if any of you are using SCOM 2016 and have recently deployed the console, you may be getting this error below:
An object of class ManagementPackFolder with ID <MP GUID>
On the sick client, you will find the following in event viewer
Essentially, it’s a clash locally with the SCSM (Service Manager) Console..
Uninstall SCSM and SCOM Console 2016 will work immediately.
This one wasn’t all that hard to work out as the exact same experience happened for System Center 2012…
Not ideal as we use both SCSM and SCOM as core business applications so hopefully a bug fix will be out soon.
Will post when a fix is produced.
#####################################################
And the fix:
1) Add a system environment variable named DEVPATH which contains the folder path of the Microsoft.EnterpriseManagement.Core.dll. For example, in my case it is C:\Program Files\Microsoft System Center 2016\Operations Manager\Console\SDK Binaries.
2) Add the following entry in the config file C:\Program Files\Microsoft System Center 2016\Operations Manager\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe.config)
<configuration> ... <runtime> <developmentMode developerInstallation="true" /> </runtime> ... </configuration>
(add the <developmentmode> section to the existing runtime section.)
3) You may need to restart the computer (I didn’t though and it worked straight away)
And with that, balance is restored….
Enjoy!
Dan
YOU SAVED THE DAY!
Currently upgrading to SCOM 2016 and found this issue… crazy!
Thank you! I love you!
Worked like a charm for me. Thanks!
Doesn’t seem to work when adding the config to the XML. Anyone else still have the issue?
Hi Dave,
I think the mixed console bug may have been fixed in one of the update rollups.
Cheers
Hi Dan. It seems not. We are on the latest and greatest CUs with no success. Kind of a bummer. Ironically, the SCSM still works fine through it. Strange that the SCOM console doesn’t when it has much more use in a MS infrastructure.
Hi Dave, maybe uninstall the consoles and install RTM version. Then apply the fix, then apply the Update Rollups to match your versions?
Worked, thank you!!
Worked like a charm!