Fail to add mailbox database copy

Hello,
When I am trying to add a mailbox database copy in DAG, I receive the following error:
error
The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to notify source server 'mbx1.domain.local' about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file.
when viewing details of the passiv, error message shows:
The database file wasn't found after log replay. The copy will be set to failed
Please help. Thanks

Hi,
Please use the Get-MailboxDatabaseCopyStatus cmdlet to check the health and status of mailbox database copy.
Please dismount and remount the active mailbox database, remove the failed passive database copy and then add it again to check the result.
Besides, please check the application log to see if there is any related events.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

Cannot add mailbox database copy to DR site - .edb file not getting created

I have a DR site setup that I want copies of 4 of my mailbox databases. 3 of the mailbox databases copied over successfully but the last and largest one which is really not that large 69Gbs keeps failing when i Update the database copy. Seems
to not be creating the .edb file. Is there another way to get the .edb file over to the server, possibly manually copying it then doing and update database copy? I have my backups turned off on all the servers that have the mailbox role on it now
thinking that was causing some issues with the database copy? Any suggestions is appreciated, thanks.
Michael Duhon

Yes manually copy the edb file and paste them in the DR server . Then try to update with for the incremental of database copy. Verify the database is clean shutdown that you are moving to the DR site.
What error message it throws when you performing update the database copy
Exchange Queries

Exchange Add Mailbox Database Copy fails.

I'm recovering from a server failure on my Exchange System and while I've been able to rebuild the server an integrate it into the Exchange System and the DAG. When I attempt to replicate any of the databases, it fails. It creates a directory on the new Exchange server in the right place, but the database isn't there and I get the following error:--------------------------------------------Summary: 1 item(s). 0 succeeded, 1 failed.Elapsed time: 00:00:23AM.ScottFailedError:A source-side operation failed. Error An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server 'FRANKLIN2.domain.com'. Hresult: 0x80070057. Error: An unexpected error occurred. Error (0x80070057).. [Database: AM.Scott, Server: FRANKLIN0C.domain.com]Failed to open a log truncation context to source server...
This topic first appeared in the Spiceworks Community

Hi Belinda,
Thanks for the response. I am holding off on using Eseutil or Isinteg for now as I may have finally found the problem.
I was reading another forum yesterday where someone else was getting many of the same errors and everyone responding was telling them the same thing, to check the database as it seemed to have some corruption. Then there was one post at the very bottom where
a guy said he had the same problems but found it was an incompatibility with Exchange 2010 and the Windows Serve Backup Command-line Tools for Server 2008. He removed the Command-line Tools and the problem was resolved. Since we do not use the Windows Serve
Backup, we use Backup Exec, I decided to give it a try. I removed the Command-line Tools and reseeded the database. It has been running since about 12:30 PM yesterday with no errors at all. I'm not claiming victory yet as I stated in my original post that
it has at times run for up to 5 days before failing. I will monitor it for the next week and keep my fingers crossed that the issue has been resolved. I will report back if it fails before then and if not I will consider the issue resolved and post to
the thread.
If this does in fact turn out to be the solution it is just another instance of Microsoft dropping the ball as I was only able to find this mentioned once on their website in a thread about Exchange logs not truncating. I would find it rather annoying their
Server backup software is incompatible with their Mail program and even more annoying that they have not acknowledged the issue. I have been fighting this for months and only found the solution by a stroke of luck. I will update accordingly.
Many thanks,
Gerard

Failed to Manually Seed the Mailbox Database Copy on Exchange 2013

Hi,
I tried to manually seed the mailbox database copy via exchange shell by run this command
Update-MailboxDatabaseCopy –Identity “DB_name\Server” -sourceserver "Name Server" –DeleteExistingFiles.
However, i got the error message whereas shown below.
A parameter cannot be found that matches parameter name 'identity'.
    + CategoryInfo          : InvalidArgument: (:) [Update-MailboxDatabaseCopy], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Update-MailboxDatabaseCopy
    + PSComputerName        : XXXX.abc.XXX
Any ideas?

I hope database is in suspended state and not in failed state.
Make sure EMS is running As Administrator.
http://technet.microsoft.com/en-us/library/dd335201(v=exchg.150).aspx
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
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.

Remove mailbox database copy from DAG

