Error when opening Organization > Apps in Exchange 2013 ECP: The underlying connection was closed: an unexpected error occurred on a receive

Question

Error when opening Organization > Apps in Exchange 2013 ECP: The underlying connection was closed: an unexpected error occurred on a receive

Shawn 16

As the title says, this error comes up when I'm in ECP and open Organization > Apps. If I refresh a few times the apps show up but refreshing again will bring the error up again.

I have 2 servers and, if I run the "Get-App" command on one, it lists the apps. However, running it on the second server produces essentially the same error that comes up in ECP when opening the Apps page:

The request failed. The underlying connection was closed: An unexpected error occurred on a receive.

CategoryInfo : InvalidOperation: (:) [Get-App], OwaExtensionOperationException
FullyQualifiedErrorId : [Server=<Server Name>,RequestId=768a4ef0-c38c-40fb-978b-a21e97752d1a,TimeStamp=9/1/2021 2:
47:44 PM] [FailureCategory=Cmdlet-OwaExtensionOperationException] 773C62A2,Microsoft.Exchange.Management.Extension
.GetApp
PSComputerName :<Server FQDN>

Any tips for getting this resolved are much appreciated. I have done some searching for the "The underlying connection was closed: An unexpected error occurred on a receive." and checked some of the suggestions that I found (both servers are running the same .net framework version, both have TLS 1.0, 1.1, and 1.2 enabled).

Aside from that I'm not seeing anything that's really relevent to my issue of this error coming up when running this specific command or from just opening the Apps page in ECP (most are from people trying to run a custom app).

4 answers

Your answer

Answer 1

Shawn 16

Hello, this has been resolved. It ended up being caused by an IP address restriction that was restricting outside access to ECP.

Answer 2

Hi @Shawn ,

The error message shows it is related to a TCP request failure. Please try re-enable TLS 1.0 and TLS 1.2.

In addition, what is the version of your Exchange? Update it to the latest version or 2016 is also a good idea.

Best regards,
Lou

If the response 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.

Answer 3

Shawn 16

I assume by "re-enable TLS 1.0 and 1.2" you mean to disable the reg values for TLS 1.0 and 1.2, reboot and then re-enable and reboot again?

Both servers are Exchange 2013 on-prem.

Anonymous

2021-09-03T07:20:52.867+00:00

Hi @Shawn ,

Yes, I found some similar posts and fixed this by re-enabling the TLS 1.0 and 1.2. And also please try disbaling 1.0 and 1.1 to test.

What's the CU number? You could check it using Get-ExchangeServer | FL Name,AdminDisplayVersion
And compare the build number with this:
https://learn.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserver-2019

Best regards,
Lou
Shawn 16 Reputation points

2021-09-03T14:24:31.143+00:00

Thanks for the reply. I'm on vacation for a week after today so will try disabling and re-enabling when I get back.

Our servers are on version 15.0.1497.2 (CU23).
Anonymous

2021-09-06T06:32:20.677+00:00

Okey, have a nice vacation.

Cheers,
Lou
Shawn 16 Reputation points

2021-09-22T03:04:43.22+00:00

Tried disabling TLS 1 and 1.2 and then rebooting, then re-enabling it and rebooting and that didn't resolve the issue. Any other ideas?

Edit: Actually, the issue moved over to my other server after I re-enabled it on the problem server and rebooted. So I did the same to the other server (disabled and re-enabled TLS 1.0 and 1.2) then rebooted, and the issue moved back to the original server with the issue.

To add to this, it looks like the issue is following whichever server is active at the time.
Anonymous

2021-09-24T05:41:12.353+00:00

Hi @Shawn ,

OK, that sounds crazy.

Please check the registry value of the TLS 1.2 and .Net framework in your servers, make sure it's correct like: https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client

And after that, try disabling TLS 1.0 and 1.1 and enabling TLS 1.2 to test.

Best regards,
Lou
Shawn 16 Reputation points

2021-09-28T14:47:04.477+00:00

Made sure all those registry settings were correct and installed all available updates. Still no dice.

I also noticed that the error comes up when I go to "Compliance Management > in-place eDiscovery & hold" as well.
Anonymous

2021-09-30T06:38:07.357+00:00

Hi @Shawn ,

Would you like to try disableing TLS 1.0 and 1.1? I know this is ridiculous but this issue is related with the TLS settings.
And in addition, have you tried using another account to open the EAC page? And on another computer?

Best regards,
Lou
Shawn 16 Reputation points

2021-10-04T15:12:34.823+00:00

I have tried disabling TLS 1.0 and 1.1 and only having TLS 1.2 enabled and it's the same issue.

My coworker has tried on his computer with his credentials and gets the same message.

Answer 4

Anonymous

Hello @Shawn ,

So sorry for some reasons that it's been a time since my last reply:(

Please also try recreating the system mailboxes: https://learn.microsoft.com/en-us/exchange/recreating-arbitration-mailboxes-exchange-2013-help
And you can migrate these system mailboxes to other database to test.

A related thread that may help: https://social.technet.microsoft.com/Forums/exchange/en-US/bd2abdd7-cafa-4a02-bec8-62aa95811932/exchange-2013-can-not-upload-apps?forum=exchangesvrdeploy

Best regards,
Lou

Shawn 16 Reputation points

2021-10-13T21:56:53.803+00:00

Thanks. I'll try that one of these evenings when I get a chance.

Share via

Error when opening Organization > Apps in Exchange 2013 ECP: The underlying connection was closed: an unexpected error occurred on a receive

4 answers

Your answer