asked on

Exchange 2013 DAG: Error: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_RpccGetDbSeedStatus

People,

Can anyone here please assist me with the below error in configuring the DAG for the first time ?

error

The seeding operation failed. Error: The Microsoft Exchange Replication service may not be running on server PRODMAIL31-VM.Domain.com. Error: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_RpccGetDbSeedStatus

Open in new window

The server PRODMAIL31-VM.Domain.com is brand new Exchange 2013 Standard which only host secondary or passive Mailbox Database only.

I've double checked that all Exchange Server 2013 services are up and running.

But why it is failed like that ?

PRADIIP SINGH

Try restarting the Replication service
Make sure Exchange server is member of Exchange Servers and Exchange Trusted Subsystems
Check the event ID 2080 and share the details

PRADIIP SINGH

Also run the EXBPA and see

Albert Widjaja

ASKER

OK, all of them is in the Exchange Servers and Exchange Trusted Subsystems group.
Now the

What's the different between the Update and the Resume command on the ECP ?
I do not want to cause any downtime or data loss, so I need your help here please.

PRADIIP SINGH

Resume will resume the database copy where it has failed and update will reseed it

Albert Widjaja

ASKER

Which one is safe to be executed without causing outage or data loss ?

PRADIIP SINGH

Resume is always better as you will not reseed rather it will start where it was left off , so first try to resume it and if no option then go with the update and either of the case it will not affect your Active copy

Albert Widjaja

ASKER

OK, let me try to do the below in order:

1. Click on Resume on the failed & suspended DB copy.
2. if the above still failed, then 1. Click on Update on the failed & suspended DB copy.

Hopefully no data loss or outage caused by running the above two command.

ASKER CERTIFIED SOLUTION

PRADIIP SINGH

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Albert Widjaja

ASKER

Not sure why in the first attempt it is complaining about not able to find the large .EDB file ?

PS C:\TEMP> Get-MailboxDatabaseCopyStatus -Identity "PRODMBX43-VM-DB04\PRODMBX31-VM" | fl name,report,*error*


Name                     : PRODMBX43-VM-DB04\PRODMBX31-VM
ErrorMessage             : The Microsoft Exchange Replication service encountered an error while inspecting the logs and database for PRODMBX43-VM-DB04\PRODMBX31-VM on startup. Error: File 
                           check failed : Database file 'H:\Mailbox\PRODMBX43-VM-DB04\PRODMBX43-VM-DB04.edb' was not found.
                           
ErrorEventId             : 2070
ExtendedErrorInfo        : Microsoft.Exchange.Cluster.Replay.FileCheckEDBMissingException: File check failed : Database file 'H:\Mailbox\PRODMBX43-VM-DB04\PRODMBX43-VM-DB04.edb' was not found.
                              at Microsoft.Exchange.Cluster.Replay.FileChecker.CheckLogfiles(Int64 minimumGeneration, Int64 maximumGeneration, LogRepair repair)
                              at Microsoft.Exchange.Cluster.Replay.FileChecker.RunChecks(LogRepair repair, Boolean forceDeleteCheckPointFile)
                              at Microsoft.Exchange.Cluster.Replay.TargetReplicaInstance.ConfigurationCheckerInternal()
                              at Microsoft.Exchange.Cluster.Replay.ReplicaInstance.<ConfigurationChecker>b__1()
ContentIndexErrorMessage : The content index has been suspended.
VolumeInfoError

Open in new window

PRADIIP SINGH

You will have to reseed it

PRADIIP SINGH

You will have to reseed it

PRADIIP SINGH

It seems your EDB file is already deleted from the passive copy might be you would have already attempted to update

Albert Widjaja

ASKER

Thanks man !

PRADIIP SINGH

Glad to assist you my Friend :)