DAG Error

I have error in database copy in DAG group and it indicates that copy " Failed and suspended" and when update database copy it take a long time then it is failed I
have this error in event log.
The Microsoft Exchange Replication service encountered an error while inspecting the logs and database for VIP DB\SRVMBX02 on startup. Error: File check failed : Database file 'E:\Exchange DB\VIP DB\VIP DB.edb' was not found.
Best Regards

Hi,
Please specify a source server to update database copy to check result.
And please use the Test-ReplicationHealth cmdlet to check replication service.
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

Exchange 2010 cross subnet Dag - Errors creating DB copies in DR site

We are running exchange 2010 standard edition in our main site with 2 mailbox servers in a DAG. I've added 2 more mailbox servers in a DR site connecting over a 20Mb fiber connection. I've tried adding one of the DR mailbox servers over to the DAG as database
server, also tried updating copies of the database after it fails to update it. Been working with Microsoft support on this but they have been little slow getting back with me so wanted to see if I can find anyone that has had this issue before. We've
changed TCP global settings, they've set the Cluster setting for samesubnet and crosssubnet threshholds settings to recommended, made sure my DAG replication networks were correct and that's about it so far. Tried running the update database
from GUI and shell but to no avail. Seems like it is copying the logs and database but fails at the very end. We thought it might be backup software running so we turned that off completely. Here are the different error messages I get..
A source-side operation failed while performing seed operation. error occurred whil communicating with mbx-01 (source server..) unable to read data from transport connection.. connected host failed to respond..
A source side operation failed performing seed operation. An I/O error occurred while attempting to access file ..CatalogData-...ci on source server could not be opened. sys cannot find file.
Information Store (1988) Mailbox-MBX-01: The internal database copy (for seeding or analysis purposes) has been stopped because it was halted by the client or because the connection with the client failed.
Any help is appreciated..
Michael Duhon

Hello,
I recommend you try to restart Microsoft Exchange Replication Service to check the result.
If the issue persists, please try to rebuild the Index for your database to check the result.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2010 DAG error adding members

I am attempting to setup a DAG with two exchange 2010 server running sp2. The DAG is there but when I try to add either server I get the following error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:11
EXCHANGE
Failed
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 '"CreateCluster() failed with 0x35. Error: The network path was not found"' failed. [Server: EXCHANGE.domain.local]
An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"CreateCluster() failed with 0x35. Error: The network path was not found"' failed..
The network path was not found
Click here for help...
http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.2.328.9&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2013-01-16_01-21-06.060_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'EXCHANGE' -Identity 'dag1'
Elapsed Time: 00:00:11
The log file doesn't seem to have much more info but I can include it if anyone thinks it will help. Please let me know what you think, thanks!
Dan

Update: It was the remote registry service being turned off. I enabled it and was able to add my primary exchange server to the dag but the other server now fails with:
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=12) failed with 0x800706d3. Error: The authentication service is unknown"' failed. [Server: exchange.local]
Dan

DAG - Backup failing on 1 DB only with error - The Microsoft Exchange Replication service VSS Writer instance ID failed with error code 80070020 when preparing for a backup of database 'DB012'

Hi Board,
i´ve search across the board, technet and symantec sites but did not found a hint about my problem.
we drive a 2 node DAG (Location1-Ex1-mb1
Location2-exc1-mb1), on SP2 RU4 patchlevel with 40 Databases.
Since some time the backup of one - and only one DB - is failing with these events, logged on the Mailboxserver on which the passive DB is hosted.
Log Name:      Application
Source:        MSExchangeRepl
Date:          28.09.2012 00:37:17
Event ID:      2112
Task Category: Exchange VSS Writer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Location1-Exc1-MB1
Description: The Microsoft Exchange Replication service VSS Writer instance 1ab7d204-609a-4aea-b0a7-70afb0db38de failed with error code 80070020 when preparing for a backup of database 'DB012'.
Followed by
Log Name:      Application
Source:        MSExchangeRepl
Date:
01.10.2012 03:33:06
Event ID:      2024
Task Category: Exchange VSS Writer
Level:         Error
Keywords:      Classic
User:
N/A
Computer:      Location1-Exc1-MB1
Description:
The Microsoft Exchange Replication service VSS Writer (Instance 42916d80-36c1-4f73-86d0-596d30226349) failed with error 80070020 when preparing for a backup.
The backup Application - Symantec Backup Exec 2010 R3 – states, this error
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Check the Windows Event Viewer for details.
Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1).
Symatec suggests within http://www.symantec.com/business/support/index?page=content&id=TECH184095
to restart the MS Exchange Replication Service – BUT the mentioned eventID
8229 isn´t present on any of the both Mailboxservers.
The affected Database is active on Location2-Exc1-Mb1 Server and in an overall healthy state. I found during my research, that below Location2-Exc1-Mb1 Server, there are not removed shadow copies present!
This confuses me, since all Backups are normally taken from the passive copy of a Database.
So my questions to the board are:
* Does anyone is facing similar issues?
* Can someone explain why snapshots are present on the Mailboxserver hosting the Active Database, whilst the errors are logged on the passive one?
-          * Does someone know the conditions, why shadows copies remain and
aren´t removed in a proper manner?
What can cause the circumstance, that only 1 DB is facing such issues?
Any suggestion is welcome!
BR
Markus

