This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 17%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
I'm running into an issue where outlook cannot connect to Exchange. When I try the connectivity analyzer I get the following.
Attempting to ping RPC proxy mail.redacted.us.
RPC Proxy can't be pinged.
Additional Details
An unexpected network-level exception was encountered. Exception details:
Message: The remote server returned an error: (500) Internal Server Error.
Type: Microsoft.Exchange.Tools.ExRca.Extensions.MapiTransportException
Stack trace:
at Microsoft.Exchange.Tools.ExRca.Extensions.MapiRpcTestClient.PingProtocolProxy(String endpointIdentifier)
at Microsoft.M365.RCA.ConnectivityTests.MapiPingProxyTest.PerformTestReally() in >
d:\dbs\sh\nibr\0406_035353_0\cmd\8\sources\dev\m365rca\src\connectivitytests\Mapi\MapiPingProxyTest.cs:line 60
Exception details:
Message: The remote server returned an error: (500) Internal Server Error.
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at RpcPingLib.RpcPing.PingProxy(String internalServerFqdn, String endpoint)
at Microsoft.Exchange.Tools.ExRca.Extensions.MapiRpcTestClient.PingProtocolProxy(String endpointIdentifier)
Obviously there's an issue somewhere. But for the life of me I can't figure out what it may be.
C:\Windows\system32>Get-OutlookAnywhere |fl
RunspaceId : aa63ad70-a1b4-4837-a847-f7e17f5563d6
ServerName : redacted
SSLOffloading : False
ExternalHostname : mail.redacted.us
InternalHostname : mail.redacted.us
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod : Negotiate
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : True
MetabasePath : IIS://redacted.local/W3SVC/1/ROOT/Rpc
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.2 (Build 858.5)
Server : redacted
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN= ,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=thi,DC=local
Identity : redacted\Rpc (Default Web Site)
Guid : bfc62afc-daa7-464d-8f3d-3cf94b93647d
ObjectCategory : redacted/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 4/13/2021 5:46:42 PM
WhenCreated : 4/12/2020 5:37:52 PM
WhenChangedUTC : 4/13/2021 9:46:42 PM
WhenCreatedUTC : 4/12/2020 9:37:52 PM
OrganizationId :
Id : \Rpc (Default Web Site)
OriginatingServer : redacted .local
IsValid : True
ObjectState : Changed
How can I attempt to figure out what's causing the 500 internal error?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 82%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEY%3C/text%3E%3C/svg%3E)
Hi,
Do you mean external users or internal users cannot connect to Outlook?
Exchange 2019 uses MAPI by default, you should check MAPI configuration rather than OutlookAnywhere:
Get-MapiVirtualDirectory|fl
This article for your reference: Configure MAPI over HTTP in Exchange Server
Do you have any firewall or third-party tools installed? Test again with them closed.
Both internal and external users cannot connect. I tried enabling mapi to see if that made a difference and it did not unfortunately. Still getting an rpc error 500 internal server error.
[PS] C:\Windows\system32>Test-OutlookConnectivity -RunFromServerId thi-mx2 -ProbeIdentity OutlookMapiHttpSelfTestProbe
WARNING: Failed Probe Result Details:
Error: The remote server returned an error: (500) Internal Server Error.
Exception: System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.Exchange.RpcClientAccess.Monitoring.VerifyRpcProxyClient.VerifyRpcProxyContext.OnEnd(IAsyncResult asyncResult)
at Microsoft.Exchange.RpcClientAccess.Monitoring.ClientCallContext`1.InternalEnd(IAsyncResult asyncResult)
I've rebooted the server on multiple occasions.
However I tried recycling the application pool like you said.
Same issue.
There is an issue server side that is giving a 500 internal error. More than likely something got misconfigured when we were doing an update. Need to figure out what to look for to fix this issue.
what kind of update you did and share if you find any errors in exchange setup log (under c:)
Try recycling the Application Pools in IIS console
Go to Internet Information Services (IIS) Manager.
Open application pools
Then select the application pool “MSExchangeAutodisocverAppPool”
In the Actions pane, click Recycle
updating to the latest cu.
I really don't have a way of sharing the log file it's too big to attach.
Provide couple of more details like whether EAC/OWA is working or not? You may send some lines showing error message in logs also
owa is working.
I did notice this. When I turn on the request tracing in IIS I get this error.
-Request Summary
Site
2
Process
13260
Failure Reason
STATUS_CODE
Trigger Status
500
Final Status
500
Time Taken
16 msec
Url
https://server.local:444/rpc/rpcproxy.dll?localhost:6001
App Pool
MSExchangeRpcProxyAppPool
Authentication
Negotiate
User from token
domain\server$
Activity ID
{8000185F-0001-DA00-B63F-84710C7967BB}
-Errors & Warnings
No.↓
Severity
Event
Module Name
ModuleName
IsapiModule
Notification
EXECUTE_REQUEST_HANDLER
HttpStatus
500
HttpReason
Internal Server Error
HttpSubStatus
0
ErrorCode
The specified procedure could not be found.
(0x8007007f)
ConfigExceptionInfo
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 38%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
The error message "The specified procedure could not be found. (0x8007007f)" is leading me to believe that there is a dll file missing somewhere or that it's out of date.
Just another approach: Get the health report of mailbox server and see any issues found:
Get-HealthReport -Identity Mailbox01-RollupGroup
Here is a similar reference which can help further troubleshooting: exchange-managed-availability-error-outlookrpcselftestprobe
WARNING: A server-side Active monitoring operation has failed. Microsoft Exchange Health Manager (MSExchangeHM) service may not be running on server
mailbox01-rollupgroup. Specific RPC error message: Error 0x6ba (The RPC server is unavailable) from cli_RpccGenericRequest
Again rpc issues.
Same Exact Issue Here. April 2021 Exchange patch failed and RPC stopped working. We tried to reapply CU 23, CU applied successfully but did not resolve the issue. We also just re applied the april 2021 update, which succeeded but the RPC issue still remains, internal server error 500.
I can't find a good reason why this is happening. And trying to diagnose a 500 leads to just a vague fix.
We ended up just installing a new exchange server and starting fresh.