OWA 및 ActiveSync with Exchange 2016에 대해 간헐적인 503 오류가 발생합니다. 이 오류는 프런트 엔드 서버에서 활성화되지 않은 데이터베이스의 계정에만 영향을 미치므로 사용자를 사서함으로 프록시하는 데 문제가 있는 것으로 보입니다. 이러한 문제는 아래에서 자세히 설명할 Hyper-V 체크포인트를 적용한 후 시작되었습니다. 체크포인트를 만들 때 모든 것이 제대로 작동했는데 왜 이런 일이 발생했는지 이해가 되지 않습니다.

구성

CU18을 실행하는 두 개의 Exchange 2016 서버가 있습니다. 서버는 DAG에 있으며 둘 다 모든 역할이 설치되어 있습니다. 우리의 모든 데이터베이스는 두 서버에 모두 복제되고 그 중 절반은 각 서버에서 활성화됩니다. DNS 로드 밸런싱이 설정되어 있지 않으므로 대신 각 서버에는 고유한 영구 IP가 있으며 mail.domain.com의 DNS는 유지 관리를 수행해야 하는 경우 서버 간에 수동으로 이동하는 세 번째 IP를 가리킵니다. 하나 등이지만 그렇지 않으면 하나의 서버에 유지됩니다. 우리의 DNS는 분할됩니다. 즉, 내부 및 외부 DNS는 각각 내부 및 외부 IP를 가리킵니다. 두 서버 모두 신뢰할 수 있는 공용 CA에서 서명한 동일한 SSL SAN 인증서를 사용하며 인증서는 유효하고 서비스에 할당됩니다.

무슨 일이에요

Exchange에 관한 한 모든 것이 잘 작동했습니다. AV/Antispam 등의 관리 에이전트가 교환 서버 중 하나의 AV 서버에 다시 연결되지 않는 문제를 발견했습니다. 에이전트를 다시 설치해도 문제가 해결되지 않아 AV 기술 지원팀에서 하나의 서버에 전체 보안 패키지를 다시 설치할 수 있는지 물었습니다(서버를 exch1이라고 부를 수 있음). 그런 다음 다음을 실행하여 exch1을 유지 관리 모드로 전환합니다.C:\Program Files\Microsoft\Exchange\V15\Scripts\StartDagMaintenance.ps1앞서 언급한 세 번째 IP를 exch2로 이동합니다. 모든 데이터베이스 복사본이 exch2에서 활성화되었음을 확인한 후 exch1의 Hyper-V 체크포인트를 사용했습니다. 그런 다음 보안 패키지를 제거하고 다시 설치하여 에이전트 문제를 해결했습니다. 그러나 공유 검역소가 실제로 exch1에 저장되어 있음을 깨달았습니다. 우리는 학교로서 대부분의 다른 사람들이 허용하는 많은 파일 형식을 격리하고 정기적으로 항목을 릴리스합니다. 이러한 이유로 우리는 검역소를 저장하기 위해 체크포인트를 적용/복원하기로 선택했습니다. AV 기술 지원은 에이전트를 다시 연결하도록 관리했고 StopDagServerMaintenance.ps1스크립트를 실행 하고 세 번째 IP를 다시 exch1로 옮겼습니다.

문제

exch1을 유지 관리 모드에서 다시 가져온 후 OWA를 통해 특정 계정에 로그인할 때 503 오류가 발생하기 시작했습니다. 문제가 있는 계정은 exch2에서 활성화되어 exch1을 통해 프록시되는 데이터베이스에 있는 모든 계정이었습니다. 내 iPhone의 메일 앱(Exchange 계정으로 구성됨)도 연결할 수 없습니다. 이 시점에서 exch1( C:\Windows\system32\LogFiles\HTTPERR) 의 HTTPERR 로그 MSExchangeRpcProxyAppPool다음에 대해 반복되는 오류를 표시했습니다 .

