There are two sides to Arden Licence Server logs that are available and should be reviewed when troubleshooting any licence server issues, such as licence revokes. These are, the Licence Server log, and the client-side logs, i.e. Impact or nServer.
Together, client and server logs can tell us whether, for example, server messages are reaching the client to keep alive the licence, but may be failing to be acknowledged via a transmission back to the server.
How to enable and locate each type of log is outlined below.
Licence Server Log
Licence Server itself has a log, which can be enabled within the Licence Server Administrator application that's included with a Licence Server installation. It offers both a simple and verbose logging mode.
- Enable Connection Logging - whether logging is enabled
- Log file - path for log file location
- Clear log file when service starts - automatically restart / clear the log file, which limiting file size growth
- Verbose log messages - higher-level logging of activity, suitable for troubleshooting
Notes:
- The default log file name and location is 'log.txt', and the file will naturally be created alongside the Licence Server program files, though both can be changed.
- The Licence Server Windows service should be restarted following such any such configuration changes to take effect.
Impact Workstation Log
The Impact workstation "client" log can be optionally enabled via the Impact Options > Workstation > Licensing tab. This dialog is reachable from the 'Connect' dialog, or, for an Impact client already connected to a database, via Options > Environment.
- Enable debug logging to 'licence.log' (restart required)
Notes:
- Once enabled, client-side logging will only begin following an Impact restart
- The log file name for an Impact client is 'licence.log'
- The default output location is 'AppData\Roaming\Arden Software Ltd\Impact\xx' (where 'xx' represents the major Impact version, e.g. Impact 2022 = 12, Impact 2023 = 13, Impact 2024 = 14 etc.)