Sage 300 is moving towards subscription licencing as the main model.
The licence refresh function then becomes crucial - it needs to operate at least once per year to keep Sage working.
Refresh requires access to the Sage licence servers, and we find this fails for some clients.
It can be very difficult to troubleshoot - we have had several clients with all firewalls off and full internet access still fail to connect. RVSpy etc doesnt help.
Request:
A Sage-centric log or trace on the licence 'Refresh' button detailing the calls made and responses received.
Idea logged : 30 August 2024
by: William W. | 9 months ago | Setup / Environment
Comments
A few notes fo those who come across this:
V 2020 PU 1 or 2 have an error in licencing that needs an updae to V 2020 PU 8.
This is re TLS
There is also a hotfix for 2018 re TLS
URL of the Sage licencing server: https://licensing.services.sage.com/ port number (443).
Whitelist the following urls:
licensing.services.sage.com:443
licensing2.services.sage.com:443
If you are really stuck you can look into using Fiddler web usage monitor
William, May 2025