Skip to main content

Move-ActiveMailboxDatabase - Failed

If by any chance you see the error below after updating the server which is part of DAG, just suspend and then activate the database copy. Exchange will resynchronize the copies and you’ll be able to move the database. You do that by clicking on the database under Database Management, then select non active copy in the Database Copies window, right click on it and select Suspend Database Copy. Repeat the step and select Resume Database Copy.
Move-ActiveMailboxDatabase
Failed
Error:
An Active Manager operation failed. Error The database action failed. Error: An error occurred while trying to validate the specified database copy for possible activation. Error: Database copy 'DBx' has been blocked from activation on server 'x.domain.com' by an administrative action. Reason: None specified.. [Database: DBx, Server: x.domain.com]
An Active Manager operation failed. Error An error occurred while trying to validate the specified database copy for possible activation. Error: Database copy 'DBx' has been blocked from activation on server 'x.domain.com' by an administrative action. Reason: None specified..
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.2.318.0&t=exchgf1&e=ms.exch.err.Ex92D94B
Exchange Management Shell command attempted:
Move-ActiveMailboxDatabase -Identity 'DBx' -ActivateOnServer 'x' -MountDialOverride 'None'
Elapsed Time: 00:00:00
Labels:

Comments

  1. AnonymousOctober 29, 2012 at 11:26 AM

    Thanks,you just saved me some time with this phenomena....
    Udi

    ReplyDelete
  2. Ross GemuendNovember 21, 2012 at 5:38 AM

    That worked for me too, thanks!

    ReplyDelete
  3. AnonymousMarch 4, 2013 at 10:38 AM

    Thanks Very Helped!!

    ReplyDelete
  4. AnonymousMarch 21, 2013 at 10:36 AM

    It works like a charm. Thanks!

    ReplyDelete
  5. AnonymousJuly 8, 2013 at 10:33 AM

    Excellent! It works like a charm. Thank you.

    ReplyDelete
  6. AnonymousFebruary 7, 2014 at 1:31 PM

    You saved my day :-) Thanks.
    Dragan.

    ReplyDelete
  7. AnonymousFebruary 22, 2015 at 11:29 AM

    Thanks. Same problem with Exchange 2013 CU7 Update. Suspend -> resume and failover was possible

    ReplyDelete
  8. ThalaDecember 30, 2015 at 2:39 AM

    Excellent! It works like a charm. You saved my life

    ReplyDelete
  9. PageDecember 26, 2019 at 10:38 AM

    Thanks for saving my time!

    ReplyDelete

Post a Comment

Popular posts from this blog

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;) So you need to change ports on those connectors. I will not say those two, because you might be using more than two. You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding) Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the
12 comments
Read more

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi
Post a Comment
Read more

The attempt to connect to http://yourserver/PowerShell using "Kerberos" authentication failed

The error you get: The attempt to connect to http://yourserver/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found If you removed Exchange server from the machine and installed it again, you can get following error when you open Exchange Management Console: The following error occurred while attempting to connect to the specified Exchange server 'yourserver.domain.com': The attempt to connect to http://yourserver.domain.com/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found. Possible causes are:   -The user name or password specified are invalid.   -Kerbero
32 comments
Read more