Answered by:
MMC has detected an error in a snap-in and will unload it

Question
-
Windows server 2008 x64 Exchange 2007 sp2
when i start the Exchange Management Console i get the folowing error
MMC has detected an error in a snap-in and will unload it
Report this to microsoft, and then shutdown MMC
Unload the snap-in and continue running.
so i choose the lower option that opens into error:
Unhandled exception in managed code snap-in
FX:{76dd58f7-54ba-42e3-a2e0-dbf4b674539f}
Exception has been thrown by the target of an invocation.
Exception type:
System.Reflection.TargetInvocationException
Exception stack trace:
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at Microsoft.ManagementConsole.FormView.InternalInitialize()
at Microsoft.ManagementConsole.View.HandleInitializationRequest(IRequestStatus requestStatus)
at Microsoft.ManagementConsole.View.ProcessRequest(Request request)
at Microsoft.ManagementConsole.ViewMessageClient.ProcessRequest(Request request)
at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)
at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest()
at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)then the mmc window loads without any functionality
Does anyone know how to solve this, i would appreciate any help i can get.
Sunday, February 2, 2014 4:35 PM
Answers
-
have resolved this and other issues on the server by editing the machine.config in the: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG
- Marked as answer by shawns587 Tuesday, February 4, 2014 12:55 AM
Tuesday, February 4, 2014 12:55 AM
All replies
-
Hi
Try cycle IIS and see if you can get into the MMC. Alternatively have you tried restarting the server?
Monday, February 3, 2014 4:35 AM -
-
Hi, i have multiple issues on this server
the server has had a restart.
when i got to administer IIS7
there was an error when trying to connect. Do you want to retype your credentials and try again?
Filename:
\\?\C:\windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config
Line number: 13
Error The configuration section 'system.web' cannot be read because it is missing a section declaration
Monday, February 3, 2014 1:55 PM -
Hi, thanks for the response, this server difficult to configure.
.Net 3.5 – cannot install generates the following errors:
The package unzips and setup begins ..
Around half of the way through setup it errors:
gives a log entry that shows
[02/03/14,13:38:49] Microsoft .NET Framework 3.0SP1 (x64) (CBS): [2] Error: Installation failed for component Microsoft .NET Framework 3.0SP1 (x64) (CBS). MSI returned error code 1
[02/03/14,13:39:34] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0SP1 (x64) (CBS) is not installed.
also get:
Description:
Microsoft .NET Framework 3.5 SP1 has encountered a problem during setup. Setup did not complete correctly.
Problem signature:
Problem Event Name: VisualStudio8Setup
Problem Signature 01: 35101
Problem Signature 02: 3.5.30729.01_ORCAS_X86_NET
Problem Signature 03: CBS
Problem Signature 04: INST
Problem Signature 05: F
Problem Signature 06: gencomp753,{61040379-156d-4ece-b126-ea395a3b2
Problem Signature 07: BASERET_FAILURE
Problem Signature 08: -
Problem Signature 09: 1
Problem Signature 10: WUSA
OS Version: 6.0.6002.2.2.0.305.9
Locale ID: 2057
Additional information about the problem:
LCID: 1033
Monday, February 3, 2014 1:59 PM -
have resolved this and other issues on the server by editing the machine.config in the: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG
- Marked as answer by shawns587 Tuesday, February 4, 2014 12:55 AM
Tuesday, February 4, 2014 12:55 AM -
I Fixed the issue by the clearing the old logs and increasing the size of event log.
Steps Done to fix it >>> Event Viewer --> Windows Logs --> Application --> Right Click properties.
Increased the Max siz log, Updated the over right event and last cleared the logs.Thursday, February 20, 2014 4:54 AM