Skip to content

Commit ff74f8b

Browse files
authored
Update certificate-assignment-fails-invalid-characters.md
Edit review per CI 8534
1 parent 9e9953d commit ff74f8b

1 file changed

Lines changed: 11 additions & 13 deletions

File tree

Lines changed: 11 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Certificate assignment fails with error 0xe434352
3-
description: This article provides the resolution for error 0xe434352 that occurs during certificate assignment when unsupported characters are used in the domain name of Receive Connectors.
4-
#customer intent: As an Exchange Server admin, I want to resolve certificate binding issues caused by invalid fully-qualified domain names (FQDNs) so that I can maintain system reliability.
3+
description: This article resolves 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 certificate binding issues that are caused by invalid fully-qualified domain names (FQDNs) so that I can maintain system reliability.
55
author: cloud-writer
66
ms.author: meerak
77
manager: dcscontentpm
@@ -20,22 +20,22 @@ search.appverid: MET150
2020
ms.date: 01/28/2026
2121
---
2222

23-
# SMTP certificate assignment fails with error 0xe434352 because of unsupported characters in the FQDN
23+
# Error 0xe434352 and SMTP certificate assignment fails
2424

2525
## Summary
2626

27-
When you assign certificates to Exchange services, you might encounter error 0xe0434352 during the certificate binding process. This error typically indicates that one or more Receive Connectors in your Exchange environment use FQDNs that contain characters that aren't supported by DNS standards.
27+
When you assign certificates to Exchange services, you might encounter error 0xe0434352 during the certificate binding process. This error typically indicates that one or more Receive Connectors in your Microsoft Exchange Server environment use FQDNs that contain characters that aren't supported by DNS standards.
2828

2929
## Symptoms
3030

31-
You run the `Enable-ExchangeCertificate` cmdlet to assign a certificate to the SMTP service. The operation fails with the following message:
31+
You run the `Enable-ExchangeCertificate` cmdlet to assign a certificate to the SMTP service. The operation fails and returns the following error message:
3232

33+
> Unknown error (0xe0434352)
3334
> The Exchange Certificate operation has failed with an exception on server <*Server Name*>.
34-
> The error message is: Unknown error (0xe0434352)
3535
3636
## Cause
3737

38-
This issue occurs when the FQDN of one or more Receive Connectors contains unsupported characters, such as underscores. The connector creation process allows underscores in the domain name, but these characters violate DNS standards and cause failures during certificate binding.
38+
This issue occurs if the FQDN of one or more Receive Connectors contains unsupported characters, such as underscores. The connector creation process allows unsupported characters, such as underscores, in the domain name. However, these characters violate DNS standards and cause failures during certificate binding.
3939

4040
For more information about domain names, see the following articles:
4141

@@ -44,34 +44,32 @@ For more information about domain names, see the following articles:
4444

4545
## Resolution
4646

47-
To resolve this issue, use the Exchange Management Shell to find connectors with invalid FQDNs.
47+
To resolve this issue, use the Exchange Management Shell to find connectors that have invalid FQDNs. Run the following Powershell command:
4848

4949
```powershell
5050
Get-ReceiveConnector | Select Identity, FQDN
5151
```
5252

53-
You can refine your search to look for specific unsupported characters. The following example searches for underscores in FQDNs.
53+
You can refine your search to look for specific unsupported characters. The following example searches for underscores in FQDNs:
5454

5555
```powershell
5656
Get-ReceiveConnector | Where-Object { $_.FQDN -like "*_*" } | Select Identity, FQDN
5757
```
5858

59-
After you identify the connector with unsupported characters, rename it using supported characters to fix the problem.
59+
After you identify the connector that contains unsupported characters, rename it by using supported characters:
6060

6161
```powershell
6262
Set-ReceiveConnector -Identity "ServerName\ConnectorName" -FQDN ValidFQDN.domain.com
6363
```
6464

65-
After you fix the domain name, retry the certificate assignment to confirm that you no longer receive the error.
65+
After you fix the domain name, retry the certificate assignment to verify that you no longer encounter the error:
6666

6767
```powershell
6868
Enable-ExchangeCertificate -Thumbprint <Thumbprint> -Services SMTP
6969
```
7070

7171
## References
7272

73-
For more information about domain name formation and supported characters, see:
74-
7573
- DoD Internet host table specification [RFC 952](https://www.rfc-editor.org/rfc/rfc952)
7674
- Domain names - Implementation and specification [RFC 1035](https://www.rfc-editor.org/rfc/rfc1035)
7775
- Requirements for Internet hosts - Application and Support [RFC 1123](https://www.rfc-editor.org/rfc/rfc1123)

0 commit comments

Comments
 (0)