Basic troubleshooting guide

Introduction

The purpose of this Troubleshooting page is to serve as a knowledge base for common problems faced or questions asked when using UiPath® Process Mining. It does not provide a complete list of all problems you may encounter, but is intended to provide guidance with the most common issues. If you encounter any issues that are not covered here, feel free to reach out to UiPath® Technical Support.

How to cancel a data run from the database

This section describes how to manually stop the data run from the database in case of a failing ingestion.

Follow these steps.

1. Retrieve the App ID of the process app for which you want to cancel the data run. See Process App properties.

2. Contact you database administrator to run the following SQL query in the AutomationSuite_ProcessMining_Metadata database:

   with Ingestion_tbl as (select top 1 * from dbo.Ingestions where AppId = '<app ID>' and [Status] = 1 order by LastUpdated desc) update Ingestion_tbl set [Status]=3 where <app ID> should be replaced with the App ID retrieved in Step 1.
   See the illustration below for an example.

   

3. Refresh Process Mining Portal page.

4. Upload data for the process app.

When creating a process app the status stays in Creating app

Possible cause

The database service is not set correctly during installation or upgrade.

Solution

Make sure to configure the process app security. See Configuring process app security.

Note:

If you cannot update the SQL server permission, it is recommended to change the app_security_mode from system_managed to single_account.

Message: [Errno 2] No such file or directory: '/dbt/dags/workflows/execdbt//target/4212eba4-1edc-4b9c-9c04-1d59c2bfe0af/run_results.json'

Possible cause

The content of the uploaded transformation package is incorrect, by an incorrect zip action.

Solution

Make sure the content of the .zip file that contains the transformations is correct.

Possible cause

Kerberos setup is used for login to Automation Suite and Kerberos setup is not used for SQL authentication. The enableSqlIntegratedAuth configuration flag determines whether or not integrated SQL authentication setup is used for SQL authentication. If the enableSqlIntegratedAuth configuration flag is set to true, this implies that Kerberos setup is not used for authentication. To solve the issue, the enableSqlIntegratedAuth configuration flag must set to false which disables integrated SQL authentication and ensures that Kerberos setup is used for authentication.

Possible solution

Follow these steps to set the enableSqlIntegratedAuth flag to false.

1. In the ArgoCD Experience, enter Airflow in the search bar and open the card.

2. Select App Details and go to the Details tab.

3. Edit the VALUES and set the flag enableSqlIntegratedAuth to false. Select SAVE.
   
4. Locate the SYNC POLICY section and set AUTOMATED to DISABLE AUTO-SYNC for the Airflow app, to ensure the configuration flag enableSqlIntegratedAuth will not be brought back to true.

   

Data transformations

Preview does not change after changing the query

It can occur that the Preview does not change after you changed the query and run the file.

Possible cause

The sql file is identical to the one in dbt, as it has not been updated since the last run. If you run the file again, no changes will be detected and therefore the Preview table won't be updated. For example, if you add a WHERE condition and run the file, the Preview will only show the filtered records. However, if you remove this WHERE condition and run the file again, the Preview will still only display the previously filtered records, when it should actually show all records.

Solution

Add, or change, a comment in the SQL file. This will force a dbt run and the Preview will be updated.

Message: The selection criterion does not match any nodes. Nothing to do.

The following warning messages are displayed in the ingestion log.

When you get the two warning messages The selection criterion "+<file>.state:modified+" does not match any nodes and Nothing to do. Try checking your model configs and model specifications args, it means that no changes were detected compared to the last time the queries were run. The Preview panels are showing the most up-to-date version of the data.

To force a complete re-run of your queries, select Apply to dashboards.

Uploading data

Message: utf-8 codec can't decode byte <byte> in position <position>: Invalid start byte

The following message is displayed in the ingestion log.

Possible cause

One or more input files you uploaded have an unexpected encoding.

Solution

Set the encoding to UTF-8 and set CR/LF end of line characters (Windows style).

You can change these settings in a file editor. For example in Notepad++.

1. Open the datasource file in Notepad++.

2. Go to Edit -> EOL Conversion and select Windows CR LF.

3. Go to Encoding and select Convert to UTF-8.

4. Save the file.

Message: File upload failed due to the following error: Network error

When uploading data using .csv or .tsv files, the following error message can occur:

Possible cause

Incorrect or missing HTTPS certificate.

Solution

The HTTPS certificate used by the BLOB store must be valid in your browser. Check the error and make sure to get the appropriate certificates.

1. Go the Process Mining portal and press F12 to open the Developer tools.

Check the Console and Network tabs for the ERR: CERT_AUTHORITY_INVALID error. This indicates an error with the trust of the HTTPS certificate. See the illustration below for an example.

2. Contact your IT department to install the certificate chain of the authority listed in the error and to add it to the trusted certificate store in operating system for all user that will be using the system. For example, pmcprddatawesa.blob.core.windows.net.

Message: The HTTP status code of the response was not expected (500)

When creating a new process app using sample data, the following error message can occur:

Possible cause

A SQL Server password has changed. See Configuring Microsoft SQL Server.

Solution

Update Automation Suite when changing SQL Server credentials.

CData Sync

Connection error: The TCP/IP connection to the host <host>, port <port> has failed.

The following message is displayed when setting up a SQL Server destination connection in CData Sync.

Possible cause

There is an issue with CData Sync connecting to SQL Server.

Solution

• Open SQL Server Configuration Manager.

• Check the TCP Port number.

• Check if TCP/IP is set to Enabled for the Port. See the illustration below for an example.