cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Warehousing & Analytics
Engage in discussions on data warehousing, analytics, and BI solutions within the Databricks Community. Share insights, tips, and best practices for leveraging data for informed decision-making.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Databricks excel plugin error

oyslan
New Contributor II

Hi, i have an error with the excel pluging.

It was working fine until today. I can login and browse the catalog but I get an error when trying to query any data. It seems like its sending in a blank warehouse id. I have choosen a warehouse and its running. 

Anyone who knows what the reason can be?

Error message:
Excel operation failed in TableSelector: {"ok":false,"status":400,"statusText":"","json":{"error_code":"INVALID_PARAMETER_VALUE","message":"INVALID_PARAMETER_VALUE: is not a valid endpoint id."},"body":{},"statement":"SELECT `report_concept_id`, `code`, `name_no`, `name_en` FROM `tower-cs_dev_base`.`heartbeat`.`report_concept` LIMIT 1000","warehouseId":""}

 

7 REPLIES 7

GaneshI
New Contributor III

It looks like the issue is coming from the Snowflake Excel connector not receiving a valid warehouse/endpoint identifier when executing the query.

Since login and catalog browsing work fine, authentication is OK โ€” the failure happens at query execution time, which usually points to one of these causes:

  • The selected warehouse session context is not being passed correctly (blank/invalid warehouse ID)
  • The worksheet/excel plugin session lost the warehouse binding after an update or session timeout
  • The connector update changed how endpoint/warehouse IDs are resolved (this has happened in recent connector versions)

What you can try:

  • Re-select the warehouse in the Excel plugin and reconnect (donโ€™t rely on the previously selected one)
  • Fully log out of the Excel plugin and log back in
  • Restart Excel to clear cached session metadata
  • Verify the warehouse is active and not suspended
  • If multiple accounts/regions are used, ensure you're connected to the correct Snowflake account endpoint

If it started suddenly today, itโ€™s very likely a session/connector-side issue rather than a SQL problem.

If the issue persists, checking the latest Excel connector version or reinstalling it often resolves this type of โ€œinvalid endpoint idโ€ error.

hb03
New Contributor II

I'm seeing similar issue on our end as well, non of the above helped to resolve the issue

oyslan
New Contributor II

Same here. I still have the same issue. Have not managed to find a solution yet.

jp8
New Contributor II

Same issue here and it's impacting multiple users in my organization since Friday.

weerasa
New Contributor II

Same issue here, it's not working since last Friday. Appreciate it if you would fix this soon and give us an update!

weerasa_0-1779749932285.png

 

 

GaneshI
New Contributor III

The blank warehouseId in the request payload is the confirmed root cause. This means the Excel connector is successfully displaying your warehouse selection in the UI but failing to bind it to the query execution context. This is a known regression pattern in connector updates.

Escalated steps to try:

  1. Clear connector credentials completely โ€” don't just log out. Go to Windows Credential Manager (or Mac Keychain) and remove all saved Databricks/Snowflake entries, then reconnect fresh.
  2. Check for a connector update released last Friday โ€” since multiple users report the same start date, this is almost certainly a connector-side bug introduced in a recent release. Check your Excel add-in version and compare with the changelog.
  3. Downgrade the connector if an update was applied around Friday โ€” rolling back one version often immediately resolves this.
  4. Try the ODBC/JDBC connection as a temporary workaround while the connector bug is investigated.
  5. File a support ticket with your connector vendor (Databricks/Snowflake support) and include the exact warehouseId:"" payload โ€” this is strong evidence of a connector-side regression, not a user configuration issue.

Bottom line: Since multiple users hit this simultaneously after Friday, this is almost certainly a broken connector release, not something fixable on your end beyond a version rollback. Push the vendor for a hotfix.

ShivangiGujar
Visitor

Hey there,

I also have seen this type of error. But it automatically vanished the next day. I have not done any change in set up. Do you guys also faced the same behaviour of excel add-ins from databricks? In general, I get error and the next day or after some days it disappears.