Link to home
Create AccountLog in
Avatar of wimpie_asg
wimpie_asgFlag for South Africa

asked on

Exchang 2013 on Windows server 2012 R2 MMC Snap-in fail trying to open Exchange Toolbox.

Hi all,


Exchange 2013 with latest service packs
Windows 2012 R2 with latest service packs

I have a very common problem with Exchange 2013 Toolbox snap-in (Or so it seemed common on Server 2008 R2 witch there is a hotfix available for, but I am running 2012 R2). The moment I try and open it is keeps on telling me:

"MMC has detected an error in snap-in and will unload it"

Options are:

1) Report this error to Microsoft
2) Unload the snap-in and continue running.

The moment I press option (2) it comes up with the error:

"Unhandled exception in managed code snap-in"
"Type is not resolved for member Microsoft.Exchange.Configuration"

Please let me know or point me in the right direction.

Thank you in advance!
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

There is nothing in the toolbox that you cannot get elsewhere.

It has three bits in it, all of which can be loaded separately:

It isn't a common problem, even on Windows 2008 R2 - I don't think I have required a hot fix for it. The most common reason is a broken Windows profile.

Avatar of wimpie_asg


Hi Simon,

Thank you for the reply.

I read on this quite extensively, this is the reason I decided to post here as I am out of ideas, it really does seem like a known issue rather than a common issue, wrong choice of words from my part.

The issue seems to appear quite allot in in server 2008 R2, which seems to be caused by .NET framework. I read it on the following Microsoft TechNet page at the bottom:

The above page took me to the following page in how to resolve it: 

But again, it is rollup updates / hotfixes for Windows server 2008 R2, I have server 2012 R2 with Exchange 2013.

The web page describes exactly what I am experiencing, but obviously the fix wont work for me.

In a nutshell, I need to resolve the MMC issue, I suppose a fix for the problem would be more appreciated than a work around?

Thank you for the information, do you perhaps have a fix for the MMC issue?

I am a bit frustrated, I am sure there is a obvious reason for this, basic 101 somewhere I could read up about it, and probably a real rooky mistake from my part, but this is the reason why I could not access Exchange 2013 toolbox:

 I was using the built-in administrator account to work in Exchange 2013, this server 2013 R2 was configured with an custom admin user as Microsoft disables the built-in Administrator accounts by default so you are kind of forced to create your own admin account (For security reasons I am sure) But out of habit, I enabled the built-in administrator account and I work from this, old habit I suppose?! This was where the issue came in, I could not access the Exchange 2013 Toolbox from the built-in administrator account.

When I logged in as the custom Administrator account that was created during server setup, Exchange 2013 Toolbox worked first time!!!

This is not the first time for me to come across this, I had another case where the built-in administrator account was used to access Exchange 2007 EMC, and all the custom setting like SMTP server settings were all blank. I could not even see the Exchange mounted databases' they just did not appear in the window pane. I logged in as the custom created admin account that was created during the Windows server setup (Windows server 2008 & Exchange 2007) and all the custom settings were back in the HUB transport, everything!

Could anyone please tell me why the built-in administrator account does not have full access to Exchange 2007 EMC, or Exchange 2013 toolbox? Was it perhaps that the built-in administrator account was disabled during the Exchange setup creating a user right issue? This is really annoying due to the fact that as technicians with many years of Microsoft server experience we are SO use to use the administrator account as the "Administrator"  that could do anything, and now one comes across massive issues like this which really is caused by such a trivial problem. The cause is so insignificant that one don't even think about it and yet can cause havoc.

So - the built-in administrator account cant access Exchange management, but the custom created admin account that was created during Windows server setup can access Exchange management, I had this now on Exchange 2007 and Exchange 2013, which was on Windows server 2008 & 2013.

Is there something I can do to elevate the built-in administrator accounts rights, never thought this would be needed as administrator was always the all powerful?????
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Problem resolved and was caused by an permission issue- Although the administrator account was enabled by a previous IT company and handover was given with only the administrator account username/password. I went in to the group administrators to see which other custom account formed part of this group and had administrator rights and compared it with profiles under users  that had logged on before to see which account was created during the Windows installation. I then reset this username to another password and logged on to this profile and all was fine, I could access Exchange EMC with no hassles at all. From 2003 server to 2008 server administrator accounts was always used to manage a server, thus as easy as the problem & solution might sound above, it was not so easy to think of the solution while in the midst of troubleshooting.

Old habits with server 2003 / Exchange 2003 - 2008 for 10 years or so by always using of the administrator account had me not thinking of the solution immediately, and that the problem might have been a permission issue, I mean, everything else was working after all, except the Exchange EMC!?

Simon, thank you for your valuable input, even though of the bad habit statement...