Restore-DatabaseAvailabilityGroup Fails With 0x46 Error in Exchange 2010 SP1

While running Restore-DatabaseAvailabilityGroup to restore a DAG in the secondary datacentre, the command fails with the error code 0x46. The version of Exchange I had was 2010 SP1 UR5. I came across the error below while restoring the DAG with the built-in cmdlet. Restore-databaseAvailabilityGroup DAG01 WARNING: Server ‘EX20101’ was marked as stopped in database availability…

While running Restore-DatabaseAvailabilityGroup to restore a DAG in the secondary datacentre, the command fails with the error code 0x46. The version of Exchange I had was 2010 SP1 UR5.

I came across the error below while restoring the DAG with the built-in cmdlet.

Restore-databaseAvailabilityGroup DAG01

WARNING: Server ‘EX20101’ was marked as stopped in database availability
group ‘DAG01’ but couldn’t be removed from the cluster. Error: A server-side
database availability group administrative operation failed. Error: The
operation failed. CreateCluster errors may result from incorrectly configured
static addresses. Error: An error occurred while attempting a cluster
operation. Error: Cluster API
‘”EvictClusterNodeEx(node.domain.com) failed with 0x46.
Error: The remote server has been paused or is in the process of being
started”‘ failed. [Server: EX20102.HEW.LOCAL]
WARNING: The operation wasn’t successful because an error was encountered. You
may find more details in log file.

dag issue

The Restore-DatabaseAvailabilityGroup reads the “stopped servers” in the DAG and evicts them from the DAG’s underlying cluster. But, the issue here is that the cmdlet issued the node eviction before the cluster service was initialized.

The cluster service was stopped prior to running the cmdlet, because of the instructions given in TechNet. The first step mentioned in TechNet is to stop cluster service on all remaining DAG members, which was applicable to Exchange 2010 RTM. This step is not required if you are running Exchange 2010 SP1+.

Stop cluster service instruction

So, there are two ways to fix the error.

  1. Run the cmdlet again and the eviction will be successful, as the cluster service will have initialized by that time.
  2. Update your DR documentation to avoid the step of stopping the cluster service.

Leave a Reply

Your email address will not be published. Required fields are marked *