3 weeks ago
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":""}
3 weeks ago
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:
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.
2 weeks ago
I'm seeing similar issue on our end as well, non of the above helped to resolve the issue
2 weeks ago
Same here. I still have the same issue. Have not managed to find a solution yet.
2 weeks ago
Same issue here and it's impacting multiple users in my organization since Friday.
2 weeks ago
Same issue here, it's not working since last Friday. Appreciate it if you would fix this soon and give us an update!
2 weeks ago
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:
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.
11 hours ago
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.