Installation troubleshooting

Use these solutions to resolve common problems that you might encounter after Task Mining Agent installation.

The Task Mining Agent log files are available in the following path:

C:\Users\<user_name>\AppData\Roaming\IBM Task Mining Agent\logs

You get one log file for one day. You can also right-click the Task Mining Agent tray icon in the taskbar and click Logs to open the Task Mining Agent logs folder.

The Task Mining Agent configuration file is available in the following path:

C:\Program Files\IBM Task Mining Agent\appsettings.json

Task Mining Agent cannot reach the endpoint

This issue occurs when you cannot log in to Task Mining Agent.

Symptom

When you log in to Task Mining Agent, you get an 404 Not Found error.

Workaround

Check the URL in your browser when you log in to Task Mining Agent. Ensure that it is not https://TM_HOST.

If you are using a Linux non-containerized environment, you must uninstall Task Mining Agent and then reinstall it by using the https://<PM_HOST>/taskmining/ endpoint.

If you are using a Red Hat® OpenShift® Container Platform environment, you must uninstall Task Mining Agent, and then reinstall it by using the https://cpd-mynamespace.<CLUSTER_DOMAIN>/processmining/ endpoint.

For more information, see Installing the Task Mining Agent.

Task Mining Agent page is moved or deleted

This issue occurs when the Task Mining page is moved or deleted.

Symptom

When you log in to Task Mining Agent, it results in the error message.

Workaround

Check the URL in your browser when you log in to Task Mining Agent. Ensure that it is not https://www.ibm.com or another generic URL.

If you are using a Linux non-containerized environment, you must uninstall Task Mining Agent and then reinstall it by using the https://_<PM_HOST>_/taskmining endpoint.

If you are using an Red Hat® OpenShift® Container Platform (OCP) environment, you must uninstall Task Mining Agent and then reinstall it by using the https://cpd-mynamespace._<CLUSTER_DOMAIN>_/processmining/ endpoint.

For more information, see Installing the Task Mining Agent.

Error caused by unreachable API services

This issue occurs when you try to start the Task Mining Agent, but it fails due to unreachable API services.

Symptom

When you try to start the Task Mining Agent, it fails with the following error message:

Unhandled response
[https://PM_HOST/taskmining/api/userinfo]: failure with status code:
NotFound

Workaround

To find the cause of the issue, you can check Apache Tomcat or NGINX logs.

To check whether the Apache Tomcat is not running or errors are present, do the following steps:

  1. Check if Apache Tomcat is running with ps -ef |grep tomcat.

  2. Check logs at <TM_HOME>/tomcat/logs/catalina.out.

To check whether NGINX is not correctly configured, check logs at /var/log/nginx/error.log or /var/log/nginx/access.log.

Error caused by untrusted or self-signed endpoints

This issue occurs when SSL connection could not be established.

Symptom

When you are using an endpoint with an untrusted or self-signed certificate, you see the following error.

Unhandled response
The SSL connection could not be established, see inner exception.

Workaround

By default, the allowUntrustedCertificate attribute in the Task Mining Agent configuration JSON file is set to false to deny access to untrusted and self-signed endpoints. To allow an untrusted endpoint, set allowUntrustedCertificate to true.

Login error caused by wrong JSON Web Token/JSON Web Encryption

This issue occurs when string that is processed contains characters that are not part of the valid hexadecimal character set.

Symptom

When you try to log in, you encounter the following error.

comexception decoding hex
string: invalid characters
encountered in Hex string

Workaround

Properties of JSON Web Token (JWT) and JSON Web Encryption (JWE) must be the same in IBM Process Mining and IBM Task Mining configuration files.

  • For IBM Process Mining, check the file <PM_HOME>/etc/processmining.conf at the key authentication.jwt and authentication.jwe.

  • For the IBM Task Mining, check the file <TM_HOME>/bin/environment.conf at the key jwt_secret and jwe_secret.

Invalid URL of Process Mining

This issue occurs when the URL of Process Mining is invalid and do not connect.

Symptom

The following log shows an information about the wrong URL that display a Generic error.

2020-12-04 13:41:52.828 ERROR 4087 --- [nio-8090-exec-3] com.invenio.task.j: Request: http://tm-test.my-domain.com/taskbuilder-2.1.0/api/projects raised not handled exception
org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://pm-test.my-domain.com/integration/tm/processes": pm-test.my-domain.com; nested exception is java.net.UnknownHostException: pm-test.my-domain.com

Workaround

Open the file <TM_HOME>/bin/environment.conf and set the value of processmining_host to the IBM Process Mining hostname.

Resource not found error

This issue is caused by the wrong permissions granted to the user.

Symptom

The following log shows an information about the wrong permissions that display the 404 Not Found error.

tail -300f /var/log/nginx/error.log

2020/12/04 14:05:51 [error] 16104#0: *42 open() "/opt/taskminer/tm/index.html" failed (13: Permission denied), client: XXX.XXX.XXX.XXX,

Workaround

Run the following command:

chcon -Rt httpd_sys_content_t /opt/taskminer/tm

Failed execution of preliminary operations required at first installation

This issue is caused by wrong or incomplete execution of preliminary operations required at first installation.

Symptom

The TM Data Processor is blocked and no evidence of errors are present in the log.

Workaround

Complete the preliminary operations explained in the TM Server Setup topic.