Exchange 2013 error testconnectivity.microsoft.com and outlook anywhere connections

Alexey Alexandrov 1 Reputation point
2021-05-31T08:30:08.9+00:00

Hello.

Installed exchange 2013. Initially there was a coexistence mode with exch 2007. Now exch 2007 is completely removed. There is a problem of working outlook anywhere from the Internet through a reverse proxy to exchange. Sent emails hang in outgoing and are not sent. Inside the local network, outlook works without problems. This also fails the test from https://testconnectivity.microsoft.com. Error:

The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.ptenergo.ru:443/Autodiscover/Autodiscover.xml for user ******@ptenergo.ru.The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.

Additional Details

A Web exception occurred because an HTTP 400 - 400 response was received from Unknown.
HTTP Response Headers:
X-Tracking-Ref: <0.21349.2125>
X-Execution-Time: 1351
Connection: keep-alive
Keep-Alive: timeout=3, max=5
Access-Control-Allow-Origin: *
Access-Control-Allow-Credentials: true
Content-Length: 326
Content-Type: text/html; charset=us-ascii
Date: Tue, 18 May 2021 08:23:59 GMT

Server: Microsoft-HTTPAPI/2.0

Also on exchange there is an error when running the Test-OutlookConnectivity -ProbeIdentity "outlookrpcctpprobe" -hostname e2013 | fl

here is the result

[PS] C:\Windows\system32>Test-OutlookConnectivity -ProbeIdentity "outlookrpcctpprobe" -hostname e2013 | fl
WARNING: Failed Probe Result Details:
Error: Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
Exception: Microsoft.Exchange.RpcClientAccess.RopExecutionException: Error returned in LogonCallResult. Error code =
WrongServer (0x00000478)

RunspaceId : 7a3a318b-2d7c-458a-8213-03792c09d0c3
Server : e2013.ptecorp.ptenergo.ru
MonitorIdentity : Outlook\OutlookRpcCtpProbe
RequestId : 1cacae52-9a85-4870-a961-bd2d5ece61e2
ExecutionStartTime : 28.05.2021 10:22:48
ExecutionEndTime : 28.05.2021 10:22:48
Error : Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
Exception : Microsoft.Exchange.RpcClientAccess.RopExecutionException: Error returned in LogonCallResult. Error
code = WrongServer (0x00000478)
PoisonedCount : 0
ExecutionId : 55313167
SampleValue : 176,2159
ExecutionContext : RpcProxy connectivity verification
Task produced output:

  • TaskStarted = 28.05.2021 13:22:48
  • TaskFinished = 28.05.2021 13:22:48
  • ErrorDetails =
  • Latency = 00:00:00.0542551
  • RequestUrl = https://e2013/rpc/rpcproxy.dll?******@ptecorp.pte
    nergo.ru:6001
  • ResponseStatusCode = OK
  • RequestedRpcProxyAuthenticationTypes = basic
  • RespondingHttpServer = E2013
  • RespondingRpcProxyServer = e2013.ptecorp.ptenergo.ru
  • ResponseHeaderCollection = Transfer-Encoding: chunked
    request-id: 4d740031-f28f-4ef2-a15f-fc6f6f5a3364
    X-CalculatedBETarget: e2013.ptecorp.ptenergo.ru
    X-DiagInfo: E2013
    X-BEServer: E2013
    X-FEServer: E2013
    Connection: close
    Cache-Control: private
    Content-Type: application/rpc
    Date: Fri, 28 May 2021 10:22:47 GMT
    Set-Cookie: ClientId=NWGSDR0EBJLLJOIUQ; expires=Sat, 28-May-2022 10:22:48 GMT; path=/; HttpOnly
    Server: Microsoft-IIS/8.5
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET

