• Home
  • About
  • Blog
  • Books
  • Training
  • Subscribe
  • Advertise
  • Contact
    • Email
    • Facebook
    • Twitter
    • RSS

Practical 365

  • Office 365
  • Exchange 2019
  • Exchange 2016
  • Exchange 2013
  • Hybrid
  • Certificates
  • PowerShell
  • Migration
You are here: 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

January 24, 2013 by Paul Cunningham 8 Comments

Share
Share
Tweet
+1
Shares 0

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.

1
2
3
4
5
6
7
[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
Description:
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.

1
[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.

Paul Cunningham

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.

Share
Share
Tweet
+1
Shares 0

Exchange Server Edge Transport, EdgeSync, Exchange 2010, Hub Transport

Comments

  1. Rusti says

    January 22, 2014 at 1:18 am

    Thanks! Worked like a charm!

    Reply
  2. Dennis says

    June 19, 2014 at 10:01 am

    Cool! Worked for me as well and save my time.

    Reply
  3. Elmar says

    November 2, 2014 at 11:12 pm

    Thanks. Worked 100%. Any clue why it just removed the setting from the AD?

    Reply
  4. Dave says

    October 22, 2015 at 4:43 pm

    Worked great, thanks!!!!

    Reply
  5. Stephen says

    November 25, 2015 at 1:35 am

    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.

    Reply
  6. detrich says

    October 12, 2016 at 2:14 am

    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. =)

    Reply
  7. Mario says

    July 20, 2017 at 7:13 am

    Hello,
    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

    Reply
    • Paul Cunningham says

      July 20, 2017 at 8:52 am

      I believe so yes, it’s been a long time since I have dealt with this issue but I think it can happen regardless of whether you’re using an Edge server.

      Reply

Leave a Reply Cancel reply

Recent Articles

  • You Can Stop Deploying Exchange Server 2013 Now
  • Automating New User Account On-boarding Using SharePoint Online, Flow, and PowerApps
  • March 2018 Updates Released for Exchange Server
  • Securing Administrator Access with Privileged Identity Management for Azure Active Directory
  • The Junkings will Continue Until Morale Improves
Practical 365

Popular Articles

Microsoft Recommending Non-Expiring Passwords to Office 365 CustomersMicrosoft Recommending Non-Expiring Passwords to Office 365 Customers
PowerShell Scripts for Office 365PowerShell Scripts for Office 365
MeetEasier Helps Your Users Find Available Meeting RoomsMeetEasier Helps Your Users Find Available Meeting Rooms
PowerShell: Listing Azure AD/Office 365 User Accounts with Directory Sync StatusPowerShell: Listing Azure AD/Office 365 User Accounts with Directory Sync Status
First Steps: Configuring Exchange Online ProtectionFirst Steps: Configuring Exchange Online Protection

eBooks and Training

  • Office 365 for IT Pros
  • Exchange Server Troubleshooting Companion
  • Migrating to Exchange Server 2016
  • Exchange 2016 Exam 70-345
  • Managing Exchange Mailboxes and Distribution Groups in PowerShell
  • Exchange 2013 Boot Camp
  • Exchange 2010 Boot Camp

Recommended Resources

  • Office 365 Books
  • Exchange Server Books
  • Exchange PowerShell Scripts
  • Exchange Analyzer
  • Exchange 2010 to 2013 Migration
  • Exchange 2003 to 2010 Migration
  • Exchange 2007 to 2010 Migration
  • Digicert SSL Certificates

About This Site

Practical 365 is a leading site for Office 365 and Exchange Server news, tips and tutorials, run by Paul Cunningham, Microsoft MVP, author, speaker, and consultant. Read more...

To stay up to date:
  • Subscribe to the email newsletter
  • Follow @Practical365 on Twitter
  • Like us on Facebook
  • Write for Us

Copyright © 2018 LockLAN Systems Pty Ltd · Disclosure · Privacy Policy · Advertise
PO BOX 7002, Hemmant, Queensland 4174 · ABN: 25 121 101 255

We are an Authorized DigiCert™ SSL Partner.