Article ID: 979695 - View products that this article applies to.
When you try to start the Exchange Management Console (EMC) snap-in, you receive the following error message:
MMC could not create the snap-in.
MMC could not create the snap-in. The snap-in might not have been installed correctly.
Name: Exchange Server 2007
Unhandled Exception in Managed Code Snap-in
Could not load file or assembly 'Microsoft.Exchange.Management.SnapIn.Esm, Version=18.104.22.168, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)
Exception type: System.IO.FileLoadException
Exception stack trace:
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Activator.CreateInstance(String assemblyName, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object args, CultureInfo culture, Object activationAttributes, Evidence securityInfo, StackCrawlMark& stackMark)
at System.Activator.CreateInstance(String assemblyName, String typeName)
at System.AppDomain.CreateInstanceAndUnwrap(String assemblyName, String typeName)
at Microsoft.ManagementConsole.Internal.SnapInClient.CreateSnapIn(String assemblyName, String typeName)
at Microsoft.ManagementConsole.Internal.ClassLibraryServices.Microsoft.ManagementConsole.Internal.IClassLibraryServices.CreateSnapIn(String assemblyName, String typeName)
at Microsoft.ManagementConsole.Executive.RunningOperationsTable.EnqueueOperation(Operation operation)
at Microsoft.ManagementConsole.Executive.StandAloneComponentData..ctor(SnapInRegistrationInfo info, Int32 bookkeepingId)
at Microsoft.ManagementConsole.Advanced.FrameworkSnapInFactory.Microsoft.ManagementConsole.Advanced.ISnapInFactory.CreateSnapIn(Int32 bookkeepingId, String snapInKey, Object& snapIn)
If you start the Exchange Management Shell (EMS) at a command prompt by running the cmdlet C:\Program Files\Microsoft\Exchange Server\bin\exshell.psc1, you receive the following error message:
WARNING: The following errors occurred when loading console C:|Program Files\Microsoft\Exchange Server\bin\exshell.psc1:
Cannot load Windows Powershell snap-in Microsoft.Exchange.Management.Powershell.Admin because of the following error:
Could not load file or assembly 'Microsoft.Exchange.Management.Powershell.Configuration, Version=22.214.171.124, Culture=neutral, PublicKeyToken=31bf3856as364e35' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)
Command ", ' C:\Program Files\Microsoft\Exchange Server\bin\exshell.psc1'" could not be executed because some Windows Powershell snap-ins did not load.
This issue occurs when you used the Strong Name tool, SN.exe, to disable Strong Name validation. Strong Name is a technology that was introduced together with the .NET Framework for use with managed code. Because Exchange Server 2007 uses managed code, Strong Name must be enabled. Otherwise, services will fail.
Note This issue can occur if there is an Exchange Server Interim Update (IU) installed. For information about how to resolve this issue when an Exchange Server IU is installed, see the "More Information" section.
To resolve this issue, you must re-enable Strong Name validation. To do this, you must use the Strong Name tool (Sn.exe) that is included with the .NET Framework Software Development Kit (SDK).
To do this, open a command prompt, type the following command, and then press Enter:
sn -Vr *Note To check your current settings for Strong Name verification, use the following command:
Strong Names Verification must disabled when you install an Exchange Server IU. Therefore, this issue can occur if there is an IU is installed on the Exchange Server computer. To resolve this issue when an IU is installed, uninstall the IU and then install the most recent Exchange Server service pack.
For more information about the .NET Framework SDK, go to the following Microsoft website:
.NET Framework 4.5For more information about the .NET Framework security policy model, go to the following Microsoft Developer Network (MSDN) website:
Security Policy ModelFor more information about how to use the Strong Name tool (Sn.exe) to create an assembly in the .NET Framework SDK, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/302340/ )How to create an assembly with a strong name in the .NET Framework SDK