# 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](https://customerportal.uipath.com/support/add-case). ## Introduction 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](https://customerportal.uipath.com/support/add-case). ## How to cancel a data run from the database This section describes how to manually stop the data run from the database in case of a failing data run. Follow these steps. 1. Retrieve the App ID of the process app for which you want to cancel the data run. Check out[Process App properties](https://docs.uipath.com/process-mining/automation-suite/2.2510/user-guide/process-mining-portal#process-mining-portal). 2. 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 = '' 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. The following illustration shows an example. ![Example query to cancel a data run](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-example-query-to-cancel-a-data-run-328803-7726e02c-1c12330e.webp) 3. Refresh Process Mining Portal page. 4. Upload data for the process app. ## How to add an IP table rule to use SQL Server port 1433 Only the default SQL Server port **1433** can be used for the Airflow metadata SQL server database `AutomationSuite_ProcessMining_Metadata`. If your organization policies or firewall rules do not allow using port 1433, you can redirect incoming traffic directed at port 1433 of the SQL Server IP address to a new SQL Server IP and port. Use the following Linux command to add a `nat` rule in the IP tables PREROUTING chain: ``` iptables -t nat -A PREROUTING -d -dport 1433 -j DNAT --to-destination : ``` Replace `` and `` with your respective SQL Server IP address and port number. :::note This command should be run as a root user or a sudo user. ::: To make the connectivity available from node level as well, an additional rule in the output chain is required: ``` iptables -t nat -A OUTPUT -p tcp -d --dport 1433 -j DNAT --to-destination : ``` The `iptables` commands needs to be executed on all the nodes of the cluster. To make the IP table rules persistent, run the following command: ``` iptables-save > /etc/sysconfig/iptables systemctl enable iptables ``` ## When creating a process app the status stays in Creating app ### Possible cause The database service is not set correctly during installation or upgrade. ### Solution Make sure to configure the process app security. Check out [Configuring process app security](https://docs.uipath.com/automation-suite/automation-suite/2023.4/installation-guide/configuring-process-app-security-#%3Cstrong-class%3D%22ph-b%22%3Eenabling-system-managed-process-mining-data-warehouse-sql-server%3C%2Fstrong%3E). :::note If you cannot update the SQL server permission, it is recommended to change the `app_security_mode` from `system_managed` to `single_account`. :::