Hi There,
We would like to remove the mailbox database copy from our exchange server as we are lack of the space on our fixed vhd and we hope to be able to free about 100GB from the passive database copies as we have deployed DAG. is there any guidelines or procedures
to safely remove the database copies? currently, we have 4 mailbox servers, HQMB01, HQMB02, SSMB01, and SSMB02. HQMB01 and HQMB02 is already part of DAG members by itself. however, on ssmb01 and ssmb02, we also add in HQMB01 and HQMB02 as the DAG member,
thus they can fail over to HQMB01 or HQMB02 if their server have issue. in this situation, SSMB01 and SSMB02 passive copies is also inside our HQMB01 and HQMB02. As the our HQMB01 and HQMB02 is lack of the disk space and we would like to remove SSMB01
and SSMB02 from the DAG, thus we could remove the passive database copies. The following is the picture of the activation preference for all servers. what is the procedures and the guidelines to remove mailbox database copy and also remove the server from
the DAG members? we are quite confuse and worry that after we are removing wrongly and cause the active database to lost as we understand that there is replication happening between them. as we have 4 mailbox servers from which server we should perform
the task? Wish to get some advises from the exchange guru from this forum. we are on exchange server 2010 sp1 and windows server 2008 R2.Thanks so much.
Name                 : HQDB01
Servers              : {HQMB01, HQMB02}
ActivationPreference : {[HQMB01, 1], [HQMB02, 2]}
ReplayLagTimes       : {[HQMB01, 00:00:00], [HQMB02, 00:00:00]}
TruncationLagTimes   : {[HQMB01, 00:00:00], [HQMB02, 00:00:00]}
Name                 : HQDB02
Servers              : {HQMB02, HQMB01}
ActivationPreference : {[HQMB02, 1], [HQMB01, 2]}
ReplayLagTimes       : {[HQMB02, 00:00:00], [HQMB01, 00:00:00]}
TruncationLagTimes   : {[HQMB02, 00:00:00], [HQMB01, 00:00:00]}
Name                 : SSDB01
Servers              : {SSMB01, SSMB02, HQMB01, HQMB02}
ActivationPreference : {[SSMB01, 1], [SSMB02, 2], [HQMB01, 3], [HQMB02, 4]}
ReplayLagTimes       : {[SSMB01, 00:00:00], [SSMB02, 00:00:00], [HQMB01, 00:00:00], [HQMB02, 00:00:00]}
TruncationLagTimes   : {[SSMB01, 00:00:00], [SSMB02, 00:00:00], [HQMB01, 00:00:00], [HQMB02, 00:00:00]}
Name                 : SSDB02
Servers              : {SSMB02, SSMB01, HQMB01, HQMB02}
ActivationPreference : {[SSMB02, 1], [SSMB01, 2], [HQMB01, 3], [HQMB02, 4]}
ReplayLagTimes       : {[SSMB02, 00:00:00], [SSMB01, 00:00:00], [HQMB01, 00:00:00], [HQMB02, 00:00:00]}
TruncationLagTimes   : {[SSMB02, 00:00:00], [SSMB01, 00:00:00], [HQMB01, 00:00:00], [HQMB02, 00:00:00]}

Hi Exchange Guru,
thanks so much for the prompt response..i have few queries to ask following your guidelines above:
1. from the show result above, I am still confuse which server that I should go to remove as this is involving 4 database copies. from what I understand from the truncation or replay lag times of SSDB01 and SSDB02, I can see that HQMB01 and HQMB02 are on
the third and fourth preference, which means that SSDB01 and SSDB02 will be able to failover to each of them when there is a failure and it cause the passive copies of both of SSDB01 and SSDB02 to be stored in the HQMB01 and HQMB02. what my purpose
is to remove both SSDB01 and SSDB02 passive copies in HQMB01 and HQMB02. in this case, should I login to SSDB01 or SSDB02 mailbox servers to perform the removal with your guidelines above?
2. is the command as below:
Remove-MailboxDatabaseCopy -Identity SSDB01\HQMB01 -Confirm:$False
Remove-MailboxDatabaseCopy -Identity SSDB01HQMB02 -Confirm:$False
Remove-MailboxDatabaseCopy -Identity SSDB02\HQMB01 -Confirm:$False
Remove-MailboxDatabaseCopy -Identity SSDB02\HQMB02 -Confirm:$False
will this cause the risk either of my HQDB01, HQDB02, SSDB01, and SSDB02 active copies accidentally being removed? I am sorry that I am a bit naggy and always want a confirmation as this is very critical and I must be super careful.
3. If after the removal successful, when is the best time to go to the drive where the passive copies stored and remove them so I can clear some space on my disk? and is it just as simple by going to the drive and do a folder file deletion manually?
because I just worry when I delete the file and the server is still replicating between each other, which will cause even corruption to the active database.
4. From point 3, you mention about when the server is empty. what do you mean by that? do you mean that when the passive copies are no more there? and what command that I used to check?
5. From point 4, is removing the server from DAG the last step to be performed? yes, I want to remove them from DAG, thus will left only HQMB01 and HQMB02 as one DAG and SSMB01 and SSMB02 as one DAG.
Thank so so much for your patient and attention.
Regards,
Henry

Moving the mailbox database copy from one exchange server to another exchange server 2010 DAG

Hello Team
is it possible to the move the passive copy of database and logs from one server to another exchange server in the same DAG with out removing and deleting the mailbox database copies in exchange 2010
normaly procedure is
Remove the mailbox database copies and manually delete the .edb files and logs from the physical location and re-add the mailbox database copy to the new server in the DAG.
is that any way to achieve to move the passive database copy to another exchange 2010 server in the same DAG ?

From your note, you appear to have a two-member DAG (with a server hosting your active database, and a second hosting the passive copy), and you want to move your passive database copy from the current passive server to another. Your note
about what "the normal procedure is" isn't 100% correct - there are many ways to handle this task, and all can be considered "normal". Why not just add the third server to the DAG and
add a database copy on that third server? Once it is fully seeded, you can remove the current passive copy. This way, you never lose your redundancy.
Yes i can add the third and fourth serve in DAG , but i cannot add the mailbox database copies to the 3rd and 4th mailbox server in DAG as am using RTM version of exchange 2010 which is allowing to have only 5 database inclding mailbox datbase copies
and also currently my lab setup is two member dag (with a server hosting your active database,
and a second hosting the passive copy) in the same site named SITE A
and recently i have created new SITE B and included the 3rd and 4th DAG members in the same DAG
i want the mailbox database copies from the mailbox server database in SITE A to
Mailbox server database in SITE B as passive copy
That is why i want to move the mailbox database without deleting / removing it manually
Hope you understand my situation!

Seed mailbox database copy through replication network (DAG members on different subnets in different sites)

