Exchange 2016 OWA和ActiveSync 503错误
Exchange 2016 OWA和ActiveSync 503错误
提问于 2021-03-04 18:29:39
我们得到了断断续续503错误的OWA和ActiveSync与Exchange 2016。这些错误似乎只影响数据库中的帐户，这些帐户在前端服务器上不活动，因此似乎存在一个问题，将用户代理到他们的邮箱中。这些问题是在应用Hyper检查点之后开始的，我将在下面进一步解释.我不明白为什么会发生这样的事情，因为我做检查站的时候一切都正常。
配置
我们有两个Exchange2016服务器运行CU18。服务器位于DAG中，并且都安装了所有角色。我们的所有数据库都在两个服务器上进行复制，其中一半在每个服务器上都处于活动状态。我们没有任何DNS负载平衡设置，因此每台服务器都有自己的永久IP，我们将mail.domain.com的DNS指向第三个IP，如果需要在一个服务器上执行维护，则手动移动该IP，但是如果需要在一个服务器上执行维护，则该IP将保持在一个服务器上。我们的DNS是分开的，即我们的内部和外部DNS分别指向内部和外部IP。两个服务器都使用相同的SSL SAN证书，该证书由受信任的公共CA签名，证书有效并分配给服务。
发生了什么，
就Exchange而言，一切都很顺利。我注意到，AV /反垃圾邮件等的管理代理存在问题，无法连接到某个交换服务器上的AV服务器。重新安装代理没有解决问题，因此AV技术支持询问他们是否可以在一台服务器上重新安装整个安全包(让我们只调用服务器exch1)。然后，通过运行exch1并将前面提到的第三个IP移动到exch2，我将C:\Program Files\Microsoft\Exchange\V15\Scripts\StartDagMaintenance.ps1置于维护模式中。在确认所有数据库副本都已在exch2上激活后，我使用了exch1的Hyper检查点。然后删除并重新安装安全包，从而解决了代理的问题。然而，我们意识到共享隔离实际上存储在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 -这些问题在一段时间后似乎已经解决了，但现在似乎是断断续续的。例如，现在我的手机在工作，而Outlook在我的电脑上在家不是，而是更早。OWA也开始再犯503个错误，但随后随机停止(至少对我来说是这样)。今天早上，我仍然可以看到一些MSExchangeRpcProxyAppPool错误，尽管我可以使用OWA和我的手机。
Test-OutlookWebServices显示自动发现失败了，但我已经使用Outlook和testconnectivity.microsoft.com对其进行了内部和外部测试，并且运行良好。但是，OAB上的延迟是不正确的。
Test-OutlookWebServices -Identity me@domain.com -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 me@domain.com -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 18053Test-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*************************************RPCPing从exch1到exch2：
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: 593testconnectivity.microsoft.com的结果是在exch1上的数据库中有一个帐户：
Testing Outlook connectivity.
The Outlook connectivity test failed.
Test Steps
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for email@domain.com.
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/rpcproxy.dll?28eeaf00-7521-49c4-96cb-17f8068514de@domain.com: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: 28eeaf00-7521-49c4-96cb-17f8068514de@domain.com: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: 28eeaf00-7521-49c4-96cb-17f8068514de@domain.com:6002.
The endpoint was pinged successfully.
Additional Details
Attempting to perform referral for user on server 28eeaf00-7521-49c4-96cb-17f8068514de@domain.com.
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 -532462766testconnectivity.microsoft.com的结果是在exch2上的数据库中有一个帐户：
Testing Outlook connectivity.
The Outlook connectivity test failed.
Test Steps
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for exch2_email@domain.com.
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/?MailboxId=3b7a0102-7dfd-43c2-835b-502c7718a50c@domain.com.
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 exch2_email@domain.com 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/?mailboxId=3b7a0102-7dfd-43c2-835b-502c7718a50c@domain.com 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任何帮助都将不胜感激。
回答 1
Server Fault用户
发布于 2021-03-05 02:53:36
我做了一些研究，这个问题可能与证书有关。
- 从IIS检查以确认用于IIS服务的证书(确保绑定证书是正确的)：
- 然后在具有管理员权限的CMD中运行IISReset。
- 检查这个问题是否还在继续。
此外，下面还有一个类似的线程供您参考：Exchange2013 ECP/OWA/Outlook所有失败的503服务不可用
页面原文内容由Server Fault提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://serverfault.com/questions/1055957
复制相关文章
相似问题
腾讯云开发者
