Error executing query on Azure Synapse via Node.js/NestJS application using Tedious

Question

Hello, Last week (around May 21, 2025), I started facing an issue when running queries on Azure Synapse through my Node.js application (using NestJS and the tedious library for SQL Server connections).

The application logs returned the following error:

Error while executing a query on Synapse: AggregateError 	

This issue occurred during data importation operations and caused failures in reading from Synapse. I would like to understand whether this was due to an instability in Azure Synapse at the time, or whether it could be a problem on my side (network, token expiration, etc.).

Has anyone else experienced similar issues recently?

Evidence:

Answer 1

Hi Luan Lopes

Thank you for sharing the detailed logs.

Based on the error trace - particularly AggregateError and issues during token handling (tedious/lib/token/handler.js) - the issue appears to be related to authentication, token parsing, or streaming failures while connecting to Synapse via the Tedious driver.

To help isolate the root cause, please consider the following checks:

1. Token Expiration or Misconfiguration:
   • If you're using Azure Active Directory (AAD) authentication, ensure the token is valid and not expired at the time of the request.
     • You might also want to enable verbose logging for the Tedious library to capture token details (excluding sensitive values).
     1. Network Instability or DNS Resolution:
        • Check if your Node.js app had transient connectivity issues (e.g., DNS failures, firewall rules, or timeouts) around the failure time (May 21, 2025, 12:39 PM).
        1. Synapse Backend Issues:
           • We are not aware of a platform-wide issue impacting Synapse around the given time, but you can confirm by reviewing the Azure Service Health for your region: https://portal.azure.com/#blade/Microsoft_Azure_Health/AzureHealthBrowseBlade/serviceIssues
           1. Tedious Compatibility:
              • Ensure you’re using a supported version of the Tedious driver compatible with Azure Synapse.
                • Consider retry logic for transient failures and handling ReadableStream errors, as seen in your stack trace.

Let us know:

• If the issue still persists or was only observed during that specific time window.
• Whether you're using SQL authentication or Azure AD (and how you're generating/accessing the token).

We’ll be glad to assist further with this information.