Quantcast
Channel: Exchange Server 2013 - General Discussion forum
Viewing all articles
Browse latest Browse all 4521

Exchange 2013 CU11 has broken the entire Exchange test farm: CAS can't connect to MBX anymore

$
0
0

I have a test environment closely reproducing our production Exchange 2013 servers: two pure mailbox servers and two pure CAS servers. The first two servers support a DAG with a single mailbox database, and CASes are jointed to an NLB cluster.

The previous version of Exchange was CU8, and everything worked fine. Several days ago I started testing CU11 before upgrading our production servers. After installing it the entire farm stopped working, as CAS servers can't connect to MBX servers for proxying anymore. Among other things, when I open OWA or ECP on one of CAS servers, it accepts user credentials (only valid ones!) but after that shows an absolutely empty page (no even error messages). Outlook can't connect to Exchange, too ("No connection", and that's it). When I start EMS on the CAS servers, it tries to connect to both CAS servers first and fails ("FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed"), then connects to one of MBXs normally. So the farm is effectively dead even in spite of the database's working properly.

No errors in Application logs on all servers. All Exchange components on all servers are enabled, all Exchange services and IIS sites are running. I even generated fresh SSL certificates for all servers, but to no effect. I don't know how to troubleshoot it any further.

Any ideas?


Evgeniy Lotosh // MCSE: Server infrastructure, MCSE: Messaging


Viewing all articles
Browse latest Browse all 4521

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>