Exchange Server Federation Error

Shota Tadumadze 41 Reputation points
2022-03-17T13:35:41.283+00:00
Exchange | Exchange Server | Management
{count} votes

Accepted answer
  1. Joyce Shen - MSFT 16,701 Reputation points
    2022-03-18T02:25:15.947+00:00

    Hi @Shota Tadumadze

    The official KB lists some possible causes when running this command Set-FederatedOrganizationIdentifier and get the error "An unexpected error occurred on a send"

    I would suggest you firstly check if your issue is related to TLS1.2, please make sure your on-premises environment supports TLS 1.2, just like this similar error discussed: Hybrid Configuration Wizard Stuck on adding federated domains

    Exchange Server TLS guidance Part 2: Enabling TLS 1.2 and Identifying Clients Not Using It
    Exchange Server TLS guidance Part 3: Turning Off TLS 1.0/1.1

    And after performing the operations above, verify the result again, and check if anything else missed introduced in the KB above.


    If an Answer 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.


1 additional answer

Sort by: Most helpful
  1. Joe Spears 1 Reputation point
    2022-09-26T15:46:28.733+00:00

    This was the solution for me, Exchange 2016 throwing the same "An unexpected error occurred on a send" whether attempted via the powershell command, or via ECP / Organization / Manage federation, or by running the HCW. I had to grab the regedit text from the other page (this one is image screenshots), and edit out the directional "" and replace them with straight "", and it worked perfectly after rebooting.


Your answer

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