2021-03-03 17:42:19 {3RD_EXCH_IP} 20228 {3RD_EXCH_IP} 444 - - - - - - Timer_ConnectionIdle -
2021-03-03 17:42:20 {3RD_EXCH_IP} 19752 {3RD_EXCH_IP} 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?{EXCH1_FQDN}:6001 - 400 2 BadRequest MSExchangeRpcProxyAppPool
2021-03-03 17:42:24 {Visitor_IP} 44932 {3RD_EXCH_IP} 443 - - - - - - Timer_ConnectionIdle -
2021-03-03 17:42:28 {Visitor_IP} 44206 {3RD_EXCH_IP} 443 - - - - - - Timer_ConnectionIdle -
2021-03-03 17:42:30 {EXCH2_IP} 33910 {EXCH1_IP} 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?{EXCH1_FQDN}:6001 - 400 2 BadRequest MSExchangeRpcProxyAppPool
2021-03-03 17:42:39 {Visitor_IP} 56932 {3RD_EXCH_IP} 443 - - - - - - Timer_ConnectionIdle -
2021-03-03 17:42:40 {3RD_EXCH_IP} 20508 {3RD_EXCH_IP} 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?{EXCH1_FQDN}:6001 - 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2021-03-03 17:42:40 {IPV6_ADDR} 18889 {IPV6_ADDR} 444 HTTP/1.1 GET /owa/ev.owa2?ns=PendingRequest&ev=PendingNotificationRequest&UA=0&cid=90952fb3-d596-4c2e-b4ae-4a19ecba2204&brwnm=chrome&X-OWA-CANARY=r6JrtadBzESnFj23L7T5ZdDs3zxr3tgIFNaGCIXOAFiqEzPIoSRDIZmhFbuZnhVVsyQp5sqSYgQ.&n=rf - - 2 Connection_Dropped MSExchangeOWAAppPool
2021-03-03 17:42:40 {EXCH2_IP} 33906 {EXCH1_IP} 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?{EXCH1_FQDN}:6001 - 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2021-03-03 17:42:40 {EXCH1_IP} 18912 {EXCH1_IP} 444 HTTP/1.1 GET /owa/ev.owa2?ns=PendingRequest&ev=PendingNotificationRequest&UA=0&cid=cf1049ad-ecca-4ec5-ac46-015e3e0eb32d&brwnm=chrome&X-OWA-CANARY=Gh9oOYHZPkuN4Ou2TTIPPyAoS1tr3tgIzL0cjYwNeE1YpjnAzHdoa7CGiidtl2YWLWqvdgHVFY0.&n=r3 - - 2 Connection_Dropped MSExchangeOWAAppPool
2021-03-03 17:42:44 {Visitor_IP} 8192 {3RD_EXCH_IP} 443 - - - - - - Timer_ConnectionIdle -
2021-03-03 17:42:44 {Visitor_IP} 35328 {3RD_EXCH_IP} 443 - - - - - - Timer_ConnectionIdle -
2021-03-03 17:43:09 {Visitor_IP} 53884 {3RD_EXCH_IP} 443 - - - - - - Timer_ConnectionIdle -
2021-03-03 17:43:09 {Visitor_IP} 53882 {3RD_EXCH_IP} 443 - - - - - - Timer_ConnectionIdle -
2021-03-03 17:43:09 {Visitor_IP} 53883 {3RD_EXCH_IP} 80 - - - - - - Timer_ConnectionIdle -
2021-03-03 17:43:09 {3RD_EXCH_IP} 20810 {3RD_EXCH_IP} 444 - - - - - - Timer_ConnectionIdle -
2021-03-03 17:43:13 {Visitor_IP} 59200 {3RD_EXCH_IP} 443 - - - - - - Timer_ConnectionIdle -
2021-03-03 17:43:13 {3RD_EXCH_IP} 18096 {3RD_EXCH_IP} 444 - - - - - - Timer_ConnectionIdle -
2021-03-03 17:43:13 {Visitor_IP} 61922 {3RD_EXCH_IP} 443 - - - - - - Timer_MinBytesPerSecond -
2021-03-03 17:43:15 {3RD_EXCH_IP} 19752 {3RD_EXCH_IP} 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?{EXCH1_FQDN}:6001 - 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2021-03-03 17:43:15 {EXCH2_IP} 33910 {EXCH1_IP} 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?{EXCH1_FQDN}:6001 - 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2021-03-03 17:43:19 {Visitor_IP} 60452 {3RD_EXCH_IP} 443 - - - - - - Timer_ConnectionIdle -

