- Release notes
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Root cause analysis
- Simulating automation potential
- Starting a Task Mining project from Process Mining
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Customizing process apps
- App templates
- Additional resources
Basic troubleshooting guide
The purpose of this Troubleshooting page is to serve as a knowledge base for common problems faced or questions asked when using 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.
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.
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.
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.
You may encounter errors while loading data using CData Sync. For example, when some of the tables have loaded successfully, but for the remaining tables an error message occurs indicating that the database or disk is full.
Possible cause
When CData loads data from your source system to Azure Blob, CData Sync temporarily stores the .csv for the task on the local disk on the server where CData is installed. This error might show up when there is is an issue with the local disk.
The location where the temporary .csv file is stored is located on C:\ drive. There is no option in CData Sync to configure or modify the storage location.
Possible solution
-
Check if the disk where CData Sync is installed has enough free space.
-
If the disk is (almost) full, check if the folder C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\cdata contains temporary folders with data.
Note:The location might be different for older versions of CData Sync.
-
In case you see temporary folders, you can delete those manually to free up disk space. In you CData Sync connections, you can add the following to your connection under Miscellaneous > Other
schemacacheduration=-1
.
Possible solution
In case the steps above do not provide a solution to the problem, you could create a symbolic link from the CData Sync temporary directory to another disk with sufficient free disk space.
-
Open a command prompt on the server where CData Sync is installed.
-
Create the symbolic link using the following command:
mklink /J "C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\cdata" "D:\cdata_tmp"
mklink /J "C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\cdata" "D:\cdata_tmp"
Replace the drive letter, in this example D, with a drive that has sufficient disk space.
- Introduction
- Uploading data
- Message: utf-8 codec can't decode byte <byte> in position <position>: Invalid start byte
- Message: File upload failed due to the following error: Network error
- CData Sync
- Connection error: The TCP/IP connection to the host <host>, port <port> has failed.
- Error: Database or disk is full