Good afternoon
I currently operate a two node DAG in our primary site supporting one mailbox database. I plan to introduce a third DAG node in our datacenter which is in a different Active Directory site. Both current DAG members replicate over a dedicated replication
network to keep the traffic separate from the MAPI traffic. The third DAG member will also have a dedicated replication network adapter (of course, on a different subnet). Ideally I would like to seed the database at a time of my choosing, rather than at the
moment I add the mailbox database copy (I know how to achieve this), but I would like to specify which network the data replicates over.
According to the following (see below link) under the 'Seeding and Networks' section as my two DAG members will be on different subnets in different sites Exchange will make the decision to use the MAPI network adapters of the target and source server.
'If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.'
http://technet.microsoft.com/en-us/library/dd335158%28v=exchg.150%29.aspx
Am I able to force Exchange to use the replication network adapters of both source and target server when I initiate the seeding process? I have a 200+ GB mailbox database that will need to replicate over a 100Mbps internet connection to our secondary
site and I would like to keep that traffic to the replication network I have configured.
Any insight would be helpful.

Hi,
If you want to specify the networks for seeding, you can use the
Network parameter when running the
Update-MailboxDatabaseCopy cmdlet and specify the DAG networks that you want to use.
If you don't use the Network parameter, then the system uses the following default behavior for selecting a network to use for the seeding operation:
If the source server and target server are on the same subnet and a replication network has been configured that includes the subnet, the replication network will be used.
If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.
If the source server and target server are in different datacenters, the client (MAPI) network will be used for seeding.
So please use the Update-MailboxDatabaseCopy cmdlet with
NetWork parameter to specify which DAG network should be used for seeding.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Mailbox Database Copy Status Failed

We have 2 Exchange 2010 servers. We run a DAG. Recently I have noticed that database copy DB2 which is located on Exch-1 is showing "Failed". Database copy DB1 which is located on Exch-2 is showing Healthy. I searched online
for information regarding the issue with the failed database copy. I found information that led me to run these commands.
Suspend-MailboxDatabaseCopy -Identity “Mailbox Database XXXXX\Server Name”
Update-MailboxDatabaseCopy -Identity “Mailbox Database XXXXX\Server Name” -DeleteExistingFiles
It went thru the seeding process and completed but the database copy still shows "Failed". Copy Q Length is 19. I have refreshed the console. What else do I need to do to correct this? I did recently shut down Exch-2 server
for maintenance. thanks

Hi,
It's glade to hear the good news. Thanks for your updating.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Microsoft Exchange Server/Exchange 2010/Mailbox/Database Copy Mounted

Good Morning everyone!!!
I Have SCOM 2007 R2 CU5 Envoirnment and i am monitoring Microsoft Exchange 2010 SP1 Messaging infrastracture,
I have Microsoft Exchange 2010 SP1 Monitoring MP, MP version is 14.2.71.0.
Case:-
When exchange is having issue with DAG, SCOM monitoring rule:- KHI: The database copy is not mounted on the local server. Another database copy may be mounted on a different server.
is generating the alert but alert Description is only " _ef4a8515_1cc0_48a9_aa12_92ba059a6eae_ " and rest of the things are blank
and because of this ticketing team is unable to process these alerts,
Impact:-
Whenever DAG is unavailable, messaging team is not getting notification and because of this. Exchange services are failing down,
Does anyone having this kind of issues on their exchange environment?
I am looking solution for this issue, please let me know if anyone is aware about this.
Regards, Ganesh M <!> Microsoft MPN - Member =========================================================== Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer
your question. This can be beneficial to other community members reading the thread.

Does anyone has updated information regarding Exchange 2010 DAG monitoring fix, <o:p></o:p>
As i see there was exchange MP release on 31st Aug 2012
ID
Name
Targets
_ef4a8515_1cc0_48a9_aa12_92ba059a6eae_
KHI: The database copy is not mounted on the local server. Another database copy may be mounted on a different server.
Root Management Server
_EF51D339_22C5_49b3_8B6B_25002BE31D4A_
KHI: Retry Mailbox Delivery Queue Length - sustained for 90 minutes - Red(>1) - Hub Transport.
Root Management Server
_93558cf0_e063_45b1_b57a_0d4b53e0d615_
KHI: The Microsoft Exchange Information Store service (MSExchangeIS) isn't running.
Root Management Server
My monitoring is affected for these rules which i mentioned below, here alerts
information is shown as rule ID instead of Rule name. and we don’t get alert description
for above rules when the generate alerts.<o:p></o:p>
Response would be appreciated <o:p></o:p>
Regards, Ganesh M <!> Microsoft MPN - Member =========================================================== Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer
your question. This can be beneficial to other community members reading the thread.

Fail to add Mailbox server to DAG

I'm Setting up Exchange Server 2013 Mailing system, the schema that i'm deploying includes two CAS servers : 3S-CAS1 and 3S-CAS2 for load balancing access authentication;
and two mailbox servers 3S-MBX1 and 3S-MBX2. A File share server 3S-FW is used as a witness for the DAG . the Exchange Trusted Subsystems AD Group is added as member ofthe File witness local administrators. A computer account EDAG is created on AD and
then disabled as recommended.
my Network configuration is the following :
3S-CAS1 : 172.16.192.7
3S-CAS2 : 172.16.192.8
3S-MBX1: 172.16.192.9 (prod trafic)
 10.0.0.1 (replication interface)
3S-MBX2: 172.16.192.10 (prod interface)
 10.0.0.2 (replication interface)