RpcProxy connectivity verification completed successfully.
Mailbox logon verification
EMSMDB.Connect()
Task produced output:

  • TaskStarted = 28.05.2021 13:22:48
  • TaskFinished = 28.05.2021 13:22:48
  • ErrorDetails =
  • RespondingRpcClientAccessServerVersion = 15.0.1497.4012
  • RequestUrl = https://e2013/rpc/rpcproxy.dll?5db5e8e3-c08f-4c16-95cc-7a655a0dabc2@ptecorp
    .ptenergo.ru:6001
  • RespondingHttpServer = <null>
  • RespondingRpcProxyServer = <null>
  • ResponseHeaderCollection =
  • ResponseStatusCode = 0
  • ResponseStatusCodeDescription = <null>
  • RequestHeaderCollection =
  • Latency = 00:00:00.1184938
  • ActivityContext = I32:ATE.C[ptepdc.ptecorp.ptenergo.ru]=2;F:ATE.AL[ptepdc.ptecorp.ptener
    go.ru]=0;I32:ADS.C[root1]=1;F:ADS.AL[root1]=3.0808;I32:ADS.C[ptepdc]=2;F:ADS.AL[ptepdc]=1.7176;I32
    :ATE.C[root1.ptecorp.ptenergo.ru]=1;F:ATE.AL[root1.ptecorp.ptenergo.ru]=16
    EMSMDB.Connect() completed successfully.
    EMSMDB.DoRpc(Logon)
    Task produced output:
  • TaskStarted = 28.05.2021 13:22:48
  • TaskFinished = 28.05.2021 13:22:48
  • Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException: Error returned in
    LogonCallResult. Error code = WrongServer (0x00000478)
  • ErrorDetails =
  • ResponseHeaderCollection =
  • ResponseStatusCode = 0
  • ResponseStatusCodeDescription = <null>
  • RequestHeaderCollection =
  • Latency = 00:00:00.0034670
  • ActivityContext = I32:ATE.C[ptepdc.ptecorp.ptenergo.ru]=2;F:ATE.AL[ptepdc.ptecorp.ptener
    go.ru]=0;I32:ADS.C[root1]=1;F:ADS.AL[root1]=3.0808;I32:ADS.C[ptepdc]=2;F:ADS.AL[ptepdc]=1.7176;I32
    :ATE.C[root1.ptecorp.ptenergo.ru]=1;F:ATE.AL[root1.ptecorp.ptenergo.ru]=16
    EMSMDB.DoRpc(Logon) failed.
    Task produced output:
  • TaskStarted = 28.05.2021 13:22:48
  • TaskFinished = 28.05.2021 13:22:48
  • Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException: Error returned in Logo
    nCallResult. Error code = WrongServer (0x00000478)
  • ErrorDetails =
  • ActualBinding = ncacn_http:5db5e8e3-c08f-4c16-95cc-7a655a0dabc2\@ptecorp.ptenergo.ru[6001,Rp
    cProxy=e2013:443\, HttpProxy=<none>]
    Mailbox logon verification failed.

FailureContext :
ExtensionXml :
ResultType : Failed
RetryCount : 0
ResultName : 1cacae529a854870a961bd2d5ece61e2-OutlookRpcCtpProbe
IsNotified : False
ResultId : 569458862
ServiceName : InvokeNow
StateAttribute1 : ActiveManager
StateAttribute2 : Passive
StateAttribute3 : e2013
StateAttribute4 : Unknown
StateAttribute5 : {4BA98CA0-F08A-4FC4-A467-1E13963813D5}
StateAttribute6 : 0
StateAttribute7 : 0
StateAttribute8 : 0
StateAttribute9 : 0
StateAttribute10 : 0
StateAttribute11 : Momt
StateAttribute12 :
StateAttribute13 : @ptecorp.ptenergo.ru
StateAttribute14 :
StateAttribute15 : I32:ATE.C[ptepdc.ptecorp.ptenergo.ru]=2;F:ATE.AL[ptepdc.ptecorp.ptenergo.ru]=0;I32:ADS.C[root1]=1;
F:ADS.AL[root1]=3.0808;I32:ADS.C[ptepdc]=2;F:ADS.AL[ptepdc]=1.7176;I32:ATE.C[root1.ptecorp.ptenerg
o.ru]=1;F:ATE.AL[root1.ptecorp.ptenergo.ru]=16
StateAttribute16 : 0
StateAttribute17 : 0
StateAttribute18 : 0
StateAttribute19 : 0
StateAttribute20 : 0
StateAttribute21 : /o=ptecorp/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=c04cb1d8724149fc8fb
8e95c979be4d2-HealthMailbox195
StateAttribute22 : EMSMDB.DoRpc(Logon)
StateAttribute23 : https://e2013/rpc/rpcproxy.dll?
@ptecorp.ptenergo.ru:6001
StateAttribute24 : Basic
StateAttribute25 : [54]28.05.2021 13:22:48 RpcProxy connectivity verification; [118]28.05.2021 13:22:48 EMSMDB.Conn
ect(); [3]28.05.2021 13:22:48 [FAILED!] EMSMDB.DoRpc(Logon);
Identity : 851cbfcef0244f659909f930f78ecbed
IsValid : True

ObjectState : New

Help me please.

Exchange | Exchange Server | Management
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Eric Yin-MSFT 4,396 Reputation points
    2021-06-01T01:19:59.683+00:00

    Hi,
    This is usually caused by invalid HealthMailboxes (e.g. health mailboxes that no longer exist or have been moved because a database has changed).

    You can attempt to resolve the situation, but it's probably more easier to simply let the Exchange Health Monitor re-create the HealthMailboxes.

    1 On each Exchange mailbox server, stop the Microsoft Exchange Health Manager service.

    net stop MSExchangeHM  
    

    2 Remove all HealthMailbox accounts in Active Directory.
    They are in the Microsoft Exchange System Objects/Monitoring Mailboxes container.

    3 On each Exchange mailbox server, start the Microsoft Exchange Health Manager service.

    net start MSExchangeHM  
    

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.