How to fix "The request was aborted: Could not create SSL/TLS secure channel" while fetching data from oDATA feed

Hi @Ramesh Mandala and @Abhishek Kumar Singh

Thank you for your updates. Since I’m a moderator, I currently don’t have access to the specialized tools or environments needed to investigate your issue in more depth.

For that reason, I recommend posting a thread on GitHub. It’s an excellent platform for deeper technical discussions and for connecting with people who have hands-on experience and expertise. They’re in the best position to provide guidance and valuable insights on this topic.

Apologies for redirecting you to the related development team’s support. Moderators in this community have limited resources to check backend information, so contacting them will ensure you receive faster and more accurate assistance.

Hi @Michelle-N

to add to what Ramesh mentioned , yes we tried out the steps and it still dodint work.

we enabled ssl in postman also and the same set of certificates worked and we were able to invoke the odata apis .

also in the steps you meantioned , we tried all the steps except Enable TLS 1.2 via Registry - in this the registry keys/path was only not showing

Hi @Ramesh Mandala

Thank you for posting your question in the Microsoft Q&A forum.

Based on the information provided, I understand that you are encountering the error "The request was aborted: Could not create SSL/TLS secure channel" while trying to fetch an OData feed from a secure external REST endpoint using Excel 2016, despite having added the Server CA certificate to the Microsoft CA trust store.

According to my research, this error typically occurs due to issues with SSL/TLS protocol negotiation, certificate trust, or underlying system configurations in Excel 2016. Have you tried the above troubleshooting steps? If the issue persists, please consider the additional information below.

As a moderator, I do not have the specific tools to reproduce your exact environment. However, please try the following steps. Please restart Excel after making any changes and check the OData connection after each step.

-Check Certificate Installation Scope

Ensure that the server's Root CA certificate (and any intermediate certificates) is installed in the Trusted Root Certification Authorities store of the Local Computer account, not just the Current User account. Excel and Power Query often require system-level trust for these operations.

Check the endpoint URL using Internet Explorer (run as Administrator). Verify if the browser trusts the certificate without any warnings. Also, ensure that no Intermediate CA is missing from the certificate chain.

-Enable TLS 1.2 via Registry

Excel 2016 relies on the .NET Framework. You may need to force the use of strong cryptography to enable TLS 1.2. Open Registry Editor (regedit.exe) as an administrator and add/modify the following keys:

• For 64-bit and 32-bit processes:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319

"SchUseStrongCrypto"=dword:00000001

• For 32-bit processes on 64-bit systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319

"SchUseStrongCrypto"=dword:00000001

If you are using a 64-bit system, ensure both keys above are configured.

Important: Please make sure to back up your registry before making any changes to avoid issues.

Let me know if this helps!

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

To resolve the error "The request was aborted: Could not create SSL/TLS secure channel" while fetching data from an oData feed, consider the following suggestions:

1. Check TLS Configuration: Ensure that TLS 1.2 is enabled on the client and server. If TLS 1.2 is misconfigured or disabled, it can lead to this error. You may need to enable it in the registry or through your application settings.
2. Certificate Trust: Verify that the server's certificate is correctly installed in the trusted root Certification Authorities (CA) store. If the Microsoft CA certificate is missing or not trusted, it can cause SSL/TLS handshake failures.
3. Firewall and Proxy Settings: Ensure that any firewall or proxy settings are not blocking the SSL/TLS traffic. Misconfigured firewall or proxy settings can prevent the secure connection from being established.
4. Load Balancer Configuration: If a load balancer is involved, ensure that it is configured to load balance TCP/443 without breaking the SSL communications. This can help maintain a secure channel between the client and server.
5. Use Diagnostic Tools: Utilize tools like the SSL server test in the Microsoft Remote Connectivity Analyzer to diagnose and troubleshoot SSL/TLS issues.

By following these steps, you should be able to troubleshoot and resolve the SSL/TLS secure channel error when accessing the oData feed.

References:

• Resolve free/busy errors
• Could not create SSL/TLS secure channel error when running Hybrid Configuration wizard