TLM: Error: E1067: The process terminated unexpectedly

25-Nov-2024

Possible causes and solutions


Port already in use by another application

If you use a local license server, it listens on port 9090 by default. If this port is already in use by another application, the TASKING License Service under Windows cannot start and Windows will display the following error message:

Windows could not start the TASKING License Service service on <name of the TLM license server PC>
E 1067: The process terminated unexpectedly

whereas the Windows event log may show:

Listen error (The system cannot find the file specified. )

To fix this, you can specify a different port number for your local license server in the options file licdopt.txt:

LICD_LISTEN_PORT = 9191


Changed security ID

Another cause of the E1067 error is a changed security ID. The security ID is used to identify the TLM license server. If the hardware configuration of the license server PC changed, the security ID might have changed as well. As a result, the TLM license server service may fail to start.

To determine if a changed security ID is causing the problem, you can review the content of the log file. It will include an error message like:

<date> <time> LicD license key for ID <security ID used in the license key> does not match with system ID <current security ID of the PC>

If your TLM local license server has not created a log file yet, you can add the following entry to the licdopt.txt file:

LICD_LOGFILE=C:\Tasking\logs\logfile.txt

Please note that the directory where the TLM log files have to be saved must already exist on the TLM server PC. If it does not exist, you will need to create it manually.

If your security ID has changed, please contact us and share the old and current security IDs, along with any relevant information regarding changes to the TLM local license server configuration that could have led to the changed security ID.


More resources

Was this answer helpful?