문제는 잠시 후에 스스로 해결되는 것처럼 보였지만 이제는 간헐적으로 보입니다. 예를 들어 지금 내 전화가 작동하고 집에 있는 내 PC의 Outlook은 그렇지 않지만 이전 버전이었습니다. OWA는 또한 더 일찍 503 오류를 제공하기 시작했지만 무작위로 중지했습니다(적어도 저에게는). 나는 MSExchangeRpcProxyAppPoolOWA와 내 전화를 사용할 수 있음에도 불구하고 오늘 아침에 여전히 일부 오류를 수 있었습니다.

Test-OutlookWebServices자동 검색이 실패하고 있음을 보여주지만 Outlook과 testconnectivity.microsoft.com을 사용하여 내부 및 외부적으로 테스트했으며 제대로 작동합니다. 그러나 OAB의 대기 시간은 옳지 않습니다.

Test-OutlookWebServices -Identity [email protected] -MailboxCredential (Get-Credential) -ClientAccessServer EXCH2

Source               ServiceEndpoint       Scenario                       Result  Latency(MS)
------               ---------------       --------                       ------  -------
{EXCH1_FQDN}         {EXCH2_FQDN}          Autodiscover: Outlook Provider Failure     242
{EXCH1_FQDN}         {EXCH2_FQDN}          Exchange Web Services          Success     124
{EXCH1_FQDN}         {EXCH2_FQDN}          Availability Service           Success     116
{EXCH1_FQDN}         {EXCH2_FQDN}          Offline Address Book           Success   17921


Test-OutlookWebServices -Identity [email protected] -MailboxCredential (Get-Credential) -ClientAccessServer EXCH1

Source               ServiceEndpoint       Scenario                       Result  Latency(MS)
------               ---------------       --------                       ------  -------
{EXCH1_FQDN}         {EXCH1_FQDN}          Autodiscover: Outlook Provider Failure     128
{EXCH1_FQDN}         {EXCH1_FQDN}          Exchange Web Services          Success      58
{EXCH1_FQDN}         {EXCH1_FQDN}          Availability Service           Success     110
{EXCH1_FQDN}         {EXCH1_FQDN}          Offline Address Book           Success   18053

Test-ActiveSyncConnectivity인증서 문제로 인해 실패했지만 할당된 인증서가 유효한 것으로 표시됩니다. 여기에서 어떤 인증서가 사용되었는지 어떻게 확인할 수 있습니까?

Test-ActiveSyncConnectivity -ClientAccessServer EXCH2 -MailboxCredential (Get-Credential)

CasServer  LocalSite     Scenario        Result  Latency(MS) Error
---------  ---------     --------        ------  ----------- -----
exch2      SiteName      Options         Failure             [System.Net.WebException
                                                            ]: The underlying
                                                             connection was closed:
                                                             Could not establish
                                                             trust relationship for
                                                             the SSL/TLS secure
                                                             channel. Inner error [Sy
                                                             stem.Security.Authentica
                                                             tion.AuthenticationExcep
                                                             tion]: The remote
                                                             certificate is invalid
                                                             according to the
                                                             validation procedure.

