- Introduction to SAP Connector
- SAP Input
- Checking the Data in the SAP Connector
- Adding Process Specific Tags to the SAP Connector for AppOne
- Adding Process Specific Due Dates to the SAP Connector for AppOne
- Adding Automation Estimates to the SAP Connector for AppOne
- Adding Attributes to the SAP Connector for AppOne
- Adding Activities to the SAP Connector for AppOne
- Adding Entities to the SAP Connector for AppOne
- Introduction to SQL Connectors
- Setting up a SQL Connector
- CData Sync Extractions
- Running a SQL Connector
- Editing Transformations
- Releasing a SQL Connector
- Scheduling Data Extraction
- Structure of Transformations
- Using SQL Connectors for Released Apps
- Generating a Cache With Scripts
- Setting up a Local Test Environment
- Separate Development and Production Environments
General Issues
JavaScript Error
Cause
JavaScript errors can show up in different ways. They can be a large error message with non-legible text, or scaling of elements happening weirdly. These errors are harmless, and there are no specific triggers for these errors.
Solution
There is no method which prevent this from happening. However, it is advised to press F5 to refresh the page.
Midair Collision
Cause
Multiple people are activating releases simultaneously. This may happen when many developers are working at the same time.
Solution
Wait a few seconds and try to activate the release again.
No Everything Is Visible in the Popup Menus
Cause
UiPath Process Mining is designed to be used with a resolution of 1920x1080 and for supported web browsers. If the user has a different resolution, a non-supported web browser, or when the user has zoomed in, it can result in the popup menus not being properly displayed.
Solution
Make sure that a supported web browser is used and that the user has not zoomed in. The resolution cannot always be changed but can be mentioned as one of the options.
Debug Panel Covers the Entire Screen
Cause
This is an error in JavaScript, which happens occasionally and does not affect anything else.
Solution
Press F5 to refresh the page to make sure that the debug panel is closed.
Message "Failed to Move Tempdir Into Final Location"
Cause
This error can be displayed for several reasons. UiPath Process Mining creates a temporary directory when uploading or exporting data. Once the uploading/exporting has finished, the
temporary directory is renamed. A virus scanner or other security program blocking the directory/files whilst scanning may cause the rename to fail. If the rename fails this error will be shown.
Solution
Add the UiPath Process Mining installation directory to the Exclusion list of you virus scanner and restart. Alternatively, disable the virus scanner to resolve this issue.
Match Level Count Differs
Cause
The number of levels in a lookup expression do not match between the aggregation tree and the matching attributes.
Solution
Make sure that you have the same number of levels in a lookup (up and until the expression level).
See also Lookup Expressions.
Foreign Key Constraint Failed
Cause
One or more foreign key constraints failed in the authentication database of the installation.
Solution
Contact UiPath Technical Support.
Assert Errors
Cause
There can be multiple causes for this, but in most cases you do not have impact on them.
Solution
Press F5 to refresh the page. If the issue persists please contact Contact UiPath Technical Support.
While Loading Large Amount of Data, All Sessions Are Killed
Cause
This error can occur for several reasons. Most likely within Internet Information Services (IIS) Manager a maximum is set on memory usage.
Solution
Follow these steps to adapt the settings for the application pool.
Step |
Action |
---|---|
1 |
Open Internet Information Services (IIS) Manager. |
2 |
In IIS Manager, click on Application Pools. and select the application pool for UiPath Process Mining. |
3 |
In the panel on the right, click on Recycling…. |
4 |
In the Memory Based Maximums panel deselect the Virtual memory usage and Private memory usage check boxes. |
5 |
Click on Next, and Finish. |
ODBC Connection String Does Not Use the User Passed in the Connection String.
Cause
This happens when setting up an ODBC connection where the database is set up to restrict access to Active Directory users
only. When using an ODBC connection string to set up the connection, the user
passed in the connection string is ignored and a local user of the current machine or the standard IIS user is used instead.
Solution
To fix this, you must force IIS to use the user that you originally intended and specified in the connection string.
Follow these steps to adapt the settings for the application pool.
Step |
Action |
---|---|
1 |
Open Internet Information Services (IIS) Manager. |
2 |
In IIS Manager, click on Application Pools and select the application pool for UiPath Process Mining. |
3 |
In the panel on the right, click on Advanced Settings…. |
4 |
Scroll down to locate the Identity entry and click on .... |
5 |
Enable the Custom account option and click on Set.... |
6 |
Enter the name and the password of the user you want to use for the ODBC connection string. |
7 |
Click on OK (3x). |
The Custom account forces IIS to use that user and makes sure that you can use the Active Directory account. UiPath Process Mining will now run under the user specified by the Custom account.
- If you plan to do a data run, you must make sure that the Scheduled Task is run with the Custom user as well.
- When the user changes the password, you must set the new password again in IIS application pool, otherwise the server will be down.
- The username and password do not need to be used in the connection string, usually you have to use the flag for trusted connection.
- You must update the access permissions of the UiPath Process Mining installation directory also for the Custom user.
- JavaScript Error
- Cause
- Solution
- Midair Collision
- Cause
- Solution
- No Everything Is Visible in the Popup Menus
- Cause
- Solution
- Debug Panel Covers the Entire Screen
- Cause
- Solution
- Message "Failed to Move Tempdir Into Final Location"
- Cause
- Solution
- Match Level Count Differs
- Cause
- Solution
- Foreign Key Constraint Failed
- Cause
- Solution
- Assert Errors
- Cause
- Solution
- While Loading Large Amount of Data, All Sessions Are Killed
- Cause
- Solution
- ODBC Connection String Does Not Use the User Passed in the Connection String.
- Cause
- Solution