无法加载Exchange PowerShell管理单元:"Microsoft.Exchange.Data.Directory.Globals"的类型初始值设定项引发异常

Question

我有以下代码,用于在加载Exchange 2010快照时创建PowerShell运行空间.

Dim runspaceConfig = RunspaceConfiguration.Create()

Dim snapInException As PSSnapInException = Nothing
runspaceConfig.AddPSSnapIn("Microsoft.Exchange.Management.PowerShell.E2010", snapInException)

Dim runspace = RunspaceFactory.CreateRunspace(runspaceConfig)
runspace.Open()

自安装Visual Studio 2012后,我在执行将管理单元添加到runspace配置的行时开始出现以下错误.

System.Management.Automation.Runspaces.PSSnapInException occurred
  HResult=-2146233087
  Message=Cannot load Windows PowerShell snap-in Microsoft.Exchange.Management.PowerShell.E2010 because of the following error: The type initializer for 'Microsoft.Exchange.Data.Directory.Globals' threw an exception.
  Source=System.Management.Automation
  WasThrownFromThrowStatement=False
  StackTrace:
       at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.LoadCustomPSSnapIn(PSSnapInInfo mshsnapinInfo)
       at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.LoadPSSnapIn(PSSnapInInfo mshsnapinInfo)
       at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.LoadPSSnapIn(PSSnapInInfo mshsnapinInfo, PSSnapInException& warning)
       at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.DoAddPSSnapIn(String name, PSSnapInException& warning)
       at System.Management.Automation.Runspaces.RunspaceConfiguration.AddPSSnapIn(String name, PSSnapInException& warning)

我已经能够确认nlog在某种程度上导致了这个问题.在创建powershell运行空间之前创建nlog记录器的组合会导致错误.

如果我从我的应用程序配置中删除nlog配置部分并只创建一个空的nlog记录器,则加载管理单元时没有错误.此外,如果我将nlog配置保留在我的应用程序配置中但不创建nlog记录器,则该管理单元也会成功加载.

• 我尝试在x64和x86中构建项目.
• 我已经重新安装了交换管理工具.
• 我已尝试在交换环境中的另一台机器上进行测试.

如果有人能提供任何可以帮我解决这个问题的建议,我会很高兴.

谢谢

Answer 1

经过进一步调查后,我发现.NET 4.5是一个就地更新意味着.NET 4.0被覆盖并在安装时替换为.NET 4.5.我不知道.NET 4.5中发生了什么变化导致了这个问题,但是通过卸载.NET 4.5并切换回Visual Studio 2010解决了这个问题.希望微软在不久的将来会有一些更新来解决问题,并允许我再次使用Visual Studio 2012.

有关就地更新的详细信息,请参阅以下文章. http://www.devproconnections.com/article/net-framework/net-framework-45-versioning-faces-problems-141160