信箱會隔離,資料庫容錯移轉意外地在 Exchange Server 2013

請注意--重要:本文是以 Microsoft 機器翻譯軟體翻譯而成,且可能由 Microsoft Community 利用 Community Translation Framework技術或人工進行事後編修。翻譯過程並無專業譯者參與。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 Service Pack 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"}    } 

警告:本文為自動翻譯

內容

文章識別碼:3095369 - 最後檢閱時間:09/17/2015 03:10:00 - 修訂: 1.0

Microsoft Exchange Server 2013 Standard, Microsoft Exchange Server 2013 Enterprise

  • kbsurveynew kbmt KB3095369 KbMtzh
意見反應