A new created Excel365 node cannot identify sheets, while the existing ones work perfectly fine

Questions
1

Describe the problem/error/question

When I use a new Office365 node, the workbook search does not work. No results show up. The strange thing is that existing Office365 nodes work fine with the current names. So it seems that it has to do with the new update.

Also ‘workbook’ ‘by id’ isn’t working any longer.

What is the error message (if any)?

When I lookup an existing office365 node that works and change from ‘by name’ to ‘by id’, the ID has this format: 545D590F18E68994!30556 and is not accepted. You get a warning sign that says: ‘issues: not a valid workbook id’. And it breaks.

Please share your workflow

THIS IS THE EXISTING WORKING ONE

this is the not working new node (but it is just blank)

Information on your n8n setup

# Debug info

## core
- n8nVersion: 1.68.0
- platform: docker (self-hosted)
- nodeJsVersion: 20.18.0
- database: sqlite
- executionMode: regular
- concurrency: -1
- license: community

- it is running on a docker on ubuntu at a droplet of digital ocean 

## storage
- success: all
- error: all
- progress: false
- manual: true
- binaryMode: memory

## pruning
- enabled: true
- maxAge: 336 hours
- maxCount: 10000 executions

## client
- userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/131.0.0.0 safari/537.36
- isTouchDevice: false
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

When I do ‘workbook’ → ‘get many’, I get this error:

{
  "errorMessage": "The service was not able to process your request",
  "errorDescription": "Error Calling Substrate Search",
  "errorDetails": {
    "rawErrorMessage": [
      "500 - {\"error\":{\"code\":\"generalException\",\"message\":\"Error Calling Substrate Search\",\"innerError\":{\"date\":\"2024-11-25T09:52:32\",\"request-id\":\"a81c559e-aa89-4947-aee1-758c196430d2\",\"client-request-id\":\"a81c559e-aa89-4947-aee1-758c196430d2\"}}}"
    ],
    "httpCode": "500"
  },
  "n8nDetails": {
    "nodeName": "Microsoft Excel 365",
    "nodeType": "n8n-nodes-base.microsoftExcel",
    "nodeVersion": 2.1,
    "resource": "workbook",
    "operation": "getAll",
    "time": "25-11-2024, 10:52:32",
    "n8nVersion": "1.68.0 (Self Hosted)",
    "binaryDataMode": "default",
    "stackTrace": [
      "NodeApiError: The service was not able to process your request",
      "    at Object.microsoftApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Microsoft/Excel/v2/transport/index.js:25:15)",
      "    at processTicksAndRejections (node:internal/process/task_queues:95:5)",
      "    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Microsoft/Excel/v2/actions/workbook/getAll.operation.js:71:32)",
      "    at Object.router (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Microsoft/Excel/v2/actions/router.js:45:26)",
      "    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Microsoft/Excel/v2/MicrosoftExcelV2.node.js:16:16)",
      "    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:722:19)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:704:51",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1134:20"
    ]
  }
}

Still… als existing nodes work perfectly fine! Anybody experience the same issues? or am I the only one?

6

Hi @Thomas_B ,

Both the working and non-working nodes are the same node version - 2.1 - so it’s not likely an issue with the instance version.

How to see a node's version

You can see the node version by clicking Settings in the node and checking the last line of text

Is your document in Onedrive or Sharepoint?

And do you get any error message when you try to get the rows, or just the warning you mentioned above?

7

Seems something with authentication. When login in the browser it works again. If I find the solution I’ll post it here. (in the mean time switched to google, it works flawless)

1 Like
8

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