EGAG : 172.16.192.20
the issue is when i try to create a DAG (Database Availability Group) i'm getting the following error message
[PS] C:\Windows\system32>New-DatabaseAvailabilityGroup -Name EDAG -WitnessServer 3S-FW -WitnessDirectory c:\shares\fws_dag -DatabaseAvailabilityGroupIpAddresses 172.16.192.20
WARNING: Unable to access file shares on witness server '3S-FW.3s.com.tn'. Until this problem is corrected, the database availability group may be more vulnerable to failures. You can use the Set-DatabaseAvailabilityGroup cmdlet to try the operation again.
Error: The network path was not found
After that i'm giving up using witness server since creating a DAG without specifying a witness server would elect one from CAS servers that do not contain the mailbox role.
[PS] C:\Windows\system32>New-DatabaseAvailabilityGroup -Name EDAG -DatabaseAvailabilityGroupIpAddresses 172.16.192.20
Name Member Servers
Operational Servers
EDAG {}
and all things seems to be ok. but when adding the first Mailbox server (3S-MBX1) to the DAG i get the following error :

[PS] C:\Windows\system32>Add-DatabaseAvailabilityGroupServer -Identity EDAG -MailboxServer 3S-MBX1
WARNING: The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-02-11_14-35-14.226_add-databaseavailabiltygroupserver.log".
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 0x57. Error: The parameter is incorrect"' failed.. [Server: 3S-MBX1.3s.com.tn]
 + CategoryInfo : InvalidArgument: (:) [Add-DatabaseAvailabilityGroupServer], DagTaskOperationFailedException
 + FullyQualifiedErrorId : [Server=3S-MBX1,RequestId=d774dd8b-0d03-41a1-a3d9-5d2a09432e58,TimeStamp=11/02/2014 14:35:22] E84D00B4,Microsoft.Exchange.Management.SystemConfigurationTasks.AddDatabaseAvailabilityGroupServer
 + PSComputerName : 3s-mbx1.3s.com.tn
