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 Pipeline 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 Data Pipelines.
  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 Member role to enable pipeline metadata extraction.

​
Fabric APIs Not Enabled

If you encounter errors about disabled APIs: 
Error: Service principals are not allowed to use Fabric APIs
This indicates that the “Service Principals can use Fabric APIs” setting is disabled in the Microsoft Fabric Admin Portal.

​
Resolution

  1. Log in to the Microsoft Fabric Admin Portal.
  2. Navigate to Tenant settings > Developer settings.
  3. Enable the setting “Service principals can use Fabric APIs”.
  4. Specify which security groups can use the API, or enable it for the entire organization.
  5. Wait a few minutes for the change to propagate.
More details can be found in the Microsoft Fabric documentation.

​
Invalid Workspace ID

If you encounter workspace-related errors: 
Error: Workspace 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' not found
This indicates that the workspace ID specified in the configuration is incorrect or the Service Principal does not have access to it.

​
Resolution

  1. Open Microsoft Fabric and navigate to your workspace.
  2. The workspace ID is found in the URL: https://app.fabric.microsoft.com/groups/<workspace-id>/...
  3. Copy the workspace ID from the URL and update the connector configuration.
  4. Ensure the Service Principal has been added as a member of this workspace.

​
Pipeline Run History Not Available

If pipeline metadata is ingested but run history is missing: 
Warning: No pipeline runs found for pipeline 'MyPipeline'
This may occur if pipelines have not been executed recently or if the Service Principal lacks permissions to view run history.

​
Resolution

  1. Verify that the pipeline has been executed at least once in Microsoft Fabric.
  2. Ensure the Service Principal has Member or Admin role in the workspace (not just Viewer).
  3. Check the pipeline filter pattern in the connector configuration to ensure the pipeline is not being excluded.
  4. Verify that the pipeline is not in a different workspace than the one specified in the configuration.

​
Connection Timeout Issues

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

​
Resolution

  1. Verify Network Access: Ensure that the system running the ingestion can reach the Microsoft Fabric API endpoints.
  2. Check Firewall Rules: Verify that outbound HTTPS (port 443) traffic to *.fabric.microsoft.com is allowed.
  3. Retry the Connection: Transient network issues may cause timeouts. Try running the ingestion again.
  4. Check Fabric Service Status: Visit the Microsoft 365 Service Health Dashboard to verify there are no ongoing outages.