Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Set-SendConnector doesn't work for Exchange Server in hybrid scenarios with Edge Server installed

Set-SendConnector doesn't work for Exchange Server in hybrid scenarios with Edge Server installed

View products that this article applies to.

Symptoms

Assume that you install the Cumulative Update 3 for Microsoft Exchange Server 2019 or Cumulative Update 2 for Exchange Server 2019 in a hybrid environment that has an Edge server installed. When a certificate is configured for the respective send connector, the Set-SendConnector cmdlet doesn't work, and you receive the following error message:
"PowerShell failed to invoke 'Set-SendConnector': Error 0x5 (Access is denied) from cli_GetCertificate"
or
"Error 0x6ba (the RPC server is unavailable) from cli_GetCertificate"

↑ Back to the top

Cause

This issue occurs because the TLS certificate check (in case the TlsCertificateName attribute is populated on the send connector) doesn't work against the Edge servers because the RPC communication is blocked against the Edge servers.

↑ Back to the top

Resolution

To fix this issue, install one of the following updates:

For Exchange Server 2019, install the Cumulative Update 4 for Exchange Server 2019 or a later cumulative update for Exchange Server 2019.

For Exchange Server 2016, install the Cumulative Update 15 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016.

↑ Back to the top

Workaround

The Hybrid Configuration Wizard (HCW) can successfully create the "Outbound to Office 365" send connector if it doesn't exist. This is because the New-SendConnector cmdlet can be used without issues.

Further changes (by using the Set-SendConnector cmdlet) of the "Outbound to Office 365" send connector after the creation aren't possible. However, the "Outbound to Office 365" send connector can be deleted and re-created by using the desired configuration.

↑ Back to the top

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

More information

Microsoft has realized this problem and will post more information in this article when it becomes available.

↑ Back to the top

Keywords: Mail Flow, kbContentAuto, kb, kbfix, kbqfe, PowerShell fails to invoke set-sendconnector, set-sendconnector not working in hybrid, kbHotfixAuto, CI108393, kbSupportTopic

↑ Back to the top

Article Info
Article ID : 4523519
Revision : 22
Created on : 4/2/2020
Published on : 4/2/2020
Exists online : False
Views : 311