For the complete documentation index, see llms.txt. This page is also available as Markdown.

Template 1

Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.

General

S. No.
Error Message
Error Description & Resolution

1

Connection Validation Failed

Error Description: Connection validation fails due to incorrect credentials, invalid authentication details, inaccessible storage resources, or network connectivity issues.

Resolution:

  • Verify the connection string or Service Principal credentials.

  • Confirm the Storage Account and Fabric workspace are accessible.

  • Ensure outbound connectivity to Azure services.

2

Authentication Failed / Invalid Client Secret

Error Description: Authentication fails when the Client ID, Client Secret, or Tenant ID is incorrect, expired, or the Service Principal is unavailable.

Resolution:

  • Verify the Client ID, Client Secret, and Tenant ID.

  • Check whether the Client Secret has expired.

  • Ensure the Service Principal exists and is enabled.

3

Authorization Failure (Access Denied)

Error Description: The configured account does not have sufficient permissions to access Microsoft Fabric or Azure Storage resources.

Resolution:

  • Assign the required Azure Storage roles.

  • Verify the Service Principal has access to the target Fabric workspace.

  • Confirm resource-level permissions are correctly configured.

4

Resource Not Found

Error Description: The specified storage account, container, folder, or file does not exist, or the configured path is incorrect.

Resolution:

  • Verify the resource exists in Azure Portal.

  • Validate the container and folder path.

  • Remove any incorrect or extra path separators.

5

No Containers or Files Found

Error Description: The storage account contains no accessible containers or the configured location is empty.

Resolution:

  • Verify that the storage account contains data.

  • Confirm permissions to list containers and files.

  • Validate the configured container and folder path.

6

Operation Timed Out

Error Description: Operations exceed the configured timeout because of large datasets, network latency, or temporary Azure service delays.

Resolution:

  • Retry the operation after some time.

  • Limit operations to a specific folder when possible.

  • Verify network stability and timeout configuration.

7

File Download Failed

Error Description: File download fails because the file is unavailable, access is restricted, or the network connection is interrupted.

Resolution:

  • Verify the file exists.

  • Confirm read permissions for the file.

  • Check network connectivity before retrying.

8

Unsupported or Invalid File Format

Error Description: Metadata extraction fails because the file format, structure, or encoding is unsupported or invalid.

Resolution:

  • Verify the file format is supported.

  • Ensure CSV files contain a header row and valid encoding.

  • Open the file to confirm it is not corrupted.

9

Data Detection Failed

Error Description: Column names or data types cannot be detected because of inconsistent data or insufficient sample records.

Resolution:

  • Ensure files contain sufficient sample data.

  • Maintain consistent values within each column.

  • Use supported date and data formats.

10

Network or Proxy Error

Error Description: Connector communication fails because Azure endpoints are unreachable or proxy configuration is incorrect.

Resolution:

  • Verify proxy configuration, if applicable.

  • Allow outbound HTTPS access to Azure endpoints.

  • Confirm DNS resolution and firewall settings.

11

AADSTS Authentication Error

Error Description: Microsoft Entra ID returns authentication errors because of invalid application configuration, tenant information, credentials, or permissions.

Resolution:

  • Verify the Client ID, Client Secret, Tenant ID, and endpoint configuration.

  • Confirm the Service Principal has the required API permissions and Azure roles.

  • Review the AADSTS error code returned by Microsoft Entra ID to identify the specific cause.

Authentication

S. No.
Error Message
Error Description & Resolution

1

Authentication Failed

Error Description: Authentication fails because the configured username, password, token, API key, Client Secret, or other authentication credentials are invalid or expired.

Resolution:

  • Verify the configured authentication credentials.

  • Renew expired passwords, tokens, or secrets.

  • Ensure the selected authentication method is supported.

2

Authorization Failed / Insufficient Privileges

Error Description: Authentication succeeds, but the configured account does not have sufficient permissions to access the requested resources.

Resolution:

  • Verify the assigned permissions.

  • Ensure the account has the required read or administrative privileges.

  • Contact the source system administrator if additional permissions are required.

3

Access Token Expired

Error Description: OAuth access tokens, service principal credentials, or temporary security credentials have expired.

Resolution:

  • Generate a new access token or secret.

  • Update the connector configuration.

  • Validate the authentication configuration before saving.

4

Credential Manager Authentication Failed

Error Description: The connector cannot retrieve credentials from the configured Credential Manager.

Resolution:

  • Verify the Credential Manager configuration.

  • Confirm the stored secrets exist and are accessible.

  • Ensure the connector has permission to retrieve the secret.

5

Permission Denied

Error Description: The configured account does not have permission to perform the requested operation, such as crawling, profiling, previewing data, or executing queries.

Resolution:

  • Verify the required permissions for the selected operation.

  • Grant additional privileges if necessary.

  • Retry the operation after permissions are updated.

Connectivity

S. No.
Error Message
Error Description & Resolution

1

Connection Validation Failed

Error Description: The connector cannot establish communication with the source system because of incorrect connection details, unreachable endpoints, or network restrictions.

Resolution:

  • Verify the server name, hostname, port number, and endpoint.

  • Confirm the source system is reachable.

  • Retry the connection validation.

2

Connection Timed Out