Hi Lenora,
I´ve encreases VSS / Exchange Backup Log levels to expert, before starting
those things i´ve all tried now:
- Backup from passive DB (forced within Symantec Backup Exec)
- Backup from active DB (forced within Symantec Backup Exec)
- Backup from passive DB without GRT enabled (forced within Symantec Backup Exec)
- Backup from active DB without GRT enabled(forced within Symantec Backup Exec)
All those attempts failed.
But brought some more details - the backup against the active DB states, that there is still a backup in progress and therefore this backup is cancelled by VSS.
The Solution was, that i´ve needed to restart the Exchange Replication Service on the Mailbox Server hosting the passive DB.
Backups are working again on all DBs!
THX for your replys.
Best regards
Markus

[SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

Hi there!
I have a problem which makes me very angry already :)
I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
LOGS on the second nodes:
Application Log
"Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
Failover Clustering Diagnostic Log
"[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
CMDLET Error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:06:21
MSC-CO-EXC-02V
Failed
Error:
A 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: msc-co-exc-04v.int.krls.ru]
An Active Manager operation failed. 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..
This operation returned because the timeout period expired
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
Elapsed Time: 00:06:21
UPD:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.
Please, help me if you can.

Hi, Jared! Thank you for the reply.
Of course I did it already :) I have new info:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.

Error while adding member to the dag in exchange 2013 sp1

I have Windows Server 2012 Std Edition with Exchange 2013 SP1 and get the following error while adding member to the dag either i do it using EAC or the powershell
Senior Technical Consultant, MDS Computers

When running set-databaseavailabilitygroup Exchange-dag without parameters, it crashes again:
[PS] C:\Windows\system32>Set-DatabaseAvailabilityGroup exchange-dag
WARNING: An unexpected error has occurred and a Watson dump is being generated: Some or all identity references could not be translated. Some or all identity references could not be translated.
+ CategoryInfo : NotSpecified: (:) [Set-DatabaseAvailabilityGroup], IdentityNotMappedException
+ FullyQualifiedErrorId : System.Security.Principal.IdentityNotMappedException,Microsoft.Exchange.Management.Syste
mConfigurationTasks.SetDatabaseAvailabilityGroup
+ PSComputerName : <server>
Also, this is logged in the eventlog:
Watson report about to be sent for process id: 7424, with parameters: E12, c-RTL-AMD64, 15.00.0847.032, w3wp#MSExchangePowerShellAppPool, M.Exchange.Management, M.E.M.C.FileShareWitness.Create, S.S.Principal.IdentityNotMappedException, 3e5c, 15.00.0847.031.
ErrorReportingEnabled: True
Definitely looks like a problem creating the filewitness share.
Frank.

Exchange 2013 DAG with single site and 2 multi-role servers with error "MapiExceptionIllegalCrossServerConnection"

