Home » Exchange Server » MSExchange EdgeSync Service Won't Start and Event ID 1045 is Logged

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.

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.

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.

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.
Category: Exchange Server


  1. Stephen says:

    I have this exact issue. The only problem is that the error refers to a site that hasn’t had an exchange server for more than 2 years now. We have Exchange servers at our DC, one CAS/HUB and the other the mailbox server. We have two other Exchange servers at remote sites wil the CAS/Hub/Mailbox roles and one of these is complaining about the missing config. I’m not quite sure how to go ahead and fix this. Any assistance will be appreciated.

  2. detrich says:

    Thanks Paul,

    We recently relocated our Ex2016 DR server from one AD site to a new AD (DR) site. And, after I got Ex2016 replication up and running again, I was still seeing MS Ex2016 EdgeSync service having the issue you described. Your explanation and fix made sense and worked spot on.

    Thanks again for this information. =)

  3. Mario says:

    I have got the same error on my Exchange server. We do not have Edge server in our environment.
    Should I run New-EdgeSyncServiceConfig -Site sitename to avoid this error even we do not use Edge server?

    Thank you

Leave a Reply

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