Applies to: ERD desktop client only |  Estimated time: 10–15 minutes


Issue Summary

Some users of the Enterprise Report Designer (ERD) client have seen a connection error when trying to reach the reporting service, similar to:

Could not establish secure channel for SSL/TLS with authority 'eda.ctuit.com:9001'

This is caused by the version of the Microsoft .NET Framework installed on your computer, not by an outage on the R365 side. Our servers are online and working correctly. The reporting service requires TLS 1.2, and older .NET Framework versions do not use TLS 1.2 by default. Installing .NET Framework 4.8 on the computer running ERD resolves the error.


Full step-by-step instructions are attached — download and follow the guide: [ERD Connection Fix – Instructions]

Who Should Follow These Steps

Apply this fix on any Windows computer where the ERD client is installed and showing the connection error above.


Before You Start

  • You will need administrator rights on the computerto install .NET Framework 4.8. If you're unsure, contact your internal IT support.
  • .NET Framework 4.8 is an in-place update to the .NET Framework 4.x line. It replaces earlier 4.x versions (4.0, 4.5, 4.6, 4.7) and remains fully compatible with ERD and with other applications already installed on the computer.
  • The installer may require a restart of the computer.
  • Close ERD completely before starting (check that it isn't running in the background).

Step-by-Step Instructions

Step 1 — Check Which .NET Framework Version Is Installed

Many newer Windows builds already include .NET Framework 4.8. To check before installing:

  • Click the Windows Start button and type PowerShell.
  • Right-click Windows PowerShell in the results and select Run as administrator.
  • If prompted by Windows to allow changes, select Yes.
  • Paste the command below and press Enter.
reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release

Compare the value returned against the list below:

  • 0x80EA8 (528040) or higher — .NET Framework 4.8 or newer is already installed. Skip to Step 3.
  • Lower than 0x80EA8, or the command returns an error — continue to Step 2.


Step 2 — Install .NET Framework 4.8

Download the .NET Framework 4.8 Runtime from Microsoft:

https://dotnet.microsoft.com/download/dotnet-framework/net48
  • Choose the Runtime download (the Developer Pack is not required).
  • Run the downloaded installer and follow the prompts.
  • Restart the computer if the installer asks you to.
Note: If your organization deploys software centrally, ask your internal IT team to push .NET Framework 4.8 rather than downloading it directly. The offline installer is also available from Microsoft for machines without internet access.


Step 3 — Restart ERD

  1. Make sure ERD is fully closed.
    To ensure that it is closed (check the Task Manager if unsure).
  2. Reopen the Enterprise Report Designer application.
  3. Try the action that previously failed (e.g., loading or saving a report).
Note: These settings only take effect after ERD is restarted. If you applied the fix while ERD was still open, close it fully and reopen it before testing.



If the Issue Continues

If you still see the same connection error after completing all steps and restarting ERD, contact support and let us know:

  • That you completed the steps in this document
  • The exact error message you see
  • The Release value returned by the command in Step 1
  • Your Windows version (Settings > System > About)

Why This Happens

Our reporting service requires a modern, secure connection method (TLS 1.2). The ERD client was built against .NET Framework 4.0, which predates TLS 1.2 being enabled by default. .NET Framework 4.8 is a backward-compatible, in-place update to the same 4.x line — ERD runs on it without any change to the application — and it negotiates TLS 1.2 automatically. Installing 4.8 therefore resolves the connection error without any manual registry changes.

For IT and security teams: Earlier versions of this document instructed users to install .NET Framework 4.0 and to set the SchUseStrongCrypto and SystemDefaultTlsVersions registry values manually. That guidance is superseded. .NET Framework 4.0 reached end of support in 2016 and should not be installed. .NET Framework 4.8 is the supported, currently serviced release, enables TLS 1.2 by default, and requires no registry modification. The R365 reporting servers themselves already run .NET Framework 4.8.