Troubleshooting

This section describes a few potential problem scenarios and how to troubleshoot them.

I do not see any syslog messages

• Make sure the syslog server address includes the port number. If your syslog server is using address 10.0.1.14 and accepts UDP messages on port 514, then the syslog server address should look like this: udp://10.0.1.14:514.

• Make sure the license server was restarted after changing the syslog server address. Due to a limitation in v1.1.5, the syslog server address is only read and configured at server startup.

• Make sure your license server is configured to accept the license server as a syslog source.

A CodeMeter server connection not available

The web UI shows no licenses on the CodeMeter page.

The log file will have one or more entries like this one:

2022/06/10 09:53:37 http: proxy error: dial tcp 127.0.0.1:35797: connectex: No connection could be made because the target machine actively refused it.

This indicates that the CodeMeter server is not running. Check the running processes and make sure that the service is running.

The data folder specifies a path that does not exist or does not have write rights

The log file will show an entry like this one at startup:

2022/06/10 10:35:29 Error: Failed to load config.json from Q:\temp\config.json : mkdir Q:: The system cannot find the path specified.

Loading a file that's not a proper .key9 file

The Key9 page will show a message like this one:

The log file will contain this message:

2022/06/10 13:11:33 Error: Unable to load license file 'VXS-lic2.key9': bad file (2)

Loading a .key9 license file that has been prepared for another server ID

The key9 license files are keyed to your server ID, as shown at the top of the Key9 licenses page. The server ID appears as the suffix of the key9 license file name:

If loading a key9 license intended for another server, the following error message will be shown on the key9 licenses page: