Hi,

I am working with SCCM 2007 eval edition. I have installed Configuration Manager in Windows server 2003 SP2. In that itself, it is having MMC. It was working fine. Now i got one error. When i try to open the Configuration Manager console, it is telling "MMC cannot initialize the snap-in".

Any one of you please help me.

Ashvanth.

I only saw that one time with the beta release. All I had to do was kill MMC from Task Manager and then all worked fine after that.

Are932303 and 913538installed?

• Proposed as answer by SiddheshM Wednesday, October 12, 2011 2:29 PM

I only saw that one time with the beta release. All I had to do was kill MMC from Task Manager and then all worked fine after that.

Are932303 and 913538installed?

• Proposed as answer by SiddheshM Wednesday, October 12, 2011 2:29 PM

I only saw that one time with the beta release. All I had to do was kill MMC from Task Manager and then all worked fine after that.

Are932303 and 913538installed?

Yes, i have tried by killing MMC from Task manager. But is was not working fine.

After telling yes for the error "MMC cannot initialise the snap-in", it is opening the MMC. But lost the data in that console.

In that console, the first option was only enable. When i try to double-click it. Its asking to delete some files. I said yes and closed all the windows.

And tried to open the MMC again, it was working fine now.

I dont have these KBs to be installed. Why we need to install these two KB(932303 and 913538) to be installed?.....

One more doubt. I am integrating SCCM 2007 with Softgrid Virtualization.

Do you know what are all the pre-requisites need to beinstalled in SCCM environmentto deploy the sequenced applications?....

To resolve this issue in server 2003 I completed the following fix.

1. Open Windows
2. Open System32
3. Look for mmc.config
4. rename mmc.config to mmc.config.bak
5. Open SCCM 2007 which should work now.

We noticed this happened to anyone who had SMS 2003 Console previously installed in the same build.

Hope this helps.

Because there are issues with .NET and WMI that these KBs resolve :-) I believe these are documented in the release notes, certainly in the prereq checker.

You might try this, it has helped others:

1. removing the site from the MMC and closing it 2. Deleting the Adminconsole cache file from \document and settings\%username%\application data\microsoft\mmc 3. starting the MMC and reconnect to the site server/database.

• Proposed as answer by Syed Irfan Naseer Thursday, November 28, 2013 7:03 AM

You might try this, it has helped others:

1. removing the site from the MMC and closing it 2. Deleting the Adminconsole cache file from \document and settings\%username%\application data\microsoft\mmc 3. starting the MMC and reconnect to the site server/database.

• Proposed as answer by Syed Irfan Naseer Thursday, November 28, 2013 7:03 AM

I, too, am having a similar problem. Tried upgrading my SMS 3.0 Primary (and only) Site to SCCM 2007 on a 2003 R2 Server. (I've ensured that .NET 3.0, MMC 3.0 are installed.) The upgrade went pear-shaped. So, I uninstalled SCCM and did a re-install from media (or rather a copy of the CD on local hd.)

Install logs say that all went well ('completed'). Since I don't administer our AD domain, I can't extend the schema. So, I ignored this warning.

I gave the two above mentioned KB's a shot, but running them gave me a notifier that I don't need these. (Already patched, if I remember correctly...)

Event viewer doesn't reveal any anomalies/complaints.

As far as I can tell SCCM is still up and running. I just can't access the console...

Found something weird: adminconsole.msc referred to C:\NTS\sms\AdminUI\Bin\SmsSnapInResources.dll
But for the life of me, I can't find this C:\NTS folder. I changed the msc to the the correct folder (...\Microsoft Configuration Manager\AdminUI\bin) and tried to run the console, but still no improvement.

The error shown in the resulting MMC window says (and has always said):
MMC could not create the snap-in. The snap-in might not have been installed correctly.
Name: System Center Configuration Manager
CLSID: FX:{6de537a5-7a1c-4fa4-ac3a-1b6fc1036560}

Also, I can't find any mmc.exe.config or mmc.config in which to delete (thus bypassing a possible force to older .NET)

Killing mmc.exe in the task manager then restarting console was also no help.

I'm running out of troubleshooting angles... HELP!

-Roger A

You might try this, it has helped others:

1. removing the site from the MMC and closing it 2. Deleting the Adminconsole cache file from \document and settings\%username%\application data\microsoft\mmc 3. starting the MMC and reconnect to the site server/database.

Couldn't remove the site: It never fully attached due to the mmc error message on startup. I did locate the cache, delete it and then try again. No luck.

Did find out that my SCCM server is up and ok! By installing the admin console on my own XP machine, I could point it to my primary site. Everything is up and running! Plus I can administrate it from my pc.

So, my only issue is that the SCCM Admin Console MMC refuses to run on the primary site. Since, I've got a way to get around this, I'm not gonna sweat this one too much. (All _other_ MMCs seem to function fine.)

Thanks for the effort! I guess I'll see if this annoyance goes away in the upcoming service pack.

-Roger A

Has anyone resolved this, I am getting the same error when i try to upgrade install the CM console on a Citrix box. We need this so that our call centre can connect to the console over Citrix. I have all the prereqs installed and and tried all of the fixes above but still no luck

I've offered all I know on this:

* Create a clean MMC snap-in and then add the Configration Manager snap-in to the new one. That has worked for some people.

* Remove the admin profile stuff as mentioned in an earlier post in this thread.

Outside that, if you get no other responses, my only othe suggestion is to open a case with product support and see if they can help. If so, then please do post the resolution back here for others.

Hi everyone.

This exact issue happened to me this morning and this was my resolution:

Rename C:\document and settings\%username%\application data\microsoft\mmc\adminconsole to adminconsole.OLD. (or I'm sure you can just delete it)

Then reopen SCCM. Worked like a charm.

-Russ

Hi,

I understand that we have received soultion to this problem. I tried above steps but it didn't work. In my case I was installing the app on XP SP2 and after repairing SCCM 2007 SP1 I used to get MMC snap-in error.

I found that after repair one of registry "HKLM\SOFTWARE\Microsoft\ConfigMgr\Setup\UI Installation Directory"was changing from "C:\Program Files\Microsoft Configuration Manager Console\AdminUI" to "C:\Program Files\Microsoft Configuration Manager Console". As there was difference in path I was getting snap-in error. Fixing this registry solved my problem.

I hope this helps someone.

Many Thanks,
Saurabh.

• Proposed as answer by Saurabh_Patel Wednesday, February 25, 2009 3:40 PM

Hi,

I understand that we have received soultion to this problem. I tried above steps but it didn't work. In my case I was installing the app on XP SP2 and after repairing SCCM 2007 SP1 I used to get MMC snap-in error.

I found that after repair one of registry "HKLM\SOFTWARE\Microsoft\ConfigMgr\Setup\UI Installation Directory"was changing from "C:\Program Files\Microsoft Configuration Manager Console\AdminUI" to "C:\Program Files\Microsoft Configuration Manager Console". As there was difference in path I was getting snap-in error. Fixing this registry solved my problem.

I hope this helps someone.

Many Thanks,
Saurabh.

• Proposed as answer by Saurabh_Patel Wednesday, February 25, 2009 3:40 PM

Hi,

I understand that we have received soultion to this problem. I tried above steps but it didn't work. In my case I was installing the app on XP SP2 and after repairing SCCM 2007 SP1 I used to get MMC snap-in error.

I found that after repair one of registry "HKLM\SOFTWARE\Microsoft\ConfigMgr\Setup\UI Installation Directory"was changing from "C:\Program Files\Microsoft Configuration Manager Console\AdminUI" to "C:\Program Files\Microsoft Configuration Manager Console". As there was difference in path I was getting snap-in error. Fixing this registry solved my problem.

I hope this helps someone.

Many Thanks,
Saurabh.

I had the same issue, none the the recommended steps fixed the issue. I had serveral other problems with SCCM and i was forced to do a site reset.

This also fixed the console issue.

You can do a site reset using the setup wizard.

Hi,

The renaming/deleting of the'adminconsole' located in C:\Documents and Settings\%username%\Application Data\Microsoft\MMC resolved this for me.

Thanks guys...

Regards,

Neil

I've had this same issue. At least I think I did. None of these solutions worked for me. I noticed however that I only had the issue in the remote console (not locally).I alsonoticed that I am unable to open 'add and remove programs' in a remote session also. I was able to do work arounds by going directly to the server console or using an admin console on anothe box but I finally had time to address this issue. Anyway, I made sure I had a good backup, wiped the old OS and made a clean installation of SCCM with all of the updates, service packs, and prerequisites and then did a restore. Now everything works properly. Still don't know the cuase, but I thought that I would share that a complete restore will in fact get rid of this issue and the problem isn't restored with the restore.

• Edited by NimbleNerd Wednesday, July 22, 2009 2:41 PM

I've had this same issue. At least I think I did. None of these solutions worked for me. I noticed however that I only had the issue in the remote console (not locally).I alsonoticed that I am unable to open 'add and remove programs' in a remote session also. I was able to do work arounds by going directly to the server console or using an admin console on anothe box but I finally had time to address this issue. Anyway, I made sure I had a good backup, wiped the old OS and made a clean installation of SCCM with all of the updates, service packs, and prerequisites and then did a restore. Now everything works properly. Still don't know the cuase, but I thought that I would share that a complete restore will in fact get rid of this issue and the problem isn't restored with the restore.

• Edited by NimbleNerd Wednesday, July 22, 2009 2:41 PM

I've had this same issue. At least I think I did. None of these solutions worked for me. I noticed however that I only had the issue in the remote console (not locally).I alsonoticed that I am unable to open 'add and remove programs' in a remote session also. I was able to do work arounds by going directly to the server console or using an admin console on anothe box but I finally had time to address this issue. Anyway, I made sure I had a good backup, wiped the old OS and made a clean installation of SCCM with all of the updates, service packs, and prerequisites and then did a restore. Now everything works properly. Still don't know the cuase, but I thought that I would share that a complete restore will in fact get rid of this issue and the problem isn't restored with the restore.

ditto for me... tried everything listed, no help.

Terry

Hi 

 

On the Configuration Manager Console, I just clicked File -> Options ->Delete Files (disk cleanup). Press Ok. Restart console

 

Above worked for me.

 

Regards

I had the same issue

Now it got rectified by replacing the old windows login profile

Regards,

Durai

 

Well I finally got it working.  Had to do the steps outlined here:

http://support.microsoft.com/?id=300956

 

It took a while but now it installs.

 

Terry

 

PS - Any insight on why Performance Monitor Counters would cause the MMC not to initialize?  Seems weird to me.

This worked for me when i had this problem on SCCM  2008R2 SP2 on Server 2008r2.

 

thanks

steve

Rename C:\document and settings\%username%\application data\microsoft\mmc\adminconsole to adminconsole.OLD. (or I'm sure you can just delete it)

-Russ

Hi,

It worked on a Win2008 R2 deleting file C:\Users\%username%\AppData\Roaming\Microsoft\MMC\tsadmin

Thanks Russ.

--

Philippe Ferrucci

http://www.amigaos.net

Windows Server 2008 R2: In this Procedure the prompt as:

You need permission to perform this action

You require permission from Trusted Installer to make changes to this file

I am already login as Administrator :S

In this Procedure i solved the problem

1.  Close the application on which the mmc prompt

2.  Deleting the Adminconsole cache file from \document and settings\%username%\application data\microsoft\mmc

3.  starting the MMC and reconnect to the site server/database.

It solved my problem in Windows Server 2008 R2.

Thankyou

You might try this, it has helped others:

 

1.  removing the site from the MMC and closing it 2.  Deleting the Adminconsole cache file from \document and settings\%username%\application data\microsoft\mmc 3.  starting the MMC and reconnect to the site server/database.

This led me into the correct way to resolve a similar issue with Win SBS 2011 / Exchange 2010.

The Exchange Management Console was not opening up and would display the error "mmc cannot initialize the snap-in" even though I could successfully manually add the Exchange Management Console to a mmc.exe snap-in. 

I also was able to log on with a different username and successfully opened the Console so it led me to believe there was an issue with the user profile.

To resolve:

Closed Exchange Management Console

Appended C:\Users\%username%\AppData\Roaming\Microsoft\MMC\Exchange Management Console with .old extension.

Exchange Management Console started successfully.

Thanks to Syed for leading me in to the right direction. : )