Quantcast
Channel: Exchange Server 2013 - High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 1985

Exchange 2013 cannot failover databases manually or upon reboot, blocking a migration

$
0
0

I have 6 Exchange 2013 CU 13 servers, 3 CAS and 3 Mailbox in a DAG. When I run move-activemailboxdatabase, I receive the following error:

An Active Manager operation failed. Error: The database action failed. Error: An error occurred while trying to select
a database copy for possible activation. Error: The database 'XXXXXXXXX' was not mounted because errors occurred
either while validating database copies for possible activation, or while attempting to activate another copy.
Detailed error(s):
        XXXXXX:
        A server-side administrative operation has failed. The Microsoft Exchange Replication service may not be
running on server XXXX.mydomain.org. Specific RPC error message: Error 0x6ba (The RPC server is unavailable) from
cli_RpcsGetCopyStatusWithHealthState
         [Database: XXXXX, Server: XXXXXXXX]
    + CategoryInfo          : InvalidOperation: (XXXXX:ADObjectId) [Move-ActiveMailboxDatabase], AmDbActionWrapp
   erException
    + FullyQualifiedErrorId : [Server=XXXXXX,RequestId=0d13ea5f-f0f3-40e9-ac3b-515ca3b64d96,TimeStamp=7/15/2016 8
   :05:23 AM] [FailureCategory=Cmdlet-AmDbActionWrapperException] B6FDBB31,Microsoft.Exchange.Management.SystemConfig
  urationTasks.MoveActiveMailboxDatabase

I've tried the following:
1. Reboot each server
2. Reset the TCP Chimney
3. Run test-replication health on each server (from each server, I tried to run this Cmdlet on every other server to see if there were any network issues but I always got a passing result:
Check                      Result
-----                      ------
ClusterService             Passed
ReplayService              Passed
ActiveManager              Passed
TasksRpcListener           Passed
TcpListener                Passed
ServerLocatorService       Passed
DagMembersUp               Passed
MonitoringService          Passed
ClusterNetwork             Passed
QuorumGroup                Passed
DatabaseRedundancy         Passed
DatabaseAvailability       Passed
DBCopySuspended            Passed
DBCopyFailed               Passed
DBInitializing             Passed
DBDisconnected             Passed
DBLogCopyKeepingUp         Passed
DBLogReplayKeepingUp       Passed
4. Check to ensure that the copy queue length, replay queue length are both zero and the content index state is listed as healthy.
5. Checked to make sure that the firewall was disabled and there was no third-party antivirus or firewall software running that could cause a network issue
6. Tried to run resume-mailboxdatabase on each health DB copy to see if that would help. The cmdlet returned successfully each time but didn't fix anything


Viewing all articles
Browse latest Browse all 1985

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>