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
(3 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 1584 times Last modified on Thursday, 16 November 2017 14:04
  1. Comments (0)

  2. Add yours
There are no comments posted here yet

Leave your comments

Posting comment as a guest.
0 Characters
Attachments (0 / 3)
Share Your Location

Recent Posts

  • Yet Another Windows 10 Optimization Script
    As a reminder, Microsoft will be ending support for Windows 7 SP1 on January 14, 2020. I've had multiple enterprise…
    Written on Monday, 25 June 2018 16:09
  • Automating Dell BIOS Configuration Using MDT
    It’s been a busy couple of weeks for me, so I’m slowly going through a backlog of things to cover.…
    Written on Thursday, 21 June 2018 08:11
  • Configuring HP BIOS Using MDT
    This is the second post in my series that explores one of the most common questions I’ve been asked from…
    Written on Tuesday, 19 June 2018 09:54
  • BIOS to UEFI - The Easy Way: MBR2GPT
    This article is the first blog post in a series I'll write over the coming days that will provide a…
    Written on Monday, 11 June 2018 17:08
  • Force LAPS Password Reset during MDT OSD
    My customers often send me exciting cases. This particular one is especially interesting because it is common in infrastructures that…
    Written on Friday, 08 June 2018 10:10
  • Localizing Inbox Apps during OSD
    As a reader of this blog, I suspect that most of you, like me, are frequenting Twitter. And I bet…
    Written on Monday, 04 June 2018 18:18