우리의 인증서. 여기에는 오래된 것들이 있지만 어떤 서비스에도 할당되지 않았습니다.

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {65******-****-****-****-************, {EXCH1}, {EXCH1_IP}, {3RD_EXCH_IP}, 169.254.1.63}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=MS-Organization-P2P-Access [2020]
NotAfter           : 05/03/2021 15:36:39
NotBefore          : 04/03/2021 15:31:39
PublicKeySize      : 2048
RootCAType         : Unknown
SerialNumber       : 21******************************
Services           : None
Status             : Invalid
Subject            : CN=65******-****-****-****-************, DC=46******-****-****-****-************
Thumbprint         : 7B*************************************

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {{EXCH1}}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=Exchange_{Company} Comm Group Root CA, OU=Exchange_{Company} Comm Group, O=ESET
NotAfter           : 03/03/2051 15:34:04
NotBefore          : 03/03/2021 15:34:04
PublicKeySize      : 2048
RootCAType         : Registry
SerialNumber       : 02
Services           : None
Status             : RevocationCheckFailure
Subject            : CN={EXCH1}, OU=Exchange_{Company} Comm Group, O=ESET
Thumbprint         : EC*************************************

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {65******-****-****-****-************, {EXCH1}, {EXCH1_IP}, {3RD_EXCH_IP}, 169.254.1.19, {EXCH1_FQDN}}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=MS-Organization-P2P-Access [2019]
NotAfter           : 05/06/2020 21:59:17
NotBefore          : 04/06/2020 21:54:17
PublicKeySize      : 2048
RootCAType         : Unknown
SerialNumber       : 42******************************
Services           : None
Status             : Invalid
Subject            : CN=65******-****-****-****-************, DC=46******-****-****-****-************
Thumbprint         : 9A*************************************

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {mail.domain.com, www.mail.domain.com, domain.com, autodiscover.domain.com}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US
NotAfter           : 22/10/2021 12:25:35
NotBefore          : 22/10/2019 12:25:35
PublicKeySize      : 2048
RootCAType         : ThirdParty
SerialNumber       : 1A******************************
Services           : IMAP, POP, IIS, SMTP
Status             : Valid
Subject            : CN=mail.domain.com, OU=Domain Control Validated
Thumbprint         : 72*************************************

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {65******-****-****-****-************, {EXCH1}, {EXCH1_IP}, {3RD_EXCH_IP}, 169.254.1.5, {EXCH1_FQDN}}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=MS-Organization-P2P-Access [2018]
NotAfter           : 06/07/2019 00:53:49
NotBefore          : 05/07/2019 00:48:49
PublicKeySize      : 2048
RootCAType         : Unknown
SerialNumber       : 50******************************
Services           : None
Status             : Invalid
Subject            : CN=65******-****-****-****-************, DC=46******-****-****-****-************
Thumbprint         : 37*************************************

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {65******-****-****-****-************, {EXCH1}, {EXCH1_IP}, {3RD_EXCH_IP}, 169.254.1.252, {EXCH1_FQDN}}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=MS-Organization-P2P-Access [2017]
NotAfter           : 05/08/2018 00:05:25
NotBefore          : 04/08/2018 00:00:25
PublicKeySize      : 2048
RootCAType         : Unknown
SerialNumber       : 3F******************************
Services           : None
Status             : Invalid
Subject            : CN=65******-****-****-****-************, DC=46******-****-****-****-************
Thumbprint         : 66*************************************

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {65******-****-****-****-************, {EXCH1}, {EXCH1_IP}, {3RD_EXCH_IP}, 169.254.1.80, {EXCH1_FQDN}}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=MS-Organization-P2P-Access [2016]
NotAfter           : 03/09/2017 20:59:10
NotBefore          : 02/09/2017 20:54:10
PublicKeySize      : 2048
RootCAType         : Unknown
SerialNumber       : 43******************************
Services           : None
Status             : Invalid
Subject            : CN=65******-****-****-****-************, DC=46******-****-****-****-************
Thumbprint         : 5B*************************************

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=Microsoft Exchange Server Auth Certificate
NotAfter           : 08/06/2022 09:39:03
NotBefore          : 04/07/2017 09:39:03
PublicKeySize      : 2048
RootCAType         : None
SerialNumber       : 4E******************************
Services           : SMTP
Status             : Valid
Subject            : CN=Microsoft Exchange Server Auth Certificate
Thumbprint         : 2B*************************************

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {{EXCH1}, {EXCH1_FQDN}}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN={EXCH1}
NotAfter           : 04/07/2022 09:37:32
NotBefore          : 04/07/2017 09:37:32
PublicKeySize      : 2048
RootCAType         : Registry
SerialNumber       : 18******************************
Services           : IIS, SMTP
Status             : Valid
Subject            : CN={EXCH1}
Thumbprint         : 65*************************************

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {WMSvc-SHA2-{EXCH1}}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=WMSvc-SHA2-{EXCH1}
NotAfter           : 28/06/2027 14:27:42
NotBefore          : 30/06/2017 14:27:42
PublicKeySize      : 2048
RootCAType         : Registry
SerialNumber       : 18******************************
Services           : None
Status             : Valid
Subject            : CN=WMSvc-SHA2-{EXCH1}
Thumbprint         : 68*************************************

