- Release notes
- Before you begin
- Getting started
- Integrations
- Managing access
- Working with process apps
- Creating apps
- Loading data
- Uploading data
- Retrieving the SQL Server database parameters
- Setting up a SQL Server account for data upload using an extractor
- Loading data using Theobald Xtract Universal
- Customizing process apps
- Data transformations
- TemplateOne app template
- Purchase to Pay app template
- Order to Cash app template
- Basic troubleshooting guide
- Process Mining troubleshooting and FAQs
Process Mining troubleshooting and FAQs
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.
When creating a new process app using sample data, the following error message can occur:
A SQL Server password has changed. See Configuring Microsoft SQL Server.
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.
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: [Errno 2] No such file or directory: '/dbt/dags/workflows/execdbt//target/4212eba4-1edc-4b9c-9c04-1d59c2bfe0af/run_results.json'
The content of the uploaded transformation package is incorrect, by an incorrect zip action.
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.
enableSqlIntegratedAuth
flag to false.
-
In the ArgoCD Experience, enter Airflow in the search bar and open the card.
-
Select App Details and go to the Details tab.
-
Edit the VALUES and set the flag
enableSqlIntegratedAuth
to false. Select SAVE. -
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.
This section describes how to manually stop the data run from the database in case of a failing ingestion.
Follow these steps.
-
Retrieve the App ID of the process app for which you want to cancel the data run. See Process App properties.
-
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. -
Refresh Process Mining Portal page.
-
Upload data for the process app.
Make sure to configure the process app security. See Configuring process app security.
app_security_mode
from system_managed
to single_account
.
- Introduction
- Message: The HTTP status code of the response was not expected (500)
- Possible cause
- Solution
- Message: File upload failed due to the following error: Network error
- Possible cause
- Solution
- Message: utf-8 codec can't decode byte <byte> in position <position>: Invalid start byte
- Possible cause
- Solution
- Connection error: The TCP/IP connection to the host <host>, port <port> has failed.
- Possible cause
- Solution
- Message: [Errno 2] No such file or directory: '/dbt/dags/workflows/execdbt//target/4212eba4-1edc-4b9c-9c04-1d59c2bfe0af/run_results.json'
- Possible cause
- Solution
- Possible cause
- Possible solution
- How to cancel a data run from the database
- When creating a process app the status stays in Creating app
- Possible cause
- Solution