MSExchange EdgeSync Service Won’t Start and Event ID 1045 is Logged

The Microsoft Exchange EdgeSync service on a Hub Transport server may fail to start at server startup, or when you manually attempt to start it.

The Test-ServiceHealth cmdlet will also advise you that the MSExchangeEdgeSync service is not running. This service is normally intended to run, even for Hub Transport servers in sites where no Edge Subscription exists.

[PS] C:\>Test-ServiceHealth

Role                    : Hub Transport Server Role
RequiredServicesRunning : False
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeServiceHost, MSExchangeTransport, MSExchangeTransp
                          ortLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {MSExchangeEdgeSync}

Event ID 1045 will also be logged to the Application event log.

Log Name: Application
Source: MSExchange EdgeSync
Date: 22/01/2013 11:41:43 PM
Event ID: 1045
Task Category: Initialization
Level: Warning
Keywords: Classic
User: N/A
Computer: SRVEXCDR01.gso.internal
Initialization failed with exception: Microsoft.Exchange.EdgeSync.Common.EdgeSyncServiceConfigNotFoundException: Couldn’t find EdgeSync service configuration object for the site BranchOffice. If the configuration object doesn’t exist in the Active Directory location CN=EdgeSyncService,CN=BranchOffice,CN=Sites,CN=Configuration,DC=exchangeserverpro,DC=net, create it using the New-EdgeSyncServiceConfig cmdlet. If the object does exist, check its permissions.. If this warning frequently occurs, contact Microsoft Product Support.

The solution, as mentioned in the event log entry, is to run the New-EdgeSyncServiceConfig cmdlet in the Exchange Management Shell to create the EdgeSync service configuration object for that site.

[PS] C:\>New-EdgeSyncServiceConfig -Site BranchOffice

You may need to wait for the change to replicate in Active Directory, then you should be able to successfully start the Microsoft Exchange EdgeSync service for Hub Transport servers in that site.


Leave a Reply

Your email address will not be published. Required fields are marked *