exch1에서 exch2로 RPCP:

rpcping /t ncacn_http /s {EXCH2_FQDN} /o RpcProxy=mail.domain.com /P username,domain,* /H Basic /u NTLM /a connect /F 3
Enter password for RPC/HTTP proxy:

Exception 1722 (0x000006BA)
Number of records is: 3
ProcessID is 9396
System Time is: 3/4/2021 16:11:18:616
Generating component is 14
Status is 0x6C0, 1728
Detection location is 1398
Flags is 0
NumberOfParameters is 2
Long val: 0x4
Long val: 0x6c0
ProcessID is 9396
System Time is: 3/4/2021 16:11:18:603
Generating component is 13
Status is 0x6C0, 1728
Detection location is 1428
Flags is 0
NumberOfParameters is 1
Long val: 0x190
ProcessID is 9396
System Time is: 3/4/2021 16:11:18:603
Generating component is 13
Status is 0x190, 400
Detection location is 1417
Flags is 0
NumberOfParameters is 1
Unicode string: Invalid RPC Port: 593

testconnectivity.microsoft.com은 exch1의 데이터베이스에 있는 계정으로 결과를 얻습니다.

Testing Outlook connectivity.
The Outlook connectivity test failed.
Test Steps

The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected]
Autodiscover was tested successfully.
Test Steps

Autodiscover settings for Outlook connectivity are being validated.
The Microsoft Connectivity Analyzer validated the Outlook Autodiscover settings.

Testing MAPI over HTTP connectivity to server mail.domain.com
MAPI over HTTP connectivity was verified successfully.
Test Steps

Testing RPC over HTTP connectivity to server mail.domain.com
RPC over HTTP connectivity failed.
Test Steps

Attempting to resolve the host name mail.domain.com in DNS.
The host name resolved successfully.
Additional Details

Testing TCP port 443 on host mail.domain.com to ensure it's listening and open.
The port was opened successfully.

Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Test Steps

Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details

Testing HTTP Authentication Methods for URL https://mail.domain.com/rpc/[email protected]:6002.
The HTTP authentication methods are correct.
Additional Details

Attempting to ping RPC proxy mail.domain.com.
RPC Proxy was pinged successfully.

Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The endpoint was pinged successfully.
Additional Details

Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Test Steps

Testing the MAPI Referral service on the Exchange Server.
An error occurred while the Referral service was being tested.
Test Steps

Attempting to ping the MAPI Referral Service endpoint with identity: [email protected]:6002.
The endpoint was pinged successfully.
Additional Details

Attempting to perform referral for user on server [email protected]
An error occurred while trying to get the address book server.
Additional Details
An RPC error was thrown by the RPC Runtime process. Error -532462766 -532462766
RPC Status: -532462766 -532462766

testconnectivity.microsoft.com은 exch2의 데이터베이스에 있는 계정으로 결과를 얻습니다.

Testing Outlook connectivity.
The Outlook connectivity test failed.
Test Steps

The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected]
Autodiscover was tested successfully.
Test Steps

Autodiscover settings for Outlook connectivity are being validated.
The Microsoft Connectivity Analyzer validated the Outlook Autodiscover settings.

Testing MAPI over HTTP connectivity to server mail.domain.com
MAPI over HTTP connectivity failed.
Test Steps

Attempting to resolve the host name mail.domain.com in DNS.
The host name resolved successfully.
Additional Details

Testing TCP port 443 on host mail.domain.com to ensure it's listening and open.
The port was opened successfully.

Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Test Steps

Testing HTTP Authentication Methods for URL https://mail.domain.com/mapi/emsmdb/[email protected]
The HTTP authentication methods are correct.
Additional Details

Testing the MAPI Address Book endpoint on the Exchange server.
An error occurred while testing the address book endpoint.
Test Steps

Testing the address book "Check Name" operation for user [email protected] against server mail.domain.com.
An error occurred while attempting to resolve the name.
Additional Details
A protocol layer error occured. HttpStatusCode: 503
Failure LID: 47372
Failure Information:

###### REQUEST [2021-03-04T17:39:53.4083406Z] [ResolvedIPs: {EXCH_EXTERNAL_IP}] ######

