Had a test environment with Exchange 2013 RTM:
DC:W2K12
CA:W2K12 CA+MB
DAG1(N1 & N2): W2K8 R2 SP1MB Only
DAG2(N1 & N2): W2K12MB Only
Both DAGs were functioning.
With CU1 release built a new test environment with CU1 binaries (no upgrade):
DC:W2K12
CA:W2K12 CA Only
Stand Alone:W2K8 R2 SP1MB Only
DAG1(N1 & N2):W2K8 R2 SP1MB Only
DAG2(N1 & N2):W2K12MB Only
But cannot get the appropriate sets into the DAG. I get the following (previously known and discussed) 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 '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned
because the timeout period expired"' failed.. [Server: e13-w12-mb1.domain.org]
+ CategoryInfo : InvalidArgument: (:) [Add-DatabaseAvailabilityGroupServer], DagTaskOperationFailedExcept
ion
+ FullyQualifiedErrorId : F7E8BD7E,Microsoft.Exchange.Management.SystemConfigurationTasks.AddDatabaseAvailabilityG
roupServer
+ PSComputerName : e13-w12-mb1.e2k13.org
Now, both servers are WK12 Datacenter, the CNO for the DAG was pre-created and disabled, the first node gets added to the DAG, the second fails.
Same story with the W2K8 R2 SP1 set:
If I remove successfully added node from the DAG and add the previously failing node - it would succeed, but then I cannot add the other node, that used to not have a problem.
The following Error is in the Application Log:
Event ID:4066
Source:MSExchangeRepl
Category:General
Text:An error occurred while trying to write to the cluster database. Error: OpenCluster failed with error 1753.
Searched a lot - have not found anything useful.
Decided to unistall Exchange 2013 CU1 and install Exchange 2013 RTM, since I did not have issues with that.
Uninstall worked just fine - install does not. On W2K8 R2 SP1 nodes I get the follwing error:
The following error was generated when "$error.Clear();
. "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1";
Set-NtlmLoopbackCheck $false
" was run: "The term 'C:\Program Files\Microsoft\Exchange Server\V15\\Scripts\ConfigureNetworkProtocolParameters.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.".
Error:
The following error was generated when "$error.Clear();
. "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1";
Set-NtlmLoopbackCheck $false
" was run: "The term 'Set-NtlmLoopbackCheck' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.".
P.S. Both sets of nodes have 4 NICs - One "Public", two "iSCSI" and one "Private". From the server build point of view the CU1 environment is exacly like the RTM environment, that used to function just fine.
P.S. From Exchange point of view (not counting the DAG issues) all servers could send and receive mail, using OWA.
Any help would be much appreciated.
DC:W2K12
CA:W2K12 CA+MB
DAG1(N1 & N2): W2K8 R2 SP1MB Only
DAG2(N1 & N2): W2K12MB Only
Both DAGs were functioning.
With CU1 release built a new test environment with CU1 binaries (no upgrade):
DC:W2K12
CA:W2K12 CA Only
Stand Alone:W2K8 R2 SP1MB Only
DAG1(N1 & N2):W2K8 R2 SP1MB Only
DAG2(N1 & N2):W2K12MB Only
But cannot get the appropriate sets into the DAG. I get the following (previously known and discussed) 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 '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned
because the timeout period expired"' failed.. [Server: e13-w12-mb1.domain.org]
+ CategoryInfo : InvalidArgument: (:) [Add-DatabaseAvailabilityGroupServer], DagTaskOperationFailedExcept
ion
+ FullyQualifiedErrorId : F7E8BD7E,Microsoft.Exchange.Management.SystemConfigurationTasks.AddDatabaseAvailabilityG
roupServer
+ PSComputerName : e13-w12-mb1.e2k13.org
Now, both servers are WK12 Datacenter, the CNO for the DAG was pre-created and disabled, the first node gets added to the DAG, the second fails.
Same story with the W2K8 R2 SP1 set:
If I remove successfully added node from the DAG and add the previously failing node - it would succeed, but then I cannot add the other node, that used to not have a problem.
The following Error is in the Application Log:
Event ID:4066
Source:MSExchangeRepl
Category:General
Text:An error occurred while trying to write to the cluster database. Error: OpenCluster failed with error 1753.
Searched a lot - have not found anything useful.
Decided to unistall Exchange 2013 CU1 and install Exchange 2013 RTM, since I did not have issues with that.
Uninstall worked just fine - install does not. On W2K8 R2 SP1 nodes I get the follwing error:
The following error was generated when "$error.Clear();
. "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1";
Set-NtlmLoopbackCheck $false
" was run: "The term 'C:\Program Files\Microsoft\Exchange Server\V15\\Scripts\ConfigureNetworkProtocolParameters.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.".
Error:
The following error was generated when "$error.Clear();
. "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1";
Set-NtlmLoopbackCheck $false
" was run: "The term 'Set-NtlmLoopbackCheck' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.".
P.S. Both sets of nodes have 4 NICs - One "Public", two "iSCSI" and one "Private". From the server build point of view the CU1 environment is exacly like the RTM environment, that used to function just fine.
P.S. From Exchange point of view (not counting the DAG issues) all servers could send and receive mail, using OWA.
Any help would be much appreciated.
BostonTea