Hi All,

We have a C#.net application (developed in Framework v4.0) which uses System.Management.Automation to connect to Office365 and modify CAS Settings of some mailboxes using the Set-CASMailBox cmd.

Below is the code for creating runspace:

runspace = RunspaceFactory.CreateRunspace(new WSManConnectionInfo(new Uri(exPowershellURI), shellURI, new PSCredential(psUserName, securePassword)) { AuthenticationMechanism = AuthenticationMechanismToUse(), SkipCACheck = true, SkipCNCheck = true, MaximumConnectionRedirectionCount = 4 }); runspace.Open();

 

In the above code variable values are set from config file as below:

exPowershellURI = "https://ps.outlook.com/powershell";
shellURI = "http://schemas.microsoft.com/powershell/Microsoft.Exchange";
psUserName, securePassword --> Exchange admin account having Recipient Management Role
AuthenticationMechanismToUse() returns Basic Authentication

 

This has been working fine for the past 1.5 years. However, just recently the line runspace.Open(); is throwing the below exception:

Connecting to remote server failed with the following error message : The server certificate on the destination computer (ps.outlook.com:443) has the following errors:       
Encountered an internal error in the SSL library. For more information, see the about_Remote_Troubleshooting Help topic.

 

This executable is configured to run with an Exchange admin account having Recipient Management Role.

On the same machine, if user tries to connect to Office365 using powershell commands, Powershell also throws the same error:

However, able to connect to O365 through powershell from any other machine.

Can someone highlight what can be the cause of this issue and its possible resolution?

 

Thanks & Regards,

Wasim Shaikh

Hi Wasim,

Did you find a solution to your powershell SSL library issue?

I am also experiencing this issue and currently looking for a solution.

Kind Regards,

Sulaimaan

Seems like Powershell connections from Windows Server 2003 are not supported for connecting to Exchange Online:

References:

http://community.office365.com/en-us/f/148/p/231854/722902.aspx#722902

http://technet.microsoft.com/en-in/library/jj984289(v=exchg.150).aspx

I had the same error from an application in a Windows Server 2003 SP2 environment and found that this hotfix corrected it:

https://support.microsoft.com/en-us/kb/938397