Error Description: The connection request exceeds the configured timeout because of network latency, firewall restrictions, or server response delays.

Resolution:

  • Verify network connectivity.

  • Confirm firewall rules allow communication.

  • Increase timeout settings if appropriate.

3

Bridge Communication Failed

Error Description: The Bridge cannot communicate with the source system because the Bridge service is unavailable, unreachable, or incorrectly configured.

Resolution:

  • Verify the Bridge service is running.

  • Confirm Bridge connectivity to the source system.

  • Review Bridge logs for additional information.

4

SSL / Certificate Validation Failed

Error Description: Secure communication cannot be established because the server certificate is invalid, expired, self-signed, or untrusted.

Resolution:

  • Verify the server certificate.

  • Import the certificate into the trusted certificate store if required.

  • Confirm the certificate matches the server hostname.

5

Network or Proxy Error

Error Description: Communication fails because of incorrect proxy configuration, DNS resolution issues, or firewall restrictions.

Resolution:

  • Verify proxy settings.

  • Confirm DNS resolution.

  • Allow outbound communication to the required endpoints.

Crawling

S. No.
Error Message
Error Description & Resolution

1

Crawl Completed but No Objects Found

Error Description: The crawl completes successfully, but no supported objects are discovered because the configured scope is empty, filters exclude all objects, or permissions are insufficient.

Resolution:

  • Verify the crawl scope.

  • Review include and exclude filters.

  • Confirm permissions to access metadata.

2

Partial Crawl Completed

Error Description: Some supported objects are successfully crawled, while others are skipped because of permissions, unsupported object types, or temporary errors.

Resolution:

  • Review crawl logs.

  • Verify permissions for skipped objects.

  • Retry the crawl after resolving the reported issues.

3

Profiling Failed

Error Description: Profiling cannot complete because of unsupported data types, insufficient permissions, large datasets, or resource limitations.

Resolution:

  • Verify profiling permissions.

  • Reduce the profiling scope if necessary.

  • Confirm the selected objects support profiling.

4

Metadata Not Updated

Error Description: Metadata changes are not reflected because the crawl has not completed successfully or change tracking is disabled.

Resolution:

  • Verify crawl completion.

  • Confirm metadata archiving or change tracking settings.

  • Execute a new crawl.

5

Data Preview Failed

Error Description: Data Preview cannot retrieve sample data because of unsupported objects, insufficient permissions, or query execution failures.

Resolution:

  • Verify read permissions.

  • Confirm the selected object supports preview.

  • Retry the operation.

FAQs

General

Why should a dedicated Service Account be used?

A dedicated Service Account simplifies permission management, provides consistent authentication, reduces operational interruptions caused by user account changes, and improves security for production environments.

What connector features are supported?

The Microsoft Fabric OneLake connector supports metadata crawling, sample profiling, data preview, manual lineage, Data Quality, Bridge connectivity, and secure authentication through supported Credential Managers.

Authentication

Why does connection validation fail?

Connection validation fails when the Tenant ID, Client ID, Client Secret, or OneLake endpoint is incorrect, the Service Principal cannot authenticate, required permissions are missing, Microsoft Fabric workspaces are inaccessible, or the application cannot reach Microsoft Entra ID or OneLake services. Verify the authentication details, assigned permissions, and network connectivity.

How can AADSTS authentication errors be resolved?

AADSTS errors indicate Microsoft Entra ID authentication problems such as invalid credentials, expired Client Secrets, incorrect Tenant IDs, application configuration issues, or missing permissions. Review the returned AADSTS error code, verify the Microsoft Entra application configuration, and update the connection details if required.

Why does Service Principal authentication fail?

Service Principal authentication fails when the Tenant ID, Client ID, or Client Secret is incorrect or expired, the Microsoft Entra application is improperly configured, or the Service Principal does not have the required permissions. Verify the authentication details, regenerate the Client Secret if necessary, and ensure the Service Principal is active.

Connectivity

Why does connection validation succeed but file access fail?

Connection validation only verifies authentication and workspace accessibility. File operations require additional read permissions on Microsoft Fabric OneLake resources. Verify that the Service Principal has the required Azure Storage and Microsoft Fabric workspace permissions to access the target files.

Why does View Data work without Bridge but fail when using Bridge?

View Data operations executed through Bridge may fail when the required Bridge configuration or system properties are unavailable. Verify that the Bridge deployment is up to date, the required system properties are configured, and the Bridge can access Microsoft Fabric OneLake successfully.

Permissions

Why are workspaces, folders, or files not displayed?

Workspaces, folders, or files may not appear when the Service Principal does not have permission to list Microsoft Fabric workspaces, the configured path is incorrect, the selected location is empty, or the resource is unavailable. Verify the workspace path, lakehouse location, and assigned permissions.

Which permissions are required?

Assign the Storage Blob Data Reader role for read operations such as browsing, previewing, downloading, and profiling files. Assign Storage Blob Data Contributor only when write operations are required. The Service Principal must also have an appropriate Microsoft Fabric workspace role to access workspace content.

Why are file operations slow?

File browsing, preview, download, or profiling may take longer when processing large lakehouses, numerous files, large Parquet datasets, or when network latency is high. Limiting operations to a specific folder or smaller dataset and ensuring stable network connectivity can improve performance.


Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.

Last updated

Was this helpful?