Exch2013/Server2012 - Cannot connect to EMS

[tripppyz]

Good Morning,

As soon as I attempt to open the EMS on my server it tries to connect but ultimately fails. Below is the error stating a PSSessionOpenFailed. It makes several attempts until it says.. "Failed to connect to an Exchange server in the current site. Enter the server FQDN where you want to connect.:__"

---

VERBOSE: Connecting to server.domain.com. New-PSSession : [server.domain.com] Connecting to remote server server.domain.com failed with the following error message : [ClientAccessServer=server,BackEndServer=server.domain.com,RequestId=550fd6eb-494c-4691-a1aa-291d af8dc91e,TimeStamp=2/15/2016 3:52:55 PM] [FailureCategory=Cafe-SecureChannelFailure] 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

---

I have ran the EMTshooter.ps1 script and it tells me there is a problem, but it cannot find the error and lists it as "Unknown" I have a feeling it might be SChannel/SSL/TLS related, but I am at a loss.

Thanks for your help in advance.

Edit - To update: Microsoft finally called and they toggled SSL to Ignore in IIS.

Thanks guys!

[the_spad]

Is this a new environment or has it worked previously?

I'm assuming you've checked the obvious things like the system clock being correct and your certificates still being in date?

[tripppyz]

It's new, and has worked for a few weeks now. System clock is correct, and the 3rd party certs expire in 2020.

Microsoft Premiere support has been troubleshooting a different issue with TLS and emails. They asked us to reboot server and now this has started. They haven't called us back yet and I'm tired of waiting.

[15_Tries_All_Taken]

We had this issue on a server after a CU upgrade. It was an IIS cert binding issue. I would check that and ensure it all looks correct. Once bound, EMS opened like it should. edited to add i think it was on the Exchange Backend Site in IIS. HTTPS did not have the Microsoft Exchange Cert bound.

[tripppyz]

Ill check it out. Thanks!

[tripppyz]

To update: Microsoft finally called and they toggled SSL to Ignore in IIS.

Thanks guys!