Information
- Products: Sparkrock 365
- Summary: The error message “The underlying connection was closed: An unexpected error occurred on a send.” appears while trying to run Jet Reports
Details
From the start of June 2020, Microsoft began implementing mandatory TLS 1.2 for all connections to BC SaaS web services. The error message indicates that Jet is incapable of establishing a connection through TLS 1.2.
Resolution
Please review these steps with your IT department. They might want to apply them to other Jet Report users.
There are two different root causes for this, you may have a version of Jet Reports older than 20.4.1 and you have to update to the latest version or TLS 1.2 may be disabled on the PC. So in order to resolve this, proceed to check your version in Help / About on the Jet Ribbon in Excel and if it is newer, please follow these instructions or ask your IT team to perform them on your machine:
- Press the Windows key + R, type "regedit", and press Enter to open the Registry Editor.
- Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\
- Create a new key called "TLS 1.2" under the "Protocols" key.
- Create two new keys called "Client" and "Server" under the "TLS 1.2" key.
- Under the "Client" and "Server" keys, create a new DWORD value called "Enabled" and set the value to "1".
- Restart your computer.
After completing the steps, try to run the reports again with Jet. If you keep facing issues, please create a case so we can help you further.
Impact / Risks
None, enabling TLS 1.2 is a security measure.
Workaround
Not applicable
Related Information
Not applicable
Update History
The following are the dates and actions pertinent to the history of this issue.
Date | Details | Link |
03/29/2023 | The first version of this Knowledge Base article was created. |
|
Attachment
Not applicable
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article