Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Exchange 2013 - Outlook cannot connect, and OWA / ECP inaccessible

Posted on 2013-06-23
8
Medium Priority
?
4,723 Views
Last Modified: 2015-11-11
Running Exchange 2013 with CU1 installed on Windows Server 2012. Still using default self-signed certificates at the moment.  Everything was running fine until I installed the Remote Access Role on the server, and restarted.  When the server came back up, Outlook clients will no longer connect to Exchange, and both the OWA and ECP web pages give "Page cannot be displayed".  

I'm not clear whether the server restart was the trigger for the issue, or the installation of the Remote Access Role.

I uninstalled the Remote Access Role once again and restarted.  However, the Exchange problem remains.

I tried temporarily disabling the Windows Firewall, in case installation of the Remote Access Role changed some firewall rules.  But it didn't help.

All services which are set to start up Automatically are started.

In terms of diagnostic information in the Event Logs, there seems very little to go on.  The only one that I think might have a bearing on the issue is an Event 5011 from "WAS" in the System Event Log.  It reads "A process serving application pool 'MSExchangeRpcProxyAppPool' suffered a fatal communication error with the Windows Process Activation Service.".

Any suggestions, please?
0
Comment
Question by:wakatashi1
  • 5
  • 2
8 Comments
 

Author Comment

by:wakatashi1
ID: 39269306
I found this article: http://www.techieshelp.com/exchange-2013-eac-ecp-blank-screen/.

I've tried all of the suggestions in that article - the SSL certificate related suggestion, and the one relating to recreating OWA and ECP virtual directories.   I had high hopes, but regrettably I'm no further forward.
0
 
LVL 23

Expert Comment

by:Stelian Stan
ID: 39269337
I would start by doing a Remote Connectivity Analyze and collect more information:
https://www.testexchangeconnectivity.com/
0
 

Author Comment

by:wakatashi1
ID: 39269350
Virtual directory authentication types as referenced in this article are OK:

http://lyncdude.net/2013/02/07/cannot-access-exchange-contorl-panel-ecp-in-exchange-server-2013/

...and I've followed the advice in this article:

http://support.microsoft.com/kb/2778897

...but with no luck.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:wakatashi1
ID: 39269373
Hi clonyxlro,

Thanks for getting back to me on this.

Possibly relevant info: we're running the default self-signed cert at present.  

I've changed references to the domain in the info below to "mail.domain.com".

RPC/HTTP test:

 
Testing RPC/HTTP connectivity.
 	The RPC/HTTP test 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 SSL certificate failed one or more certificate validation checks.
 	
	Test Steps
 	
	The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.domain.com on port 443.
 	The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
 	
	Additional Details
 	The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.

Open in new window


...and Exchange Activesync test:

The Microsoft Connectivity Analyzer is testing Exchange ActiveSync.
 	The Exchange ActiveSync test 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 SSL certificate failed one or more certificate validation checks.
 	
	Test Steps
 	
	The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.domain.com on port 443.
 	The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
 	
	Additional Details
 	The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.

Open in new window

0
 

Accepted Solution

by:
wakatashi1 earned 0 total points
ID: 39269480
Well, clonyxlro's suggestion to use the Exchange Remote Connectivity Analyser gave me the info I needed to fix this.  What had happened was that the Default Web Site in IIS had no binding for SSL on port 443.  It must've had one before, and I certainly didn't remove the binding.  I can't imagine how this happened, but am very, very glad that it's fixed!

Thanks clonyxlro.
0
 
LVL 23

Expert Comment

by:Stelian Stan
ID: 39269524
No problem. Glad that I could help you.
0
 

Author Closing Comment

by:wakatashi1
ID: 39283772
clonyxlro gave a suggestion as to how to find more information about the problem.  Having obtained the information, I reached a solution myself.  However, would like to give clonyxlro some credit.  Am a newbie on Experts Exchange - so will need to find out how this is done.
0
 

Expert Comment

by:kwall24
ID: 41228086
What was your answer? I think I have the same problem.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this post, we will learn to set up the Group Naming policy and will see how it is going to impact the Display Name and the Email addresses of the Group.
Upgrading from older Exchange server to the latest Exchange server can be tiresome, error-prone and risky, without being a seasoned exchange server administrators. It can become even problematic if you're an organization that runs on tight timeline…
This video discusses moving either the default database or any database to a new volume.
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Suggested Courses
Course of the Month11 days, 10 hours left to enroll

564 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question