What to do when the Airflow scheduler fails due to an invalid IPV6 error and Processing Mining is in a degraded state after installation?
Issue Description:
When Process Mining is installed on a nonstandard port, the SQL validation checks during install will pass; however, table creation will not complete and the database is rendered inaccessible by the application.
Resolution:
If the SQL port is running on a nonstandard port (anything other than 1433), follow the below steps:
- Uninstall Process Mining, update the cluster_config.json by setting the 'processmining.enabled' parameter to false. Afterward, execute the installer again with the -s parameter.
- Change the listening port on the SQL Server to 1433
- Update the relevant SQL Connection strings for Process Mining within the cluster_config.json
- Recreate the databases using the provided scripts below.
Dropping Existing Databases:
USE master; DROP TABLE IF EXISTS AutomationSuite_Airflow; DROP TABLE IF EXISTS AutomationSuite_ProcessMining_Metadata; DROP TABLE IF EXISTS AutomationSuite_ProcessMining_Warehouse; GO;
Recreating the Databases:
-- Create AutomationSuite_Airflow database with READ_COMMITTED_SNAPSHOT option CREATE DATABASE AutomationSuite_Airflow; GO ALTER DATABASE AutomationSuite_Airflow SET READ_COMMITTED_SNAPSHOT ON; GO -- Create AutomationSuite_ProcessMining_Metadata database CREATE DATABASE AutomationSuite_ProcessMining_Metadata; GO -- Create AutomationSuite_ProcessMining_Warehouse database CREATE DATABASE AutomationSuite_ProcessMining_Warehouse; GO -- Set READ_COMMITTED_SNAPSHOT option for AutomationSuite_ProcessMining_Metadata ALTER DATABASE AutomationSuite_ProcessMining_Metadata SET READ_COMMITTED_SNAPSHOT ON; GO
- Uninstall Process Mining, update the cluster_config.json by setting the 'processmining.enabled' parameter to true. Afterward, execute the installer again with the -s parameter.