Share via

Exchange Server Edgesync

BRIAN N 1 Reputation point
2021-04-19T14:49:58.13+00:00

Exchange 2016 CU20 Mailbox Server and Edge Server - working and normal edgesync

Exchange 2019 cu9 mailbox server will not connect via edgesync

getting 10104 event id and 1024. All certificates seem in date and fine.

any help appreciated

Exchange | Exchange Server | Management
Exchange | Exchange Server | Management

The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.


2 answers

Sort by: Most helpful
  1. BRIAN N 1 Reputation point
    2021-04-28T09:10:35.41+00:00

    Edge server is Exchange 2016 CU20

    third party cert for mailbox only

    All Servers subscribed and 2016 has lease.

    I am going to try building edge as 2019 to see if that helps

    All Services are running

    Brian

    Was this answer helpful?


  2. Anonymous
    2021-04-20T02:39:54.827+00:00

    Hi @BRIAN N ,

    As Andy said, you could provide more information so we could better help you out.

    I did a research about the Event 10104 and Event 1024, and they both point to the certificate.
    So please check/test the following:

    1. Is the Edge server also Exchange 2019 CU9?
    2. Are you using a third-party certificate for the mailbox server and edge server?
    3. Have you subscribed Edge to the mailbox server? Procedures for Edge Subscriptions
    4. Run Test-ServiceHealth to test if all services are running.

    Please also find the answer provided by Felix in this thread: EdgeSync Errors and see if it's helpful.

    Best 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.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.