Start Free Trial

asked on

MMC could not create the snap-in SBS 2003

Hello:
I have inherited a system with a new client of mine. The physical machine is running Server 2008 w/HyperV. SBS 2003 Service Pack 2 is running on the HyperV virtual machine. All appears to be OK, but.....
When I go into Server Management and try to expand most of the list there, I get the error, "MMC could not create the snap-in" Name=xx, Sometimes there is a CSLID listed and sometimes the CSLID is blank.
The following snap-in's cannot be loaded:
To Do List
Infomation Center
Monitoring and Reporting
Backup
Licensing
Group Policy Management

All MS updates are installed on the system. Since this is a new client and an inherited system, I don't have any specifics about exactly *how* the server was configured during setup. All I can do is poke around and see how it is now.

I've done some Googling about this and see it's common, but haven't hit upon a solution yet, so I thought I would pose this to the resident experts here! :)

TIA,
Jim

I would try reapplying Windows 2003 SP2. SP2 contains an update to the Microsoft management console program. Check this article, which mentions problems with the MMC that can appear if you have installed and then removed SP2:
http://support.microsoft.com/kb/555912

ASKER

I'll give it a try but I'm not aware that SP2 was ever uninstalled.

Jim

P.S. Any idea why there haven't been any comments/suggestions posted?

Most MMC errors are fixed with the updated version of MMC console.

http://www.microsoft.com/downloads/details.aspx?FamilyId=4C84F80B-908D-4B5D-8AA8-27B962566D9F&displaylang=en

ASKER

Thanks, ChiefIT:
I'll give it a try this weekend when my client is not in production mode.

Jim

Jim, I was thinking that re-installing SP2 would re-install the update to the MMC. It would also fix any other errors that might have happened during the initial SP2 install. However, Chief's suggestion is just as good, maybe even better, so go with it.

ASKER

Hi Hypercat:

Thanks! I'll keep you informed later this weekend

Jim

There were many problems with earlier versions of MMC console:

Seeing is believing:

https://www.experts-exchange.com/questions/23097626/MMC-cannot-open-the-file-C-WINDOWS-SYSTEM32-dsa-msc.html

@Hypercat:
MMC updates are a part of SP2? That's something I didn't know.

I was sort of peripherally aware of it, but it was confirmed by the article I found (see my above post) related to problems with MMC snap-ins in SBS after uninstalling SP2. The article stated this was caused because uninstalling SP2 removed MMC 3.0. I looked it up (http://support.microsoft.com/kb/914962) and it is listed as being included in SP2.

ASKER

Hi Folks:

Well....it gets worse...
I tried to install MMC 3.0 (which by the way, is already installed - appears to be the same version number, but I can't be certain). I received the error:

"KB90265 Setup Error: Setup has detected the Service Pack version of this system is newer than the update you are applying. There is no need to install this update."

I guess I'm a bit squeamish about uninstalling SP2 and re-installing.....I'm afraid at this point doing this might really break what's left of the working server and I'll be stuck with a pile of xxx. Not good news for a system in a production enviornment 6 days a week.

Any other ideas?

TIA,
Jim

Try this,

Go to start>>run>>type in MMC.exe

If that works try to use the ADD/Remove programs tool to reinstall MMC

ASKER

Hi ChiefIT:

I just tried that. Executing "mmc.exe" brought up a new box, "Console 1" That shows a Console Root box which contains the notation, "THere are no items to show in this view."

I then go to Add/Remove and do not see anything that looks like MMC to add/remove/repair/toss-overboard. I DO see a bunch of add/remove entries for "WIndows Small BUsiness Server Docs/Fax Cfg/Licensing/Monitoring/etc" These all have an icon at the beginning of the line that looks like an infinity symbol in multi-colors, but there is no button to take any add/remove action with them. Also, I did not see anything that looked like mmc in "add remove windows components".

I **really** appreciate your help with this one! I'm getting ready to spend $$$ to call Microsoft for tech support if I cannot noodle this one out!

TIA
Jim

If you can open up console, can your recreate mmc snapins?

ASKER

Hi. I don't know to do that. Can you point to the way? Thanks. Jim

In the top left hand corner, there is a drop down menu called "Console". Drop that menu down, and select "Add/Remove Snapin". The rest is self explanitory, select add snaping, choose your snapins to populate the MMC shell. Then, don't forget to save your console. Locate the console you created, and right click it, then select send desktop shortcut. Now, you have a populated MMC console and a desktop shortcut to it.

ASKER

Hi ChiefIT:

Ah...the plot thickens....

Went through the steps to Add a new snap-in. Selected the "licensing" snap-in (one which would not work before). Got the error , "MMC cannot initialize the snap-in"

I did see the following post:
http://social.technet.microsoft.com/Forums/en-US/configmgradminconsole/thread/d97e2f10-8e7e-485d-912c-5292fbec1817

It sounds like the problem I'm having, but references SCCM 2007. I don't know if that applies - I'm feeling somewhat out of my league here!
<groan>

Jim

As per Microsoft:
http://support.microsoft.com/kb/907265

When you try to add a managed code snap-in to MMC, you may receive the following error message:
MMC cannot initialize the Snap-in
This issue may occur if there is a version conflict with a previous MMC installation. If an earlier version of MMC is installed on the computer, remove the MMC version details from the Windows registry. To do this, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. In the left pane, locate and then expand the following registry subkey:
HKEY_CLASSES_ROOT\CLSID\{D5AB5662-131D-453D-88C8-9BBA87502ADE}\InprocServer32
3. Remove all the registry entries under the InprocServer32 key except for the 3.0.0.0 entry.
4. On the File menu, click Exit.

ASKER

Hi ChiefIT:

<sigh> There were no other registry entries under the InprocServer32 key OTHER than 3.0.0.0
Jim

ASKER

Hi ChiefIT:

I checked another SBS2003 system that is working correctly. The entries I mentioned earlier (10/4 08:09am) about what appears to be MMC parts showing without any way to remove, are NOT present on this other, working system, but I don't know if it's important or meaningful.

Just strikes me as wierd.

Jim

I am wondering if removing the 3.0 version reg keys and reinstalling MMC would fix this issue.

ASKER

I'm assuming you mean removing the 3.0.0.0 reg entry? Also, what do you think about uninstallling all of .net and reinstalling? I've read several posts on Google where mmc and .net are closely intertwined. I'm still wondering/concerned about the rogue, entries in add/remove.....

I was thinking of .net. Do you have the .net updates?

ASKER

Yes. All of .net appears to be installed. But, I'm going to uninstall ALL of .net and reinstall. Ugh.

Jim

I still think I would remove the 3.0.0 reg key and reinstall mmc.

ASKER

Hi:

That's next on this list! I'll keep you informed. Jim

ASKER

Still working on this...Waiting for a non-production time to test again. Not abondoned yet!! :)

Jim

ASKER CERTIFIED SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Awarding points is up to you. If you find helpful advice, then you could assign assists.

For me, points are just 1's and 0's on a computer somewhere. Other's strive for them.

I would like to see you accept your latest post as the acceptable answer, though. That helps others who run into this solution know what you did to fix the problem. This database is often looked at for answers.

ASKER

I would love too but my "post" is a comment. I don't see any way to accept my comment as a solution. Am I missing something? Jim