Maximum Call Stack Size exceeded on MS SQL

Questions
1

I’m using version 1.71.3 on self hosted windows server from npm.

When running a large query using MS SQL Node, I’m receiving the following error.

RangeError: Maximum call stack size exceeded at ExecuteContext.execute (C:\Users\me\AppData\Roaming\npm\node_modules\n8n\node_modules\n8n-nodes-base\nodes\Microsoft\Sql\MicrosoftSql.node.ts:272:17) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Workflow.runNode (C:\Users\me\AppData\Roaming\npm\node_modules\n8n\node_modules\n8n-workflow\src\Workflow.ts:1394:8) at C:\Users\me\AppData\Roaming\npm\node_modules\n8n\node_modules\n8n-core\src\WorkflowExecute.ts:1173:27 at C:\Users\me\AppData\Roaming\npm\node_modules\n8n\node_modules\n8n-core\src\WorkflowExecute.ts:1894:11

I’ve seen lots of posts about this, but it seems like it’s supposed to have been fixed already.

  • n8n version: 1.71.1
  • Database (default: SQLite): MS SQL Server
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): NPM
  • Operating system: Windows Server 2022
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

hi @darthg8r

Welcome to the community! this might be a memory issue, especially since it’s happening on a larger query. We have a guide that may be able to help: Memory-related errors | n8n Docs

Other than that, you might want to to allocate more memory/resources to that server.

Hope this helps!

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.