被隔离邮箱和数据库故障转移意外在 Exchange Server 2013

重要说明:本文是由 Microsoft 机器翻译软件进行的翻译并可能由 Microsoft 社区通过社区翻译机构(CTF)技术进行后期编辑,或可能是由人工进行的翻译。Microsoft 同时向您提供机器翻译、人工翻译及社区后期编辑的文章,以便对我们知识库中的所有文章以多种语言提供访问。翻译的文章可能存在词汇、句法和/或语法方面的错误。Microsoft 对由于内容的误译或客户对内容的使用所导致的任何不准确、错误或损失不承担责任。

点击这里察看该文章的英文版: 3095369
症状
在 Microsoft Exchange Server 2013年环境中,意外地隔离邮箱和数据库已卸除。或者,如果服务器是数据库可用性组的成员,它将故障转移到另一个成员服务器。此外,以下事件将写入应用程序日志中:
ID: 1014Level: WarningSource: MSExchangeISMachine: exchangeserver.contoso.comMessage: The mailbox with mailboxguid "3d488bd9-cfe0-493e-907a-2aa299885f45" has been quarantined. Access to this mailbox will be restricted to administrative logons for 1.00:00:00 since the last report.ID: 1002Level: ErrorSource: MSExchangeISMachine: exchangeserver.contoso.comMessage: Unhandled exception (System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode.at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout)at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout)at Microsoft.Exchange.Server.Storage.Common.LockManager.NamedLockObject.TryGetLock(LockType lockType, TimeSpan timeout, ILockStatistics lockStats)at Microsoft.Exchange.Server.Storage.Common.LockManager.GetNamedLockImpl(NamedLockObject lockObject, LockType lockType, TimeSpan timeout, ILockStatistics lockStats)at Microsoft.Exchange.Server.Storage.StoreCommonServices.Context.StartMailboxComponentReadOperation(LockableMailboxComponent component)at Microsoft.Exchange.Server.Storage.StoreCommonServices.ReplidGuidMap.GetGuidFromReplid(Context context, UInt16 replid)at Microsoft.Exchange.Protocols.MAPI.RcaTypeHelpers.StoreIdToExchangeId(StoreId storeId, Mailbox mailbox)at Microsoft.Exchange.Server.Storage.MapiDisp.RopHandlerBase.OpenFolder(IServerObject serverObject, StoreId folderId, OpenMode openMode, OpenFolderResultFactory resultFactory)at Microsoft.Exchange.RpcClientAccess.Parser.RopOpenFolder.InternalExecute(IServerObject serverObject, IRopHandler ropHandler, ArraySegment`1 outputBuffer)at Microsoft.Exchange.RpcClientAccess.Parser.InputOutputRop.Execute(IConnectionInformation connection, IRopDriver ropDriver, ServerObjectHandleTable handleTable, ArraySegment`1 outputBuffer)at Microsoft.Exchange.RpcClientAccess.Parser.RopDriver.ExecuteRops(List`1 inputArraySegmentList, ServerObjectHandleTable serverObjectHandleTable, ArraySegment`1 outputBuffer, Int32 outputIndex, Int32 maxOutputSize, Boolean isOutputBufferMaxSize, Int32& outputSize, AuxiliaryData auxiliaryData, Boolean isFake, Byte[]& fakeOut)at Microsoft.Exchange.RpcClientAccess.Parser.RopDriver.Execute(IList`1 inputBufferArray, ArraySegment`1 outputBuffer, Int32& outputSize, AuxiliaryData auxiliaryData, Boolean isFake, Byte[]& fakeOut)at Microsoft.Exchange.Server.Storage.MapiDisp.MapiRpc.<>c__DisplayClass9.<DoRpc>b__6(MapiContext operationContext, MapiSession& session, Boolean& deregisterSession, AuxiliaryData auxiliaryData)at Microsoft.Exchange.Server.Storage.MapiDisp.MapiRpc.Execute(IExecutionDiagnostics executionDiagnostics, MapiContext outerContext, String functionName, Boolean isRpc, IntPtr& contextHandle, Boolean tryLockSession, String userDn, IList`1 dataIn, Int32 sizeInMegabytes, ArraySegment`1 auxIn, ArraySegment`1 auxOut, Int32& sizeAuxOut, ExecuteDelegate executeDelegate)at Microsoft.Exchange.Server.Storage.MapiDisp.MapiRpc.DoRpc(IExecutionDiagnostics executionDiagnostics, IntPtr& contextHandle, IList`1 ropInArraySegments, ArraySegment`1 ropOut, Int32& sizeRopOut, Boolean internalAccessPrivileges, ArraySegment`1 auxIn, ArraySegment`1 auxOut, Int32& sizeAuxOut, Boolean fakeRequest, Byte[]& fakeOut)at Microsoft.Exchange.Server.Storage.MapiDisp.PoolRpcServer.EcDoRpc(MapiExecutionDiagnostics executionDiagnostics, IntPtr& sessionHandle, UInt32 flags, UInt32 maximumResponseSize, ArraySegment`1 request, ArraySegment`1 auxiliaryIn, IPoolSessionDoRpcCompletion completion)at Microsoft.Exchange.Server.Storage.MapiDisp.PoolRpcServer.EcPoolSessionDoRpc_Unwrapped(MapiExecutionDiagnostics executionDiagnostics, IntPtr contextHandle, UInt32 sessionHandle, UInt32 flags, UInt32 maximumResponseSize, ArraySegment`1 request, ArraySegment`1 auxiliaryIn, IPoolSessionDoRpcCompletion completion)at Microsoft.Exchange.Server.Storage.MapiDisp.PoolRpcServer.<>c__DisplayClassf.<EcPoolSessionDoRpc>b__c()at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch[T](TryDelegate tryDelegate, GenericFilterDelegate filterDelegate, GenericCatchDelegate catchDelegate, T state)).ID: 1013Level: ErrorSource: MSExchangeISMachine: exchangeserver.contoso.comMessage: The mailbox with mailboxguid "a5ec8237-d1b3-4ffb-9bca-9047258cfd87" caused crash or resource outage on database (GUID="daf144bc-eafb-46dc-a290-d375898a5829")ID: 126Level: ErrorSource: ExchangeStoreDBMachine: exchangeserver.contoso.comMessage: At '8/24/2015 8:37:03 PM' the Exchange store database 'DAG2-DB2048' copy on this server encountered an error that caused the database to be dismounted. For more detail about the failure, consult the Event log on the server for other "ExchangeStoreDb" or "msexchangerepl" events. A successful failover restored service.
原因
如果在服务器上安装 Microsoft.NET Framework 4.6,则会出现此问题。在 Exchange Server 2013年环境中,不支持此版本的.NET Framework。
解决方案
若要解决此问题,请从服务器卸载 Microsoft.NET Framework 4.6 的更新。
更多信息
要确定您是否具有 Microsoft.NET Framework 4.6 安装在您的计算机上,请检查下列:

  • 在 Windows Server 2008 服务包 2 (SP2) 或 Windows Server 2008 R2 SP1, Microsoft.NET Framework 4.6 作为在下一个产品安装 程序和功能 在控制面板中。
  • 在 Windows Server 2012, Microsoft Windows (KB3045562) 的更新 显示在 已安装的更新 在控制面板中。
  • 在 Windows Server 2012 R2, Microsoft Windows (KB3045563) 的更新 显示在 已安装的更新 在控制面板中。

您还可以使用以下 PowerShell 脚本以确定是否已安装了 Microsoft.NET Framework 4.5、 4.5.1、 4.5.2 或 4.6:

 $Reg = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey('LocalMachine', $Server)    $RegKey= $Reg.OpenSubKey("SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full")    [int]$NetVersionKey= $RegKey.GetValue("Release")     if($NetVersionKey -ge 381029)    {        "4.6 or later"        return    }    switch ($NetVersionKey)    {        {($_ -ge 378389) -and ($_ -lt 378675)} {"4.5"}        {($_ -ge 378675) -and ($_ -lt 379893)} {"4.5.1"}        {$_ -ge 379893} {"4.5.2"}        default {"Unable to Determine"}    } 

警告:本文已自动翻译

属性

文章 ID:3095369 - 上次审阅时间:09/17/2015 03:09:00 - 修订版本: 1.0

Microsoft Exchange Server 2013 Standard, Microsoft Exchange Server 2013 Enterprise

  • kbsurveynew kbmt KB3095369 KbMtzh
反馈