NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

Active IQ Unified Manager Discussions

Upgraded WFA 4.0 to 4.2 receiving SOAP and REST SSL errors

ninja
6,838 Views

After upgrading WFA and migrating the database to a new server we aren't able to do rest or soap over powershell. Error is related to SSL.

 

 

 

Error received when attempting SOAP

 

New-WebServiceProxy : The request was aborted: Could not create SSL/TLS secure channel.

 

 

Error received when attempting REST

 

Exception calling "GetResponse" with "0" argument(s): "The request was aborted: Could not create SSL/TLS secure channel."

5 REPLIES 5

abhit
6,785 Views

Please contact customer support and submit a ticket.

 

Regards,

Abhi

ninja
6,775 Views

Had no idea NetApp supported WFA under the standard case creation process.

SHYAMVOLVO
6,695 Views

Hi @ninja  is the issue what you are facing solved ?

I am also having similar error when trying to connect to WFA 4.2   ....   with WFA 4.1  its works fine .. 

 

is it possible for your to post the code which you are using to connect to WFA using REST over powershell ?   . 

 

 

Thanks 

Shyam

ninja
6,692 Views

I don't have a fix yet. My NetApp case is still open. I will post the fix once I have it.

SHYAMVOLVO
6,634 Views

@ninja

 

you need to enable TLS 1.1 and TLS 1.2 on your windows server and also enable the same protocol on WFA .  I tried it and its works fine for me .

 

try downloading   "IISCrypto.exe "   from  https://www.nartac.com/Products/IISCrypto    ..  by this is pretty easy to enable it . 

 

then enable the same protocol in WFA  by 

 

clip_image001.png

 

 

 

Then restart your windows server .. 

 

use   below code in your script ensure that you are using TLS 1.2  . 

 

 

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

 

 

 

Thanks 

Shyam

Public