Uploading data

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.

   

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.