Hi,
I've got a lab with a domain controller and an Hyper-v with on it two multi-role exchange 2013 CU7 servers on W2K12 R2 OS, configured in DAG semplified (but the problem is the same also if I use the classical DAG configuration), a witness server, and a L7
load balancer for the exchange servers.
When I made the test to disable the OWA application pool where I've got the active mailbox database of the user, the balancer in correct manner redirect the session to the other exchange multi-role server, but the client in his OWA session is no more
able to send new mail with the error "Error your request can't be completed rigt now. Please try again later."
The only strange log that I see on the server in the MAPI client access directory where there is the following error message:
2015-01-21T08:00:45.132Z,956,1,/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt,,Microsoft.Exchange.RpcClientAccess.Monitoring.dll,15.0.0.0,Cached,,,,MapiHttp,Client=Microsoft.Exchange.RpcClientAccess.Monitoring,R:4ab7b6c8-54ee-4be3-aa9d-f8c856c4c47c:2,C:MAPIAAAAAOC4+7OCoZOjkqeKuoumlKSEtYO5ibyGs4bc/879z/vD9sX1zP28AwAAAAAAAA==|S:0-mGmHRQ==,OwnerLogon,0x6BB
(rpc::Exception),00:00:00.0310000,"Logon: Owner, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt in database last mounted on Exch2.lab.net",RpcEndPoint: [ServerTooBusyException]
Client is being backed off -> [ClientBackoffException] Mailbox was moved to a different mailbox server. A client needs to retry. -> [IllegalCrossServerConnectionException] Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt.
-> [MapiExceptionIllegalCrossServerConnection] Monitoring mailbox [] with application ID [Client=MSExchangeRPC] is not allowed to make cross-server calls from [Exch1.lab.net] to [Exch2.lab.net] [diag::AAAOAAAA/wAAAAAAAAAAAgAAAAA=],,,[email protected],
The CAS try to access the mailbox on the other server, but without success.
Someone have idea how to solve?
Thanks

