Serverless SQl pool has encountered an internal error

Question

Hi all,

I am getting this error while trying to run a simple query on an csv file connected to azure synapse studio via linked service; Serverless SQl pool has encountered an internal error

Below is the error message from synapse studio. I did google search and did play around with firewalls and network settings as per instructions from google and some previous posts in the community. I am not expert in networking or firewalls.

But this error is not going away and because of this error I am not able to work on anything on serverless sql pool. I am at my wits end on this . Need some help from azure community here. I am not able to to raise support tickets as I am on free trial version.

Please help me with this .

Regards

Tarun

Answer 1

Hi Tarunoday Sharma,

Thanks for reaching out to Microsoft Q&A.

Did you check the below and all looks good?

1. Check Storage Account Permissions

Ensure that the Synapse SQL pool has the required permissions on the ADLS container where your CSV file is stored.

• Go to your ADLS account.
• Verify that the Managed Identity for Synapse Analytics has the "Storage Blob Data Reader" role assigned on the appropriate storage account or container level.

2. Validate Firewall Settings

You mentioned you already tried some network-related configurations. However, double-check that:

• Your storage account allows connections from the Synapse workspace.
• The firewall settings of the storage account permit access from the Synapse service. You can set this in the Networking tab of the storage account by either allowing access from all networks or specifying the Synapse service in the trusted services.

3. Check CSV Format and File Accessibility

• Double-check the CSV file's accessibility. You can try accessing the CSV via other means (e.g., directly from the Azure Storage Explorer or a local tool) to ensure the file is not corrupted or inaccessible.
• Confirm that the CSV is well-formatted and does not contain unusual characters or encodings that might cause the serverless SQL pool to fail during parsing.

Please 'Upvote'(Thumbs-up) and 'Accept' as an answer if the reply was helpful. This will benefit other community members who face the same issue.