Test-EdgeSynchronization on one server

Question

Test-EdgeSynchronization Fails on 2 servers

I have 4 Exchange 2013 servers, 4 Exchange 2019 server and 2 Edge server exchange 2016. ( out of which 2 exchange 2013 failed to Sync remaining 6 are good)

I did created new subscription
Start sync no luck.

on the effected exch 2013 server when run start-edgesync

Result : CouldNotConnect
Type : Configuration

and test-edgesub

SyncStatus : Failed
FailureDetail : EdgeSync service cannot connect to this subscription because of error "No EdgeSync
credentials were found for Edge Transport server OACTCAPS295.PA-STGLAB.LCL on the local
Mailbox server. Remove the Edge subscription and re-subscribe the Edge Transport
server.".

i checked the Ports 25 and 50636 and they are good when i telnet

Answer 1

Hi @Abdul Wajeed Mohammed ,

Thank you for posting your questions!

Are these 4 Exchange 2013 servers in a DAG? I did a test in a DAG environment, I subscribed on one, and all DAG member servers could run Test-EdgeSynchronization successfully.
Are you using the default self-signed certificate(Microsoft Exchange)? If you are using a third-party cert, you can remove this certificate and re-import.

If you use the default certificate, you can try these steps:

1. Remove the Certificate: Exchange Server.
2. Run New-ExchangeCertificate in EMS, it will re-create the default Exchange Server certificate.
3. Remove the edge Subscription on both Exchange 2013 mailbox server and Edge Server.
4. Re-subscribe.

Note after you created or imported the certificate, you should bind the certificate to services.
If these don’t help you, you can check if there are logs in Windows Event Viewer, it should provide a detailed information about this issue.
You can share the error messages by covering your personal information.

Regards,
Lou

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.