The error indicates that erors may result from incorrectly configured static addresses. i joined the log file related to the DAG tasks and the first mailbox server ip configuration.
<fieldset class="mimeAttachmentHeader"><legend class="mimeAttachmentHeaderName">dagtask_2014-02-11_14-35-14.226_add-databaseavailabiltygroupserver.log</legend></fieldset>
add-databaseavailabiltygroupserver started on machine 3S-MBX1.
[2014-02-11T14:35:14] add-dagserver started
[2014-02-11T14:35:14] commandline: $scriptCmd = {& $wrappedCmd @PSBoundParameters }
[2014-02-11T14:35:14] Option 'Identity' = 'EDAG'.
[2014-02-11T14:35:14] Option 'MailboxServer' = '3S-MBX1'.
[2014-02-11T14:35:14] Option 'DatabaseAvailabilityGroupIpAddresses' = ''.
[2014-02-11T14:35:14] Option 'WhatIf' = ''.
[2014-02-11T14:35:14] Process: w3wp w3wp.exe:612.
[2014-02-11T14:35:14] User context = 'NT AUTHORITY\SYSTEM'.
[2014-02-11T14:35:14] Member of group 'Everyone'.
[2014-02-11T14:35:14] Member of group 'BUILTIN\Users'.
[2014-02-11T14:35:14] Member of group 'NT AUTHORITY\SERVICE'.
[2014-02-11T14:35:14] Member of group 'CONSOLE LOGON'.
[2014-02-11T14:35:14] Member of group 'NT AUTHORITY\Authenticated Users'.
[2014-02-11T14:35:14] Member of group 'NT AUTHORITY\This Organization'.
[2014-02-11T14:35:14] Member of group 'BUILTIN\IIS_IUSRS'.
[2014-02-11T14:35:14] Member of group 'LOCAL'.
[2014-02-11T14:35:14] Member of group 'IIS APPPOOL\MSExchangePowerShellFrontEndAppPool'.
[2014-02-11T14:35:14] Member of group 'BUILTIN\Administrators'.
[2014-02-11T14:35:14] Updated Progress 'Validating the parameters.' 2%.
[2014-02-11T14:35:14] Working
[2014-02-11T14:35:14] Mailbox server: value passed in = 3S-MBX1, mailboxServer.Name = 3S-MBX1, mailboxServer.Fqdn = 3S-MBX1.3s.com.tn
[2014-02-11T14:35:14] LogClussvcState: clussvc is Stopped on 3S-MBX1.3s.com.tn. Exception (if any) = none
[2014-02-11T14:35:14] The IP addresses for the DAG are (blank means DHCP): 172.16.192.20
[2014-02-11T14:35:14] Looking up IP addresses for EDAG.
[2014-02-11T14:35:14] EDAG = [ 172.16.192.20 ].
[2014-02-11T14:35:14] Looking up IP addresses for 3s-mbx1.
[2014-02-11T14:35:14] 3s-mbx1 = [ ::1, 172.16.192.9, 10.0.0.1 ].
[2014-02-11T14:35:14] Looking up IP addresses for 3S-MBX1.3s.com.tn.
[2014-02-11T14:35:14] 3S-MBX1.3s.com.tn = [ ::1, 172.16.192.9, 10.0.0.1 ].
[2014-02-11T14:35:14] DAG EDAG has 0 servers:
[2014-02-11T14:35:14] Updated Progress 'Checking if Mailbox server '3S-MBX1' is in a database availability group.' 4%.
[2014-02-11T14:35:14] Working
[2014-02-11T14:35:14] GetRemoteCluster() for the mailbox server failed with exception = An Active Manager operation failed. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"OpenCluster(3S-MBX1.3s.com.tn) failed with 0x6d9. Error: There are no more endpoints available from the endpoint mapper"' failed.. This is OK.
[2014-02-11T14:35:14] Ignoring previous error, as it is acceptable if the cluster does not exist yet.
[2014-02-11T14:35:14] DumpClusterTopology: Opening remote cluster EDAG.
[2014-02-11T14:35:14] DumpClusterTopology: Failed opening with Microsoft.Exchange.Cluster.Replay.AmGetFqdnFailedNotFoundException: An Active Manager operation failed with a transient error. Please retry the operation. Error: The fully qualified domain name for node 'EDAG' could not be found.
at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerNameCache.<>c__DisplayClass1.<ResolveFqdn>b__0(Object param0, EventArgs param1)
at Microsoft.Exchange.Cluster.ActiveManagerServer.AmHelper.RunADOperationEx(EventHandler ev)
at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerNameCache.ResolveFqdn(String shortNodeName, Boolean throwException)
at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerNameCache.GetFqdn(String shortNodeName, Boolean throwException)
at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerName..ctor(String serverName, Boolean throwOnFqdnError)
at Microsoft.Exchange.Management.SystemConfigurationTasks.DumpClusterTopology..ctor(String nameCluster, ITaskOutputHelper output)
[2014-02-11T14:35:14] Dumping the cluster by connecting to: EDAG.
[2014-02-11T14:35:14] DumpClusterTopology: Not dumping, since the cluster could not be contacted.
[2014-02-11T14:35:14] The new server (3S-MBX1) is not a member of a cluster, nor are the other servers (if there are any other servers).
[2014-02-11T14:35:14] The computer account EDAG does not exist.
[2014-02-11T14:35:14] According to GetNodeClusterState(), the server 3S-MBX1 is NotConfigured.
[2014-02-11T14:35:14] InternalValidate() done.
[2014-02-11T14:35:14] Updated Progress 'Adding server '3S-MBX1' to database availability group 'EDAG'.' 6%.
[2014-02-11T14:35:14] Working
[2014-02-11T14:35:14] Connecting to server '3S-MBX1.3s.com.tn' via WMI...
[2014-02-11T14:35:14] Fetching the network adapters and including the ones without default gateways.
[2014-02-11T14:35:14] 3S-MBX1.3s.com.tn has an address: 10.0.0.1/24 default gateway(s)=<none> [valid]
[2014-02-11T14:35:14] IP address derived that's suitable for clustering DHCP/IPv6: 10.0.0.0/24.
[2014-02-11T14:35:14] 3S-MBX1.3s.com.tn has an address: 172.16.192.9/24 default gateway(s)=172.16.192.254 [valid]
[2014-02-11T14:35:14] IP address derived that's suitable for clustering DHCP/IPv6: 172.16.192.0/24.
[2014-02-11T14:35:14] The address 172.16.192.20 falls under the network (172.16.192.0/24).
[2014-02-11T14:35:14] Updated Progress 'Forming cluster named 'EDAG' on server '3S-MBX1'.' 8%.
[2014-02-11T14:35:14] Working
[2014-02-11T14:35:14] Forming cluster named 'EDAG' on server '3S-MBX1'. The cluster address is/are [172.16.192.20], and the cluster network prefix length is/are [24].
[2014-02-11T14:35:22] The following log entry comes from a different process that's running on machine '3S-MBX1'. BEGIN
[2014-02-11T14:35:22] [2014-02-11T14:35:14] Updated Progress 'Forming cluster named 'EDAG' on server '3s-mbx1'.' 2%.
[2014-02-11T14:35:14] Working
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseInitialize, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 5, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseInitialize, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 5, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 10, szObjectName = 3S-MBX1.3s.com.tn, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 10, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 15, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 15, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusterNameAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 21, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusterNameAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 21, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 26, szObjectName = EDAG in organizational unit CN=Computers,DC=3s,DC=com,DC=tn, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 26, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNetft, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 31, szObjectName = 3S-MBX1.3s.com.tn, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNetft, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 31, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusDisk, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 36, szObjectName = 3S-MBX1.3s.com.tn, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusDisk, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 36, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusSvc, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 42, szObjectName = 3S-MBX1.3s.com.tn, dwStatus = 0x0 )
[2014-02-11T14:35:15] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusSvc, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 42, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:15] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseStartingClusSvc, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 47, szObjectName = 3S-MBX1.3s.com.tn, dwStatus = 0x0 )
[2014-02-11T14:35:15] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseStartingClusSvc, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 47, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:15] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFormingCluster, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 52, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFormingCluster, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 52, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseAddClusterProperties, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 57, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseAddClusterProperties, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 57, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateResourceTypes, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 63, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateResourceTypes, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 63, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateGroups, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 68, szObjectName = Cluster Group, dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateGroups, ePhaseType = ClusterSetupPhaseContinue, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 68, szObjectName = Available Storage, dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateGroups, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 68, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateIPAddressResources, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 73, szObjectName = Cluster IP Address, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateIPAddressResources, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 73, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateNetworkName, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 78, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateNetworkName, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 78, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 84, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 84, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusterNameAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 89, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusterNameAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 89, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 94, szObjectName = EDAG in organizational unit CN=Computers,DC=3s,DC=com,DC=tn, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseFatal, dwPercentComplete = 94, szObjectName = EDAG in organizational unit CN=Computers,DC=3s,DC=com,DC=tn, dwStatus = 0x57 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseFatal, dwPercentComplete = 94, szObjectName = å° ÅŠ, dwStatus = 0x57 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 94, szObjectName = Cluster Group, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseContinue, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 94, szObjectName = Cluster IP Address, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseContinue, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 94, szObjectName = 3S-MBX1.3s.com.tn, dwStatus = 0x0 )
[2014-02-11T14:35:22] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseContinue, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 94, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:22] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 94, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:22] The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-02-11_14-35-14.226_add-databaseavailabiltygroupserver.log".
[2014-02-11T14:35:22] WriteError! Exception = Microsoft.Exchange.Cluster.Replay.DagTaskOperationFailedException: 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 0x57. Error: The parameter is incorrect"' failed.. ---> 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 0x57. Error: The parameter is incorrect"' failed. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
--- End of inner exception stack trace ---
at Microsoft.Exchange.Cluster.ClusApi.AmCluster.CreateExchangeCluster(String clusterName, AmServerName firstNodeName, String[] ipAddress, UInt32[] ipPrefixLength, IClusterSetupProgress setupProgress, IntPtr context, Exception& failureException, Boolean throwExceptionOnFailure)
at Microsoft.Exchange.Cluster.ClusApi.ClusterFactory.CreateExchangeCluster(String clusterName, AmServerName firstNodeName, String[] ipAddress, UInt32[] ipPrefixLength, IClusterSetupProgress setupProgress, IntPtr context, Exception& failureException, Boolean throwExceptionOnFailure)
at Microsoft.Exchange.Cluster.Replay.DagHelper.CreateDagCluster(String clusterName, AmServerName firstNodeName, String[] ipAddresses, UInt32[] netmasks, String& verboseLog)
--- End of inner exception stack trace (Microsoft.Exchange.Cluster.Replay.AmClusterApiException) ---
at Microsoft.Exchange.Cluster.Replay.DagHelper.ThrowDagTaskOperationWrapper(Exception exception)
at Microsoft.Exchange.Cluster.Replay.DagHelper.CreateDagCluster(String clusterName, AmServerName firstNodeName, String[] ipAddresses, UInt32[] netmasks, String& verboseLog)
at Microsoft.Exchange.Cluster.ReplayService.ReplayRpcServer.<>c__DisplayClass40.<RpcsCreateCluster>b__3f()
at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.RunRpcServerOperation(String databaseName, RpcServerOperation rpcOperation)
--- End of stack trace on server (3S-MBX1.3s.com.tn) ---
at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.ClientRethrowIfFailed(String databaseName, String serverName, RpcErrorExceptionInfo errorInfo)
at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.RunCreateCluster(AmServerName rpcServerName, String clusterName, AmServerName firstNode, String[] ipaddrs, UInt32[] netmasks, String& verboseLog)
at Microsoft.Exchange.Management.SystemConfigurationTasks.AddDatabaseAvailabilityGroupServer.FormCluster()
[2014-02-11T14:35:22] Updated Progress 'Done!' 100%.
[2014-02-11T14:35:22] COMPLETED
add-databaseavailabiltygroupserver explicitly called CloseTempLogFile().
<fieldset class="mimeAttachmentHeader"><legend class="mimeAttachmentHeaderName">ip-config.txt</legend></fieldset>
C:\Windows\system32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : 3S-MBX1
Primary Dns Suffix . . . . . . . : 3s.com.tn
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : 3s.com.tn
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
Physical Address. . . . . . . . . : 00-50-56-83-21-13
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.192.9(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.192.254
DNS Servers . . . . . . . . . . . : 172.16.192.6
172.20.10.21
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection #3
Physical Address. . . . . . . . . : 00-50-56-83-22-C9
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.0.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
Physical Address. . . . . . . . . : 02-3D-2A-2B-56-56
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{E3787791-A3D8-43D2-97F5-C941B8532445}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{C041FA54-1E89-40DA-B8AE-ABE8DF80208E}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Hi,
Please check if cluster name object (CNO) setting is correct. Make sure you have pre-staged the CNO object if you are running Windows Server 2012 for the DAG members. When you add the first node to DAG, you should assign Full Control permissions to the CNO.
For more details about this, you can refer to the following article.
Pre-Stage the Cluster Name Object for a Database Availability Group
http://technet.microsoft.com/en-us/library/ff367878(v=exchg.150).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Cannot Adding Mailbox Server for Database Copy for Exchange 2013 SP1

Before I upgraded to 2013 SP1 everything works find but after I upgrade to SP1 I cannot add database copy. the details are...
I have 2 sites
Site 1 : 4 Mailboxes (Mailbox01,Mailbox02,Mailbox03,Mailbox04)   + 2 CAS
Site 2 : 2 Mailboxes (Mailbox05,Mailbox06)   + 2 CAS (just for standby site)
So I have 2 DAG group  (6 Mailboxes separate to 3 Mailboxes for 1 DAG group Mailbox01,Mailbox02,Mailbox05 for DAG1 and Mailbox03,Mailbox04,Mailbox06 for DAG2)
After I upgrade Exchange 2013 to SP1 , I try to create new database on Mailbox01 and after that I try to add mailbox02 and mailbox05 to database copy of new database that I created.
"Mailbox05 can added to be database copy but Mailbox02 cannot add database copy for it , Error "Network path not found" occur" but Im very sure that path is the same for each mailbox database server.
so I try to create new database on Mailbox 03 and add database copy on mailbox04 and mailbox06.... the result is the same only Mailbox06 can add mailbox copy of database.
It look like I cannot have 2 mailbox in site 1 for database copy of each new database (I already try to create new database on Mailbox 02 and add database copy on mailbox01 and mailbox05 , the result is only mailbox05 can be database copy of database).
Please help me to fix this out.

Hi,
I recommend you check if the Remote Registry service is running on Mailbox01, Mailbox02, Mailbox03 and Mailbox04. If not, please start it and then add mailbox database copy to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Primary Mailbox Database fails to replicate after failing over to secondary copy in DAG

We had an issue yesterday on a primary mailbox database server when the drive the log files are located on filled up and took the databases off-line on the primary server bringing them up on the secondary.
After the issue was resolved and enough space was freed up, all but one database failed back. The one that would not come back showed Failed in the copy status. It remained mounted on the secondary server. I attempted several times to 'update' the copy and
it would run for aver 40 minutes and look like it was going okay then it would 'fail' and end up in a 'failed and suspended' state. The error would indicated it could not complete because the it could not find the source server.
The Update job was configured to point to the server holding the secondary copy as the source so should not have a problem.
Any idea on how I can get the primary copy working again? I thought about making the second copy the 1st to activate and removing the primary copy from the DAG and recreating it, but past experience doing that did not resolve the issue.
Thank you,
Nick
Nick Laurino

Find out why database file is missing, I doubt on antivirus and start looking at the antivirus sacanning exclusion to ensure it is properly set...
File-Level Antivirus Scanning on Exchange 2010
Then try to reseed the database copy from a good source, it might be possible that antivirus would be scanning file when it is getting reseeded and causing issue...
How to Reseed a Failed Mailbox Database Copy in Exchange Server 2010
Blog |
Get Your Exchange Powershell Tip of the Day from here

Database copy seeding fails

Hi,
I am trying to add a mailbox database copy from server1 to server2. Every time after seeding the status of the second copy is shown as 'Failed'. In the event log i can see one error message as given below :
The required log file 374413 for BInew\EX02 is missing on the active copy. If you removed the log file, please replace it. If the log file is lost, the database copy will need to be reseeded using Update-MailboxDatabaseCopy.
I have tried reseeding many times both from console and shell.
Update-MailboxDatabaseCopy -Identity "Binew\EX02" -DeleteExistingFiles
Is this the reason for the replication getting failed.I have never deleted any log file from server1.
Please help!

Hello,
You may run the following cmdlets one by one:
Suspend-MailboxDatabaseCopy <databaseName>\<ReplicaServerName>
Update-MailboxDatabaseCopy <databaseName>\<ReplicaServerName> -SourceServer <ActiveServerName> -DeleteExistingFiles:$True
Resume-MailboxDatabaseCopy <databaseName\<ReplicaServerName>
Regards from ExchangeOnline.in|Windows Administrator Area | Skype:[email protected]

Database copy is failed and suspended

Hi Everyone,
My environment is Exchange server 2010 sp3, two sites one denver one houston, 2 DAGs and DR server of each DAG is placed on the second DAG.
Scenario is
Site 1:denmbx1,denmbx2 and den1 are hosted on denver DAG01
Site 2: HOUmbx1,HOUmbx2 and HOU1 are hosted on DAG02
We've had outage few days back and now one mailbox database copy on one DR server is FAILED and SUSPNEDED while rest of the databases are Fine.
Now i cannot resume and update this database copy.
CAn anyone please help on this?
Thanks.

Hi,
You can reseed database copy manually to check result. You need to dismount the active copy of the database and copy the database file (EDB file) to the same location on Mailbox server in
the DR site. If you use this method, there will be an interruption in service because the process requires you to dismount the database.
1. If circular logging is enabled for the database, it must be disabled before proceeding.
2.
On the server who holds the active copy of the mailbox database, dismount this mailbox database.
3.
Verify that database is in a Clean Shutdown state.
4.
If it is Dirty Shutdown, we must use the command “ESEUTIL /r” to manually recover the database.
5.
Copy the edb file to passive node to the same path as the active database copy.
6. Perform seeding operation using following command:
Update-MailboxDatabaseCopy -Identity "database name / server name"
To check if the above steps finished successfully. We could run the following command to check the mailbox database copy status:
Get-MailboxDatabase| Get-MailboxDatabaseCopyStatus
Here is a related article for your reference.
http://technet.microsoft.com/en-gb/library/dd351100(v=exchg.141).aspx
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

CAS restart and Mailbox database dismount unexpectedly somtimes

Hi all,
In my environment I have 2 Exchange server 2013 (CAS + Mailbox Role both) CU2 : EX01 & EX02 in DAG01. Sometimes CAS service is restarted or Mailbox Database copy on Exchange servers is dismounted unexpectedly. For example today:
I have "Mailbox Database 01" copies on EX01 & EX02
Get-MailboxDatabaseCopyStatus "Mailbox Database 01"
Name Status
Mailbox Database 01\EX01 Healthy
Mailbox Database 01\EX02 Mounted
"Mailbox Database 01" copy on EX02 is dismounted, of course the other copy on EX01 is mounted automatically
Log Name:      Application
Source:        MSExchangeRepl
Date:          4/3/2015 2:32:19 PM
Event ID:      2153
Task Category: Service
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EX02.mydomain.com
Description:
The log copier was unable to communicate with server 'EX01.mydomain.com'. The copy of database 'Mailbox Database 01\EX02' is in a disconnected state. The communication error was: An error occurred while communicating with server 'EX01'. Error: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine. The copier will automatically retry after a short delay.
CAS service on EX01 , The Microsoft Exchange Mailbox Assistants service on EX02 are restarted
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:25:49 PM
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.mydomain.com
Description:
The Microsoft Exchange RPC Client Access service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:25:51 PM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: EX01.mydomain.com
Description:
The Microsoft Exchange RPC Client Access service entered the running state.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:25:54 PM
Event ID: 7032
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.mydomain.com
Description:
The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange RPC Client Access service, but this action failed with the following error:
An instance of the service is already running.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:30:28 PM
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EX02.mydomain.com
Description:
The Microsoft Exchange Mailbox Assistants service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:30:30 PM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: EX02.mydomain.com
Description:
The Microsoft Exchange Mailbox Assistants service entered the running state.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:30:33 PM
Event ID: 7032
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EX02.mydomain.com
Description:
The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange Mailbox Assistants service, but this action failed with the following error:
An instance of the service is already running.
On EX01 I can see many 1309 , 2009 , 6002 , 4999 in Event Viewer on both servers, and they just used half of RAM
I'm going to upgrade to SP1 this weekend but please help me to figure out really reason of this issue, limit of max connections on Exchange/Window server , or Disk IO or something ?
Thanks for your help.

Last night I tried reseed Mailbox Database 01\EX02 , about 8:15 PM
I checked event viewer, last 2153 event happened on 7:49 PM, check around :
Get-MailboxDatabaseCopyStatus -Server ex02 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 07\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 01\EX02
IncomingLogCopyingNetwork : {EX01,ReplicationDagNetwork01,An error occurred while communicating with server
'EX01'. Error: Unable to write data to the transport connection: An established
connection was aborted by the software in your host machine.}
OutgoingConnections :
Name : Mailbox Database 99\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Get-MailboxDatabaseCopyStatus -Server ex01 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 01\EX01
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 99\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Name : Mailbox Database 07\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Then I suspend and update Mailbox Database 01\EX02
Suspend-MailboxDatabaseCopy -Identity "Mailbox Database 01\EX02"
Update-MailboxDatabaseCopy -Identity "Mailbox Database 01\EX02" -Network "DAG01\ReplicationDagNetwork01"
Confirm
Are you sure you want to perform this action?
Seeding database copy "Mailbox Database 01\EX02".
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):
The seeding operation failed. Error: An error occurred while running prerequisite checks. Error: Log files exist in
'D:\Exchange Mailbox Database\Mailbox Database 01'. You must remove them before database seeding or reseeding can be
performed. You can use the Update-MailboxDatabaseCopy cmdlet with the -DeleteExistingFiles or -SafeDeleteExistingFiles
parameter to do this. [Database: Mailbox Database 01, Server: EX02.mydomain.com]
+ CategoryInfo : InvalidOperation: (Mailbox Database 01:String) [Update-MailboxDatabaseCopy], SeedPrepare
Exception
+ FullyQualifiedErrorId : [Server=EX02,RequestId=56f71c07-6209-4aae-94cb-bf3cfc0a38fd,TimeStamp=4/22/2015 1:0
5:56 PM] [FailureCategory=Cmdlet-SeedPrepareException] 5F5B4C53,Microsoft.Exchange.Management.SystemConfigurationT
asks.UpdateDatabaseCopy
+ PSComputerName : ex02.mydomain.com
I want they use DAG01\ReplicationDagNetwork01 (1Gbps) for reseeding database, then I tried to add -SafeDeleteExistingFiles
Update-MailboxDatabaseCopy -Identity "Mailbox Database 01\EX02" -Network "DAG01\ReplicationDagNetwork01" -SafeDeleteExistingFiles
Confirm
Are you sure you want to perform this action?
Seeding database copy "Mailbox Database 01\EX02".
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):
The seeding operation failed. Error: An error occurred while running prerequisite checks. Error: An error occurred
when trying to run the database redundancy validation checks for database 'Mailbox Database 01' due to
'SafeDeleteExistingFiles' being specified. Error: There were database redundancy check failures for database 'Mailbox
Database 01' that may be lowering its redundancy and putting the database at risk of data loss. Redundancy Count: 1.
Expected Redundancy Count: 2. Detailed error(s):
ex02:
Database 'Mailbox Database 01' does not have enough copies configured to meet the validation criteria.
[Database: Mailbox Database 01, Server: EX02.mydomain.com]
+ CategoryInfo : InvalidOperation: (Mailbox Database 01:String) [Update-MailboxDatabaseCopy], SeedPrepare
Exception
+ FullyQualifiedErrorId : [Server=EX02,RequestId=48374aa6-1198-4976-a435-3eb034dc5b58,TimeStamp=4/22/2015 1:0
8:44 PM] [FailureCategory=Cmdlet-SeedPrepareException] 458ED9A2,Microsoft.Exchange.Management.SystemConfigurationT
asks.UpdateDatabaseCopy
+ PSComputerName : ex02.mydomain.com
I think I should stop here, search more about -DeleteExistingFiles before continue. So I Resume-MailboxDatabaseCopy "Mailbox Database 01\EX02"
Everything is fine, I checked again
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus -Server ex02 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 07\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 01\EX02
IncomingLogCopyingNetwork : {EX01,ReplicationDagNetwork01}
OutgoingConnections :
Name : Mailbox Database 99\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus -Server ex01 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 01\EX01
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 99\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Name : Mailbox Database 07\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections
What is going on :) ? IncomingLogCopyingNetwork for Mailbox Database 01\EX02 is fine :) til mid night
This morning I view events on EX02 and event 2153 appears again on 7:30 AM , I run command et-MailboxDatabaseCopyStatus again
Get-MailboxDatabaseCopyStatus -Server ex02 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 07\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 01\EX02
IncomingLogCopyingNetwork : {EX01,ReplicationDagNetwork01,An error occurred while communicating with server
'EX01'. Error: Unable to write data to the transport connection: An established
connection was aborted by the software in your host machine.}
OutgoingConnections :
Name : Mailbox Database 99\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Get-MailboxDatabaseCopyStatus -Server ex01 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 01\EX01
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 99\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Name : Mailbox Database 07\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Any suggest ?

Fail to add mailbox database copy

Similar Messages

Maybe you are looking for