Thursday, 16 November 2017 12:37

Fixing the "MMC could not create the snap-in" Error in Active Roles Console

Written by
Rate this item
(4 votes)

image

Quite a few of my blog posts start off with a customer engagement - this one is no different. This week I am implementing a LoginVSI Automation Machine powered RDS infrastructure at a large automotive company. This process involves packaging quite a few applications including Dell Active Roles 7.1 MMC Interface, a single, intuitive tool designed for comprehensive privileged account management in Active Directory and Azure Active Directory. Packaging Dell Active Roles console is *SUPER* easy with Login VSI Automation Machine because it comes in an MSI package, so all you need to do is simply importing the MSI file into the media repository, creating the corresponding package and adding Install MSI action item. However, when opening the Dell Active Roles 7.1 console, the following error reared its ugly head: "MMC could not create the snap-in. The snap-in might not have been installed correctly.", followed by "CLSID: {D50F5BB7-337F-4A59-8797-BDA0B7DC1DF0}".

Normally I would check vendor's documentation for installation prerequisites, but as I did not have access to any product documentation I had no choice but to investigate myself. My initial hunch was to check the Event Viewer's Application log for error messages, but I came up empty.

Next, I opened the ActiveRoles.msc file in Notepad++. It referenced two CLSID: {C96401CC-0E17-11D3-885B-00C04F72C717} and {D50F5BB7-337F-4A59-8797-BDA0B7DC1DF0} (the one shown in the error message). The first CLSID references mmcndmgr.dll and is used by default in all consoles. The only purpose of this snap-in is to create a sub-section in the console root. The second CLSID corresponds to the file C:\Program Files\Dell\Active Roles\7.1\Console\ActiveRoles.msc. So I still had nothing.

After some more digging around the customer's base Windows Server 2012 R2 image, I noticed that the installation did not include various Microsoft Visual C++ runtimes. As a rule of thumb, I always include following Visual C++ runtimes in the reference image because a lot of applications out there are dependant on one or multiple VC++ libraries: 2008, 2010, 2012, 2013 and 2017.

Once I built and deployed the Visual C++ bundle, I could start the Active Roles console and the issue was resolved.

Read 10217 times Last modified on Thursday, 16 November 2017 14:04
Published in OS Deployment
Anton Romanyuk

Latest from Anton Romanyuk

More in this category: « Using MDT to Import Wireless Network Profile Install Appx Files Using PowerShell Wrapper »
back to top

Main Menu

Recent Posts

  • Windows 10 21H2 Built-In Apps: What to Keep
    The development of the Windows 10, version 21H2 is finished and the update will soon be available for download from…
    Written on Wednesday, 20 October 2021 11:41
  • Group Policy Changes in Windows 10 21H2
    As Windows 10, version 21H2 update development winds down, Microsoft is now preparing for the final release of the Windows…
    Written on Wednesday, 20 October 2021 07:20
  • Group Policy Changes in Windows 10 20H1 Preview
    As Windows 10 Vibranium Update (20H1) development winds down, Microsoft is now beginning the phase of checking in the final…
    Written on Tuesday, 14 January 2020 04:51
  • An alternative ESU MAK Activation Solution
    This blog post was shared with me by a colleague of mine, Daniel Dorner, a Microsoft Premier Field Engineer. It’s…
    Written on Wednesday, 04 December 2019 21:04
  • The Case of Missing UE-V Templates
    My customers often deal with unexpected Windows behavior and this case is no different. This particular one is especially interesting…
    Written on Tuesday, 03 September 2019 12:20
  • The Case of Changing Default Printer
    While I sometimes long for the day when I no longer have to deal with unexpected Windows 10 behavior, there’s…
    Written on Wednesday, 14 August 2019 20:36

Guides