Skip to content

Commit 3280a44

Browse files
authored
Merge pull request #10617 from MicrosoftDocs/AB#8924-CertAssignmentFails-Error-0xe0434352-Exchange-OnPrem
AB#8524 Certificate assignment fails due to invalid FQDN in Exchange Server
2 parents c6da221 + 33f2490 commit 3280a44

3 files changed

Lines changed: 81 additions & 1 deletion

File tree

Exchange/ExchangeServer/administration/cannot-import-third-party-certificate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.custom:
1010
- sap:OWA And Exchange Admin Center\Virtual Directories configuration
1111
- Exchange Server
1212
- CSSTroubleshoot
13-
ms.reviewer: batre, skumarg, batre, v-six
13+
ms.reviewer: batre, skumarg, v-six
1414
appliesto:
1515
- Exchange Server 2010 Enterprise
1616
- Exchange Server 2010 Standard
Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
---
2+
title: Certificate assignment fails and returns error 0xe434352
3+
description: This article provides the resolution for error 0xe434352 that occurs during certificate assignment if unsupported characters are used in the domain name of Receive Connectors.
4+
#customer intent: As an Exchange Server administrator, I want to resolve SMTP (Simple Mail Transfer Protocol) certificate binding issues that are caused by invalid fully-qualified domain names (FQDNs) so that I can maintain system reliability.
5+
author: cloud-writer
6+
ms.author: meerak
7+
manager: dcscontentpm
8+
audience: ITPro
9+
ms.topic: troubleshooting
10+
ms.custom:
11+
- sap:Administrative Tasks
12+
- Exchange Server
13+
- CSSTroubleshoot
14+
ms.reviewer: igserr, batre, arindamt, v-kccross
15+
appliesto:
16+
- Exchange Server SE
17+
- Exchange Server 2019
18+
- Exchange Server 2016
19+
search.appverid: MET150
20+
ms.date: 01/28/2026
21+
---
22+
23+
# Error 0xe434352 and SMTP certificate assignment fails
24+
25+
## Summary
26+
27+
When you assign certificates to Exchange services, you might encounter error 0xe0434352 during the certificate binding process. The error indicates that one or more Receive Connectors in Microsoft Exchange Server use FQDNs that contain characters not allowed by DNS standards.
28+
29+
## Symptoms
30+
31+
You run the `Enable-ExchangeCertificate` cmdlet to assign a certificate to the SMTP service. The operation fails and returns the following error message:
32+
33+
> The Exchange Certificate operation has failed with an exception on server <*Server Name*>.
34+
>
35+
> The error message is: Unknown error (0xe0434352)
36+
37+
## Cause
38+
39+
This issue occurs if the FQDN of one or more Receive Connectors contains unsupported characters. The connector creation process allows underscores in the domain name. However, underscores violate DNS standards and cause failures during certificate binding.
40+
41+
For more information about domain names, see the following articles:
42+
43+
- [DNS host names](/troubleshoot/windows-server/active-directory/naming-conventions-for-computer-domain-site-ou#dns-host-names)
44+
- [Unsupported characters for Exchange 2013 object names](/exchange/unsupported-characters-for-exchange-2013-object-names-exchange-2013-help)
45+
46+
## Resolution
47+
48+
To resolve this issue, use the Exchange Management Shell to find connectors that have invalid FQDNs. Run the following PowerShell command:
49+
50+
```powershell
51+
Get-ReceiveConnector | Select Identity, FQDN
52+
```
53+
54+
You can refine your search to look for specific unsupported characters. The following example searches for underscores in FQDNs:
55+
56+
```powershell
57+
Get-ReceiveConnector | Where-Object { $_.FQDN -like "*_*" } | Select Identity, FQDN
58+
```
59+
60+
After you identify the connector that contains unsupported characters, rename it by using supported characters:
61+
62+
```powershell
63+
Set-ReceiveConnector -Identity "ServerName\ConnectorName" -FQDN ValidFQDN.domain.com
64+
```
65+
66+
After you fix the domain name, retry the certificate assignment to verify that you no longer encounter the error:
67+
68+
```powershell
69+
Enable-ExchangeCertificate -Thumbprint <Thumbprint> -Services SMTP
70+
```
71+
72+
## References
73+
74+
For more information about domain name formation and supported characters, see:
75+
76+
- DoD Internet host table specification [RFC 952](https://www.rfc-editor.org/rfc/rfc952)
77+
- Domain names - Implementation and specification [RFC 1035](https://www.rfc-editor.org/rfc/rfc1035)
78+
- Requirements for Internet hosts - Application and Support [RFC 1123](https://www.rfc-editor.org/rfc/rfc1123)

Exchange/ExchangeServer/servertoc/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,8 @@ items:
5454
href: ../administration/cannot-eac-add-remote-shared-mailbox-distribution-group.md
5555
- name: Certificate status couldn't be determined error
5656
href: ../administration/cannot-import-third-party-certificate.md
57+
- name: Certificate assignment fails with error 0xe434352
58+
href: ../administration/certificate-assignment-fails-invalid-characters.md
5759
- name: Cmdlet/parameter combinations not working
5860
href: ../administration/cmdlet-parameter-combinations-not-working.md
5961
- name: Connecting to the remote server failed

0 commit comments

Comments
 (0)