- Release notes
- Before you begin
- 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
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Customizing process apps
- App templates
- Additional resources
- Out-of-the-box Tags and Due dates
- Editing data transformations in a local environment
- Setting up a local test environment
- Designing an event log
- Extending the SAP Ariba extraction tool
- Performance characteristics
- Data transformations
- Uploading data
- CData Sync
Uploading data
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.
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.
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.
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.
- 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
- Message: utf-8 codec can't decode byte <byte> in position <position>: Invalid start byte
- Possible cause
- Solution
- Message: File upload failed due to the following error: Network error
- Possible cause
- Solution
- Message: The HTTP status code of the response was not expected (500)
- Possible cause
- Solution