Applies to: ERD desktop client only 

Issue

Some users of the Enterprise Report Designer (ERD) client see a connection error when opening or using the application:

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

This is caused by a Windows security setting on the local computer, not an outage on the R365 side. The fix below adjusts that setting so ERD can connect using the required security protocol (TLS 1.2).


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

Before You Start

  • You will need administrator rights on the computer. If you're unsure, contact your internal IT support.
  • Close ERD completely before starting (check that it isn't running in the background).
  • This change only affects settings on the local machine — no files are modified or removed.

Steps

Step 1 — Open PowerShell as Administrator

  1. Click the Windows Start button and type PowerShell.
  2. Right-click Windows PowerShell in the results and select Run as administrator.
  3. If prompted by Windows to allow changes, select Yes.

Step 2 — Run the Following Commands

Copy and paste each command below into the PowerShell window, pressing Enter after each one. Each should return: "The operation completed successfully."

reg add "HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319" /v SchUseStrongCrypto /t REG_DWORD /d 1 /f

reg add "HKLM\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319" /v SchUseStrongCrypto /t REG_DWORD /d 1 /f

reg add "HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319" /v SystemDefaultTlsVersions /t REG_DWORD /d 1 /f

reg add "HKLM\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319" /v SystemDefaultTlsVersions /t REG_DWORD /d 1 /f


Step 3 — Confirm the Settings Were Applied

Run these four commands to verify. Each should show a value of 0x1:

reg query "HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319" /v SchUseStrongCrypto

reg query "HKLM\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319" /v SchUseStrongCrypto

reg query "HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319" /v SystemDefaultTlsVersions

reg query "HKLM\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319" /v SystemDefaultTlsVersions


Step 4 — Restart ERD

  1. Make sure ERD is fully closed.
    To ensure that it is closed,  check the Task Manager.
  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.

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 provide:

  • Confirmation that you completed all steps in this article
  • The exact error message you see
  • Your Windows version (Settings > System > About)

Why This Happens

The R365 reporting service requires a modern, secure connection method (TLS 1.2). Some Windows computers don't automatically use this method for older applications unless a specific registry setting is enabled. The steps above enable that setting. No data or files on the computer are affected.