Exchange 2013 EMS, ECP, OWA not working

Question

Exchange 2013 EMS, ECP, OWA not working

create share 676

Hi,

I am getting these errors after opening Exchange Management Shell, ECP, and OWA. CU 23 is installed. Secondly, there is a second internal website called 'internalEAC' to block the default ECP access.

Thanks.

New-PSSession : [mail.domain.com] Connecting to remote server mail.domain.com failed with the following
error message : [ClientAccessServer=mail,BackEndServer=mail.domain.com,RequestId=7eea727a-4b9f-4e7e-938b-e63
694f4115a,TimeStamp=12/11/2023 10:52:52 AM] [FailureCategory=Cafe-SendFailure]  For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed

User's image

2 answers

Your answer

Answer 1

Check the ECP virtual directory settings:

Check the web.config file:

Verify the ECP URL: You can check this by running the following command in Exchange Management Shell:

Get-EcpVirtualDirectory | Format-List InternalURL, ExternalURL

Restart IIS and Exchange services:

iisreset /restart

Restart-Service MSExchangeServiceHost

Restart-Service MSExchangeRPC

Check for browser issues:

Also, always run these commands after patching:

cd 'C:\Program Files\Microsoft\Exchange Server\v15\Bin'

.\UpdateCas.ps1

.\UpdateConfigFiles.ps1

iisreset

Microsoft documentation on about_Remote_Troubleshooting: https://learn.microsoft.com/en-us/exchange/troubleshoot/administration/connecting-remote-server-failed

Answer 2

Anonymous

Hi @create share ，

Based on the situation you described, since the problem only occurred recently, I would like to know if you have performed any special operations on the certificate or server before and did these problems occur after adding this internalEAC site? Also, it is recommended that you check the event viewer to see if there are any error messages providing details about the issue.

In addition, it is speculated that it may be related to certificate binding. Please ensure that Exchange and the Exchange backend website use the correct certificate in IIS (edit the binding), and then restart the website or IIS.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

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.

create share 676 Reputation points

2023-12-13T09:47:55.4333333+00:00

The certificate is expired but OWA, ECP stopped working before that. Now I am not able to renew the certificate because Exchange Mgmt Shell is not working as well. InternalEAC was added a long time ago and everything was working fine. To disable InternalEAC, do I have to only remove the directory and the second IP Address?
Anonymous

2023-12-14T09:57:14.0566667+00:00

According to what you said, the internalEAC actually existed a long time ago, so this problem may have nothing to do with it and we can just not change it yet.

Based on our search, the reason may also be that the self-signed certificate bound to the Exchange Back End website is lost. It is recommended that you check again to confirm.
create share 676 Reputation points

2023-12-14T23:54:27.0033333+00:00

When I try to change the self-signed certificate, I get the below error message.
Anonymous

2023-12-18T09:56:53.85+00:00

Hi，I would like to know if you have a third-party certificate and is there a way to renew your third-party certificate?
create share 676 Reputation points

2023-12-19T08:21:37.4566667+00:00

Unfortunately no. I am using internal CA.
Anonymous

2023-12-20T08:06:07.9733333+00:00

Thanks for the reply. We suggest you try using remote powershell. If possible, follow this document to add the certificate back to the Exchange backend website by creating a new self-signed certificate, and then bind it to the Exchange backend website.

If that doesn't work, could you please provide some information on what we asked about earlier, like if there were any error messages in Event Viewer and if you did anything special with the certificate or server before the problem occurred so that we can see if more clues can be found?

Share via

Exchange 2013 EMS, ECP, OWA not working

2 answers

Your answer