Skip to main content

​
Troubleshooting

​
Workflow Deployment Error

If there were any errors during the workflow deployment process, the Ingestion Pipeline Entity will still be created, but no workflow will be present in the Ingestion container.
  • You can then Edit the Ingestion Pipeline and Deploy it again.
  • From the Connection tab, you can also Edit the Service if needed.

​
Connector Debug Troubleshooting

This section provides instructions to help resolve common issues encountered during connector setup and metadata ingestion in OpenMetadata. Below are some of the most frequently observed troubleshooting scenarios.

​
How to Enable Debug Logging for Any Ingestion

To enable debug logging for any ingestion workflow in OpenMetadata:
  1. Navigate to Services Go to Settings > Services > Service Type (e.g., Database) in the OpenMetadata UI.
  2. Select a Service Choose the specific service for which you want to enable debug logging.
  3. Access Ingestion Tab Go to the Ingestion tab and click the three-dot menu on the right-hand side of the ingestion type, and select Edit.
  4. Enable Debug Logging In the configuration dialog, enable the Debug Log option and click Next.
  5. Schedule and Submit Configure the schedule if needed and click Submit to apply the changes.

​
Permission Issues

If you encounter permission-related errors during connector setup or metadata ingestion, ensure that all the prerequisites and access configurations specified for each connector are properly implemented. Refer to the connector-specific documentation to verify the required permissions.

​
Service Principal Authentication Failed

If you encounter authentication errors when connecting to Microsoft Fabric: 
Authentication failed: AADSTS7000215: Invalid client secret provided
This indicates that the client secret for the Azure Service Principal is either incorrect, expired, or not properly configured.

​
Resolution

  1. Verify the Client Secret: Log in to the Azure Portal and navigate to Azure Active Directory > App registrations.
  2. Select your application and go to Certificates & secrets.
  3. Check if the client secret has expired. If so, create a new client secret.
  4. Update the Microsoft Fabric connector configuration with the new client secret value.

​
Service Principal Not Added to Workspace

If you encounter errors related to missing permissions: 
Error: Access denied. The service principal does not have access to this workspace
This indicates that the Service Principal has not been added as a member of the Fabric Workspace.

​
Resolution

  1. Open Microsoft Fabric and navigate to the Workspace containing your Warehouses/Lakehouses.
  2. Click on Workspace settings (gear icon).
  3. Go to the Access tab and click Add people or groups.
  4. Search for your Service Principal by its Application (client) ID or name.
  5. Add it with at least Viewer role to enable metadata extraction.

​
ODBC Driver Not Found

If you encounter ODBC driver errors: 
pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open lib 'ODBC Driver 18 for SQL Server'")
This indicates that the required ODBC driver is not installed on the system running the ingestion.

​
Resolution

For Linux: 
curl https://packages.microsoft.com/keys/microsoft.asc | sudo apt-key add -
curl https://packages.microsoft.com/config/ubuntu/$(lsb_release -rs)/prod.list | sudo tee /etc/apt/sources.list.d/mssql-release.list
sudo apt-get update
sudo ACCEPT_EULA=Y apt-get install -y msodbcsql18
For macOS: 
brew tap microsoft/mssql-release https://github.com/Microsoft/homebrew-mssql-release
brew update
brew install msodbcsql18
For Windows: Download and install the ODBC Driver from Microsoft’s official page.

​
Connection Timeout Issues

If you encounter timeout errors when connecting to Microsoft Fabric: 
TimeoutError: Connection timeout after 30 seconds
This may occur if the SQL endpoint is not accessible or if there are network connectivity issues.

​
Resolution

  1. Verify the Host and Port: Ensure that the hostPort value is correct (e.g., your-workspace.datawarehouse.fabric.microsoft.com:1433).
  2. Check Network Access: Verify that the system running the ingestion can reach the Microsoft Fabric SQL endpoint.
  3. Firewall Rules: Ensure that port 1433 is open and not blocked by firewalls.
  4. Workspace Status: Verify that the Microsoft Fabric Workspace and Warehouse/Lakehouse are active and running.

​
Database Not Found

If the specified database cannot be found: 
Error: Database 'MyWarehouse' does not exist
This indicates that the database name specified in the configuration does not match any Warehouse or Lakehouse in your Microsoft Fabric workspace.

​
Resolution

  1. Log in to Microsoft Fabric and verify the exact name of your Warehouse or Lakehouse.
  2. Update the database field in the connector configuration with the correct name (case-sensitive).
  3. Alternatively, leave the database field empty to scan all databases, or set ingestAllDatabases: true to ingest from all Warehouses and Lakehouses.