1. Close Sage Accounts, log off Windows, then log in as an administrator.
2. Press the Windows key + E then browse to C:\ProgramData\Sage
3. Right-click the folder SDK Licence, click Rename then rename the folder to SDK Licence OLD.
4. Browse to C:\ProgramData\Sage\Accounts\XXXX and delete the sage.usr file. Where XXXX is your software version, for example, 2024.
5. Open Sage Accounts then re-enter your licence information.
   
   

If the issue persists, you must exclude the following URL from your firewall and, if using a proxy connection, your proxy server:

https://licensing.services.sage.com/lic/services/LicenceService

For more information, refer to our guides on Proxy Servers and Firewall. For assistance with configuring the proxy server and firewall, refer to your local IT support.

NOTE: This can also be due to the user account on your computer not having sufficient permissions to write the AccountNumber to the registry. To check your permissions, refer to your local IT support.

If the issue persists, uninstall and reinstall Sage Accounts.

Check for outdated Cipher suits

From November 3rd outdated cipher suites that no longer meet security standards won’t be supported and will be blocked from contacting our license server. You can read more about this in the Cloudflare developer guidance document, it's the legacy cyphers that aren’t to be supported and will be blocked. 

These ciphers are typically used by Windows Server 2012 and Windows 8 (or earlier). If you’re using one of these operating systems it’s advisable to upgrade to a supported windows operating system, Check your system requirements.

If you’re already using a supported operating system, contact your IT regarding the cipher suites.