Fixing Exchange 2013 EdgeTransport “CouldNotConnect” error

Quite often this problem occurs to messaging administrators when deploying Exchange 2013 Edge Transport server role.
After creating a new EdgeSubscription you call for results with Start-EdgeSynchronization and get the following response:

[PS] C:\Start-EdgeSynchronization -Server mbx.domain.local -TargetServer edge.domain.com -ForceFullSync
RunspaceId : 578a8a8c-002b-4bf4-86ff-f78c285d2944
Result : CouldNotConnect
Type : Configuration
Name : Edge
FailureDetails : The LDAP server is unavailable.
StartUTC : 4/23/2014 10:42:24 AM
EndUTC : 4/23/2014 10:42:24 AM
Added : 0
Deleted : 0
Updated : 0
Scanned : 0
TargetScanned : 0

RunspaceId : 578a8a8c-002b-4bf4-86ff-f78c285d2944
Result : CouldNotConnect
Type : Recipients
Name : Edge
FailureDetails : The LDAP server is unavailable.
StartUTC : 4/23/2014 10:42:24 AM
EndUTC : 4/23/2014 10:42:24 AM
Added : 0
Deleted : 0
Updated : 0
Scanned : 0
TargetScanned : 0

First check firewall rules to and fro EdgeTransport and

telnet servername 25

or

Test-NetConnection servername -Port 25

If everything seems to be all right – there still one thing might left overlooked –
Your Exchange Server 2013 must be supplied with a product key to run EdgeSync successfully!
Many seem to forget or think to postpone installing the license key to EdgeTransport. However, unlike previous versions, Exchange 2013 EdgeTransport role fails to interact with rest of services in such case.

Quick check:

Get-ExchangeServer servername | fl Edition,IsExchangeTrialEdition,IsExpiredExchangeTrialEdition

If you find your server is unlicensed yet –

Set-ExchangeServer servername -ProductKey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Since EdgeTransport does not run any user databases – there is no need to restart anything here. You just need to recreate your EdgeSubscription once again. This issue must no longer be a problem for you.

3 thoughts on “Fixing Exchange 2013 EdgeTransport “CouldNotConnect” error”

Leave a Reply to MaxMVP Cancel reply

Your email address will not be published.