There is an odd error out there when trying to add the first database to a new DAG. What occurs when adding a database to a new DAG is a Windows Cluster is created, the resources and FSW for the Exchange 2010 cluster are created and the Database is then added to the DAG.
In some rare instances users are getting an error message:
Microsoft.Exchange.Cluster.Replay.DagTaskOperationFailedException: A server-side database availability group administrative operation failed. Error: The operation failed with message: An error occurred while attempting a cluster operation. Error: Cluster API ‘”CreateCluster() failed with 0×57. Error: The parameter is incorrect”‘ failed.
And
Microsoft.Exchange.Cluster.Replay.AmClusterApiException: An Active Manager operation failed. Error: An error occurred while attempting a cluster operation. Error: Cluster API ‘”CreateCluster() failed with 0×57. Error: The parameter is incorrect”‘ failed.
You will note that in these two errors is a reference to 0×57. There is nothing more, nothing in the event logs, just a generic error. This is actually very confusing and leaves it open to debate what is wrong. Also listed in the log files is the key phrase dwPercentComplete = 94. The installation is getting to 94% complete before erroring out.
Well, if you are having problems deploying your first member to a DAG and you see the 0×57 and dwPercentComplete = 94 then I would suggest you check your Network binding order on your Mailbox Server.
To Check your network binding order on Windows 2008 perform the following:
- Click on Start
- Locate Network and right click, select Properties
- On the Network and Sharing Center locate Manage network connections and click it
- On the Menu bar click Advanced and select Advanced Settings
- Move your Production NIC to the Top. The Private NIC (Heartbeat) should come Second, Remote Access Connections last. (If you’re using ISCSI it should come after the private network)
- Click OK and you’re done!
You may also need to configure your Bindings.
The Production LAN will need to have File and Printer Sharing for MS Networks enabled and Clients for MS Networks enabled. The Bindings for the Private Network will need to be unchecked.
When finished it should look something like this:
