> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/connectors/troubleshooting-and-faqs/template-4.md).

# Template 4

{% tabs %}
{% tab title="Troubleshootings" %}

<table><thead><tr><th width="90.66668701171875">S. No.</th><th width="120.66668701171875">Error Message</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Connection Validation Failed</td><td><p><strong>Error Description</strong>: Connection validation fails due to incorrect credentials, invalid authentication details, inaccessible storage resources, or network connectivity issues.</p><p><strong>Resolution</strong>:</p><ul><li>Verify the connection string or Service Principal credentials.</li><li>Confirm the Storage Account and Fabric workspace are accessible.</li><li>Ensure outbound connectivity to Azure services.</li></ul></td></tr><tr><td>2</td><td>Authentication Failed / Invalid Client Secret</td><td><p><strong>Error Description</strong>: Authentication fails when the Client ID, Client Secret, or Tenant ID is incorrect, expired, or the Service Principal is unavailable.</p><p><strong>Resolution</strong>:</p><ul><li>Verify the Client ID, Client Secret, and Tenant ID.</li><li>Check whether the Client Secret has expired.</li><li>Ensure the Service Principal exists and is enabled.</li></ul></td></tr><tr><td>3</td><td>Authorization Failure (Access Denied)</td><td><p><strong>Error Description</strong>: The configured account does not have sufficient permissions to access Microsoft Fabric or Azure Storage resources.</p><p><strong>Resolution:</strong></p><ul><li>Assign the required Azure Storage roles.</li><li>Verify the Service Principal has access to the target Fabric workspace.</li><li>Confirm resource-level permissions are correctly configured.</li></ul></td></tr><tr><td>4</td><td>Resource Not Found</td><td><p><strong>Error Description</strong>: The specified storage account, container, folder, or file does not exist, or the configured path is incorrect.</p><p><strong>Resolution</strong>:</p><ul><li>Verify the resource exists in Azure Portal.</li><li>Validate the container and folder path.</li><li>Remove any incorrect or extra path separators.</li></ul></td></tr><tr><td>5</td><td>No Containers or Files Found</td><td><p><strong>Error Description</strong>: The storage account contains no accessible containers or the configured location is empty.</p><p><strong>Resolution</strong>:</p><ul><li>Verify that the storage account contains data.</li><li>Confirm permissions to list containers and files.</li><li>Validate the configured container and folder path.</li></ul></td></tr><tr><td>6</td><td>Operation Timed Out</td><td><p><strong>Error Description</strong>: Operations exceed the configured timeout because of large datasets, network latency, or temporary Azure service delays.</p><p><strong>Resolution:</strong></p><ul><li>Retry the operation after some time.</li><li>Limit operations to a specific folder when possible.</li><li>Verify network stability and timeout configuration.</li></ul></td></tr><tr><td>7</td><td>File Download Failed</td><td><p><strong>Error Description</strong>: File download fails because the file is unavailable, access is restricted, or the network connection is interrupted.</p><p><strong>Resolution</strong>:</p><ul><li>Verify the file exists.</li><li>Confirm read permissions for the file.</li><li>Check network connectivity before retrying.</li></ul></td></tr><tr><td>8</td><td>Unsupported or Invalid File Format</td><td><p><strong>Error Description</strong>: Metadata extraction fails because the file format, structure, or encoding is unsupported or invalid.</p><p><strong>Resolution:</strong></p><ul><li>Verify the file format is supported.</li><li>Ensure CSV files contain a header row and valid encoding.</li><li>Open the file to confirm it is not corrupted.</li></ul></td></tr><tr><td>9</td><td>Data Detection Failed</td><td><p><strong>Error Description</strong>: Column names or data types cannot be detected because of inconsistent data or insufficient sample records.</p><p><strong>Resolution</strong>:</p><ul><li>Ensure files contain sufficient sample data.</li><li>Maintain consistent values within each column.</li><li>Use supported date and data formats.</li></ul></td></tr><tr><td>10</td><td>Network or Proxy Error</td><td><p><strong>Error Description</strong>: Connector communication fails because Azure endpoints are unreachable or proxy configuration is incorrect.</p><p><strong>Resolution</strong>:</p><ul><li>Verify proxy configuration, if applicable.</li><li>Allow outbound HTTPS access to Azure endpoints.</li><li>Confirm DNS resolution and firewall settings.</li></ul></td></tr><tr><td>11</td><td>AADSTS Authentication Error</td><td><p><strong>Error Description</strong>: Microsoft Entra ID returns authentication errors because of invalid application configuration, tenant information, credentials, or permissions.</p><p><strong>Resolution</strong>:</p><ul><li>Verify the Client ID, Client Secret, Tenant ID, and endpoint configuration.</li><li>Confirm the Service Principal has the required API permissions and Azure roles.</li><li>Review the AADSTS error code returned by Microsoft Entra ID to identify the specific cause.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="FAQs" %}

<table data-search="true"><thead><tr><th width="88.3333740234375" align="center">Sl. No</th><th width="140">Question</th><th>Answer</th></tr></thead><tbody><tr><td align="center">1</td><td><strong>Why does connection validation fail?</strong></td><td>Connection validation fails when authentication details are invalid, the Storage Account is inaccessible, required permissions are missing, or Azure resources cannot be reached. Verify the configured credentials, Storage Account, and network connectivity.</td></tr><tr><td align="center">2</td><td><strong>Why are folders or files not displayed?</strong></td><td>Folders or files may not appear if the configured path is incorrect, the location is empty, or the account does not have permission to access the resources. Verify the path, resource availability, and assigned permissions.</td></tr><tr><td align="center">3</td><td><strong>Why are file operations slow?</strong></td><td>Operations may take longer when processing large numbers of files, accessing large datasets, or experiencing network latency. Limiting operations to a specific folder and ensuring a stable network connection can improve performance.</td></tr><tr><td align="center">4</td><td><strong>Which Azure roles are required?</strong></td><td>Assign <strong>Storage Blob Data Reader</strong> for read operations. Assign <strong>Storage Blob Data Contributor</strong> when write operations are required. Grant the appropriate <strong>Microsoft Fabric workspace role</strong> (<strong>Member</strong> or <strong>Contributor</strong>) to the Microsoft Entra ID application.</td></tr><tr><td align="center">5</td><td><strong>Why does Service Principal authentication fail?</strong></td><td>Service Principal authentication fails when the <strong>Client ID</strong>, <strong>Client Secret</strong>, or <strong>Tenant ID</strong> is incorrect, expired, or the Service Principal lacks the required Azure permissions. Verify the authentication details and assigned roles.</td></tr><tr><td align="center">6</td><td><strong>How can AADSTS authentication errors be resolved?</strong></td><td>AADSTS errors indicate issues with Microsoft Entra ID authentication, such as invalid credentials, tenant configuration, or missing permissions. Review the returned <strong>AADSTS</strong> error code and verify the Microsoft Entra ID application configuration.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

***

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/connectors/troubleshooting-and-faqs/template-4.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.