Hi Hinte, sorry for the answer delay.
I've run the command you suggest to check the HealthMailbox status, but seems that all are fine:
[PS] C:\Windows\system32>get-Mailbox -Monitoring | ft name, servername
Name ServerName
HealthMailbox7021deb6ae104dadbf52feedfa7fa68b exch1
HealthMailboxb83c9040b32e4d1197f7f54f6709bb7f exch1
HealthMailboxb1c32037890b43fbb2af2efe7c36ba00 exch1
HealthMailbox8d174269b494458daf9ade5099e22845 exch1
HealthMailboxaa7d10f02d2d4cc588243b291ead3e3a exch1
HealthMailboxeb32c30a019f42968a7cbc49a6ac3e65 exch1
HealthMailboxc6ff1d36ba154c5db5411b44718edcbd exch1
HealthMailbox75dc7caa7e8c4a3b812a01b607536d48 exch1
HealthMailbox16c86e512f454e7890b80c180ce19c00 exch1
HealthMailboxc6e447f7dba24d9b913f1dfcabe9f927 exch1
HealthMailbox40fa5a3f2abc4accae6286cd98abc90a exch1
HealthMailbox2712b9544bad4e7b8b671be2cda8cfde exch2
HealthMailboxe2559124da20499386bf8103dcb21e9b exch2
HealthMailbox3264c6078dad45d4a78c56a3afe81df1 exch1
HealthMailboxacacc51eb8bc4717b295ddf0adccf77e exch2
HealthMailbox64c4dd8cddac4c4e8bb7314010e797b1 exch1
HealthMailbox4a92bfa14fdd47fbb27c19513f6d2beb exch2
HealthMailbox465d2a69de93430e84b4d699a88cb0c3 exch1
HealthMailbox97b578e57cd44204820fffa416b25633 exch2
HealthMailboxb411059771db4647bb775c665ec29440 exch1
HealthMailboxf981dde6f4134f839bf41eb0000434e4 exch2
HealthMailboxc33801c7c3b1474f8aa6065249bb4fca exch1
HealthMailbox2282128ed8d14937998212edd15adf20 exch2
HealthMailboxe3d12b756cf545239b38be4607904ae1 exch2
[PS] C:\Windows\system32>
Regarding the test sugested to diable instead the OWA App Pool only the OWA virtual directory, I've not found on IIS the possibility to stop the access to this virtual directory.
Also on exchnage Administration page there is no the possibility to switch off this virtual directory only (or I don't found where is this setting).
Regards

Error when adding MB servers to a DAG in Exchange 2013

Hello,
I have already pre-staged my CNO in active directory. I also have created my DAG in exchange 2013. When I try to add my mailbox servers to my DAG, I receive the following error. I also tried to install the Failover Clustering feature manually, but I received
the same following error. Could you please assist me with this?
<label style="font-weight:bold;">ERROR</label>
A server-side database availability group administrative operation failed. Error Failed to add or remove the Failover-Clustering feature. Error: The request to add or remove features on the specified server failed. Installation of one or more roles, role
services, or features failed. Error: 0x800f0922 .
Pooriya Aghaalitari

Hi,
From the error message, it seems that the issue is related to failover clustering feature.
What’s your Windows version?
Based on
this article, if you're installing the Mailbox server role and you intend for the server to be a member of a database availability group (DAG), you must be running Windows Server 2012 R2 Standard or Datacenter Edition, Windows Server 2012 Standard or Datacenter
Edition, or Windows Server 2008 R2 SP1 Enterprise Edition. Windows Server 2008 R2 SP 1 Standard Edition doesn't support the features needed for DAGs.
Please make sure you meet this requirement.
Best regards,
Belinda Ma
TechNet Community Support

Network DR test causes Exchange DAG network to fail (Failover Cluster Manager reports comms errors)

We have a DAG configured between 2 mailbox servers, one in each of our main data centres. Our comms team recently performed a DR test between our 2 data centres, switiching from the main production link to the backup link. During this outage the Failover
Cluster Manager reported errors, with each mailbox server reporting the other as uncontactable. The Events that were logged include the following:
Isatap interface isatap.{02ADE20A-D5D4-437F-AD00-E6601F7E7A9D} is no longer active. (EventID 4201)
Cluster node 'MAILBOX_SERVER' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the
Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is
connected such as hubs, switches, or bridges. (EventID 1135)
File share witness resource 'File Share Witness (\\WITNESS_SERVER\SHARE_NAME)' failed to arbitrate for the file share '\\WITNESS_SERVER\SHARE_NAME'. Please ensure that file share '\\WITNESS_SERVER\SHARE_NAME' exists and is accessible by the cluster. (EventID
1564)
Cluster resource 'File Share Witness (\\\WITNESS_SERVER\SHARE_NAME)' in clustered service or application 'Cluster Group' failed. (EventID 1069)
The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. Run the Validate a Configuration wizard to check your network
configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges. (EventID 1177)
The Cluster Service service terminated with service-specific error A quorum of cluster nodes was not present to form a cluster. (EventID 7024)
The Microsoft Exchange Information Store service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. (EventID 7031)
Looking at the Cluster Events in the Failover Cluster Manager Snap-In i see a heap of Event ID 47 (cannot activate the DAG databases as the server is not up according to Windows Failover Cluster Service) and:
Node status could not be recorded. This could prevent some network failure logic from functioning correctly. NodeStatus:IsHealthy=True,HasADAccess=True,ClusterErrorOverrideFalse,LastUpdate=5/2/2011 8:25:42 AMUTC Failure:An Active Manager operation failed.
Error: An error occurred while attempting a cluster operation. Error: Cluster API '"ClusterRegSetValue() failed with 0x6be. Error: The remote procedure call failed"' failed.. (EventID 184)
Forcefully dismounting all the locally mounted databases on server 'BACKUP_MAILBOX_SERVER. (EventID 307).
Our Comms team doesn't believe it is a comms issue as they did not log any network communication errors between the servers in the two sites (using icmp). So if it is not a comms issue, how can I configure the Failover Cluster Manager to be resilient to
this type of network failover event.
Thanks
Dan

Isn't it also true that in a stretched DAG with even numbered nodes, the PAM needs to be in the same site as the active DAG node? If the connection between both nodes goes down, and the PAM is in the "passive" site, the primary node will
dismount the databases since it can't check with the PAM to make sure its safe for it to be up.
In a even-numbered node stretched DAG, the PAM changes to the DR/passive site everytime a failover occurs, but doesn't automatically switch back when you reactivate the primary node.

DAG Failover Cluster Service Errors

Hi all,
I have six Exchange 2013 SP1 mailbox servers installed on Server 2008 R2 configured in two seperate DAG's (3 and 3).
I'm using a single NIC on all the servers for replication and server connectivity.
I pre-staged the DAG computer object in AD (and assigned permissions), and configured DNS entries for both (confirmed and resolvable). I also configured the DAG network subnet and DAG IP address via EAC.
At the moment I have active DB's on each server and then a passive copy on each other server, and all instances are healthy.
However, when I look in the WFC on each server, there are a ton of errors in the cluster event logs. All of the nodes show up as green, along with the cluster network, but the cluster shows "The cluster network name is not online".
Cluster resource 'Cluster Name' in clustered service or application 'Cluster Group' failed.
Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'contoso.com' for the following reason:
Unable to obtain the Primary Cluster Name Identity token.
The text for the associated error code is: An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.
The cluster identity 'DAG$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.
I've removed and re-added DNS records, and double checked the permissions on the CNO object. What else can I do?

Hi,
Its not a good idea to add a static DNS-Record for the DAG - Remove it and on the member holding the PAM, run ipconfig /registerdns.
Martina Miskovic
It also turns out that the CNO objects were never re-enabled by Exchange during the DAG creation process. Once I followed your steps above, and manually enabled the object in AD, the DNS entries auto-populated and everything came online.
Thanks for the help!

Exchange2010 SP3 RU4, database in a DAG setup fail error 3145

We are an Exchange 2010 sp3 ru4 running on a hybrid Physical(MB servers) virtual (CAS/HUB servers) with 6 DBs' inonw DAG in a single site with local witness server.
We experienced a failure on one of the DBs wit an error 3145 "
Incremental seeding of database xxx\MB01 encountered an error. A
full reseed is required. Error: The Microsoft Exchange Replication service failed
to determine if the log files in database 'xxx' are divergent from
the source copy on server 'xxx.xxx.local'. Error: There is not enough
space on the disk."
There is no issue with the disk space for the databases or logs or local drives for either MB servers!
I have initiated a suspend and fail for the DB in discussion and initiated a manual seed from the good (only) copy.
I want to know though, which disk is detected here with not enough space? could it be that MSExchangeRepl service couldn't get the disk usage report from AD in due time and decided to fail the copy
and activate the other?
Any pointers would be greatly appreciated.
Ash

Not sure, I've never had to mark a question before. But I looked up the question in the FAQ -
http://social.technet.microsoft.com/wiki/contents/articles/7359.forums-help-faq.aspx#257 and found this:
How do I indicate a post answered my question?
To mark a post as answer, click Mark as Answer beneath the post. You can unmark a post as answer by clicking Unmark as the Answer.
JAUCG - Please remeber to mark replies as helpful if they were or as answered if I provided a solution.

Adding server in DAG failing with error Error: Cluster API failed: "AddClusterNode() (MaxPercentage=25) failed with 0x800706ba. Error: The RPC server is unavailable

Hi, Below is teh environments
DC: Win 2008 R2 SP1
Exchange Server OS: Win 2012 R2 Std
Exchange : 2013 SP1 Ent
Two Servers with CAS+MB role, already part of one DAG. I am trying to add one new server in existing DAG. The installation of exchange 2013 competed successfully. However when i am adding it to the existing DAG, the below error is coming. Please help
to solve the issue. Thanks in advance.
A server-side database availability group administrative operation failed with a transient error. Please try the operation again. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "AddClusterNode() (MaxPercentage=25)
failed with 0x800706ba. Error: The RPC server is unavailable" [Server: cluster owner FQDN]
Manu

Hi Manu,
As Deepak mentioned, please try to enable IPv6 on all member servers first.
Based on my research, In Microsoft Exchange Server 2013, IPv6 is supported only when IPv4 is also installed and enabled. If Exchange 2013 is deployed in this configuration, and the network supports IPv4 and IPv6, all Exchange servers can send data to and
receive data from devices, servers, and clients that use IPv6 addresses.
Please also configure or disable Firewall to allow the connection.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Mavis Huang
TechNet Community Support

DAG DB copy error

Exchange 2013
When I try to add a DB copy I get this error:
error
The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server 'server1.domain.local'. Hresult: 0xc7ff1004. Error: Error returned from an ESE function call (-1305).
[Database: MBX1, Server: server2.domain.local]
I do see the proper path created on server 2

Hi,
First, please check the mailbox database status and please restart the Microsoft Exchange Replication service to check the result.
Generally, it is recommended to have at least two networks, one for MAPI network and one for Replication network. I recommend you specify the network you want to use for seeding to check the result. You can use the Network parameter when running the Update-MailboxDatabaseCopy
cmdlet and specify the DAG network that you want to use.
Besides, please check the application log to see if there is any related events.
If possible, please create a new test database and check if you can add the copy.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

When adding a database copy to a server in the dag I receive the following error message

I have tried force replication, but didn't work. any suggestion on this
The wizard could not complete . clokc finish to close this wizard.
elapsed time 00:02:52
summary 1 item 0 succeeded, 1 failed
EX01-DB01
Error:
A source-side operation failed. Error An error occurred while running prerequisite checks. Error: the specified database isn't
configured for replication and therefore cannot be used to perform seed operations. Database:EX01-DB01,
Server:XXXXXXXXX
Warning:
Active directory couldn't be updated in HeadOffice site affected by the change to EX01-DB01; it won't be completely usable
until after active directory replication occurs.
Exchange management shell command attempted
Add-MAILBOXDATABASECOPY. Identiy EX01-DB01 -Mailboxserver HUTAEX01'
ActivationPreference '3'

After Add-MailboxDatabaseCopy command fails, do you see if the DatabaseCopy added to the server or?
I have seen this issue, it fails with above error, but after sometime it shows the copy added to the server.
Check the event log for more information also, any event related to AD!!!
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Unable to send to external email recipients - Multi Tenant Exchange 2013 - MultiRole servers in DAG

Greetings all, I hope someone can help.
I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
Internal mail flow is fine (external email addresses can send to the domain).
External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
There are two multi-role Exchange servers that are members of the DAG.
I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
No SSL certificates have been purchased or installed yet.
Exchange URLs have not been changed since default configuration at install.
OWA and ECP works both internal and external.
External DNS works with SPF and PTR records correctly configured
Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
Send Connectors are the default ones created during install. Receive connector is standard configuration with - * -
When sending email to an external address, I receive a failure notice
ServerName.test.corp.int gave this error:
Unable to relay
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
More Info -
ServerName.test.corp.int
Remote Server returned '550 5.7.1 Unable to relay'
I have been troubleshooting this for many hours with no progress.
I have created new Send Connectors for the server that is advising that it is unable to relay, but they have all failed.
I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
I am at a loss as to why I can't send out with the default configuration. I would assume that email would flow out without any changes, but this does not happen.
Can someone please assist before I lose my sanity.
Thanks in advance,
Terry

Greetings all, I hope someone can help.
I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
Internal mail flow is fine.
Incoming mail from external senders is also fine. -
external email addresses can send to the domain).
External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
There are two multi-role Exchange servers that are members of the DAG.
I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
No SSL certificates have been purchased or installed yet.
Exchange URLs have not been changed since default configuration at install.
OWA and ECP works both internal and external.
External DNS works with SPF and PTR records correctly configured
Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
Receive Connectors are the default ones created during install. Send connector is standard configuration with - * -
When sending email to an external address, I receive a failure notice
ServerName.test.corp.int gave this error:
Unable to relay
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
More Info -
ServerName.test.corp.int
Remote Server returned '550 5.7.1 Unable to relay'
I have been troubleshooting this for several days with no progress.
I have created new Receive Connectors for the server that is advising that it is unable to relay, but they have all failed.
I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
Even more info - Further troubleshooting -
I found my one of my Exchange servers had an extra NIC. I have since added a second NIC to the other server, so now both Exchange servers have dual NICs. I removed the DAG cleanly and recreated the DAG from scratch, using this link -
hxxp://careexchange.in/how-to-create-a-database-availability-group-in-exchange-2013/
The issue still exists, even with a newly created DAG. I also found that the Tenant Address Books were not 'applied'. I applied them but still no resolution
I think the issue is related to multi-tenant configuration even though the error says that it can't relay. The unable to relay message can appear when sending from a domain that the Organization does not support. Like trying to email as [email protected]
when you domain name is apple.com - But through extensive research I still can't resolve the issue.
Can someone please assist before I lose my sanity.
Thanks in advance,
Terry

DAG Error

Similar Messages

Maybe you are looking for