POST /mapi/nspi/[email protected] HTTP/1.1
Content-Type: application/octet-stream
User-Agent: MapiHttpClient
X-RequestId: 199148da-e4e8-45cc-9109-8462a54e9449:1
X-ClientInfo: afeca7b0-830f-491d-874b-90e03f295d7c:1
client-request-id: 0917a5aa-f28e-4e11-95c0-460d6cc0b0bf
X-ClientApplication: MapiHttpClient/15.20.3825.0
X-RequestType: Bind
Authorization: Negotiate [truncated]
Host: mail.domain.com
Content-Length: 45

--- REQUEST BODY [+0.041] ---
..[BODY SIZE: 45]

--- REQUEST SENT [+0.041] ---

###### RESPONSE [+0.138] ######

HTTP/1.1 503 Failed authentication on backend server: Unauthorized
request-id: 6b446af9-fe00-403c-b390-038b740f3000
X-CalculatedBETarget: {EXCH2_FQDN}
X-FailureContext: BackEnd;401;NDAx;U3lzdGVtLk5ldC5XZWJFeGNlcHRpb246IFRoZSByZW1vdGUgc2VydmVyIHJldHVybmVkIGFuIGVycm9yOiAoNDAxKSBVbmF1dGhvcml6ZWQuDQogICBhdCBTeXN0ZW0uTmV0Lkh0dHBXZWJSZXF1ZXN0LkVuZEdldFJlc3BvbnNlKElBc3luY1Jlc3VsdCBhc3luY1Jlc3VsdCkNCiAgIGF0IE1pY3Jvc29mdC5FeGNoYW5nZS5IdHRwUHJveHkuUHJveHlSZXF1ZXN0SGFuZGxlci48PmNfX0Rpc3BsYXlDbGFzczE5OV8wLjxPblJlc3BvbnNlUmVhZHk+Yl9fMCgp;;;
Persistent-Auth: true
X-FEServer: {EXCH1}
Content-Length: 0
Cache-Control: private
Date: Thu, 04 Mar 2021 17:39:52 GMT
Server: Microsoft-IIS/10.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET

--- RESPONSE BODY [+0.139] ---

--- RESPONSE DONE [+0.139] ---

###### EXCEPTION THROWN [+0.139] ######


HTTP Response Headers:
request-id: 6b446af9-fe00-403c-b390-038b740f3000
X-CalculatedBETarget: {EXCH2_FQDN}
X-FailureContext: BackEnd;401;NDAx;U3lzdGVtLk5ldC5XZWJFeGNlcHRpb246IFRoZSByZW1vdGUgc2VydmVyIHJldHVybmVkIGFuIGVycm9yOiAoNDAxKSBVbmF1dGhvcml6ZWQuDQogICBhdCBTeXN0ZW0uTmV0Lkh0dHBXZWJSZXF1ZXN0LkVuZEdldFJlc3BvbnNlKElBc3luY1Jlc3VsdCBhc3luY1Jlc3VsdCkNCiAgIGF0IE1pY3Jvc29mdC5FeGNoYW5nZS5IdHRwUHJveHkuUHJveHlSZXF1ZXN0SGFuZGxlci48PmNfX0Rpc3BsYXlDbGFzczE5OV8wLjxPblJlc3BvbnNlUmVhZHk+Yl9fMCgp;;;
Persistent-Auth: true
X-FEServer: {EXCH1}
Content-Length: 0
Cache-Control: private
Date: Thu, 04 Mar 2021 17:39:52 GMT
Server: Microsoft-IIS/10.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET

HTTP Status Code: 503 ServiceUnavailable

도움을 주시면 대단히 감사하겠습니다.

answer

나는 약간의 연구를 수행했으며 이 문제는 인증서와 관련이 있을 수 있습니다.

  1. IIS에서 확인하여 IIS 서비스에 사용된 인증서를 확인합니다(바인드 인증서가 올바른지 확인).여기에 이미지 설명 입력

  2. 그런 다음 관리자 권한으로 CMD에서 IISReset을 실행합니다.

  3. 이 문제가 계속 발생하는지 확인하십시오.

또한 참조용으로 유사한 스레드가 있습니다. Exchange 2013 ECP/OWA/Outlook 모두 실패 - 503 서비스를 사용할 수 없음