Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Microsoft SQL Node throws Invalid URL Error

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Describe the problem/error/question

Connection worked in Version 2.13.4 but now MS SQL connection does not work and gives a Invalid URL error

What is the error message (if any)?

  • error: all

Code Example

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

Connection worked in Version 2.13.4 but now MS SQL connection does not work and gives a Invalid URL error

What is the error message (if any)?

TypeError: Invalid URL at new URL (node:internal/url:819:25) at appendResumeToken (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/get-additional-keys.ts:14:17) at getAdditionalKeys (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/get-additional-keys.ts:30:15) at ExecuteContext.get additionalKeys (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/node-execution-context/node-execution-context.ts:435:27) at ExecuteContext.Memoized.descriptor.get (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@n8n+decorators@file+packages+@n8n+decorators/node_modules/@n8n/decorators/src/memoized.ts:29:32) at ExecuteContext.getNodeParameter (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/node-execution-context/node-execution-context.ts:473:11) at ExecuteContext.getNodeParameter (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/node-execution-context/execute-context.ts:136:9) at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/Microsoft/Sql/MicrosoftSql.node.ts:293:26) at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1045:8) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1224:11) at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1672:27 at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2324:11

Please share your workflow/screenshots/recording

<img width="640" height="590" alt="Image" src="https://github.com/user-attachments/assets/f3dd5a0a-9f14-4257-8cfe-324434a85699" /> 
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

{ "nodes": [ { "parameters": { "operation": "executeQuery", "query": "EXECUTE [alert].[xxxxxxxxx] ", "options": {} }, "type": "n8n-nodes-base.microsoftSql", "typeVersion": 1.1, "position": [ 240, 192 ], "id": "7d16bcfc-9012-4dda-9149-783b7cf69334", "name": "Microsoft SQL", "credentials": { "microsoftSql": { "id": "xxxxxxxxxxx", "name": "Microsoft SQL account" } } } ], "connections": { "Microsoft SQL": { "main": [ [] ] } }, "pinData": {}, "meta": { "templateCredsSetupCompleted": true, "instanceId": "11a69c9b09082e05f4cda9827fdf2e95df27a283bf7bf4b9f7c53cc6ba8fd880" } }

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

  • n8nVersion: 2.16.1
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: open source

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10.15; rv:149.0) gecko/20100101 firefox/149.0
  • isTouchDevice: false

Generated at: 2026-04-20T14:28:39.782Z

extent analysis

TL;DR

The MS SQL connection issue can be resolved by verifying the connection URL and updating it if necessary, as the error message indicates an invalid URL.

Guidance

  1. Verify the connection URL: Check the Microsoft SQL node's connection settings to ensure the URL is correctly formatted and points to the correct database instance.
  2. Check for URL changes: If the database instance or connection details have changed, update the URL accordingly to reflect these changes.
  3. Review node configuration: Ensure that the Microsoft SQL node is configured correctly, including the operation, query, and options, as any misconfiguration could lead to connection issues.
  4. Test the connection: After making any changes, test the connection to verify that it is working as expected.

Example

No code snippet is provided as the issue seems to be related to configuration rather than code.

Notes

The exact cause of the issue is not explicitly stated, but the error message suggests a problem with the URL. It's possible that changes in the database or network configuration could be contributing to the issue.

Recommendation

Apply workaround: Verify and update the connection URL as needed, and test the connection to ensure it is working correctly. This approach is recommended because the error message specifically mentions an invalid URL, suggesting that this is the most likely cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#LLM response#prompt template#agent execution#callback error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING