Loading
Slack製品の問い合わせ先はSalesforce Helpへ統合・変更されます続きを読む

Tableau Bridge Refresh Fails with "There is no active connection to the data source" (Status Code 3001) When a Virtual Connection Is Combined with Another Connection in a Published Data Source

公開日: Oct 12, 2026
説明
Applies To
  • Tableau Cloud
  • Tableau Bridge 
  • Published data sources that combine a Virtual Connection with one or more other connections, such as SQL Server or Excel on SharePoint/OneDrive

 

Cause
Reviewing the Bridge client log from a failed refresh shows this error for the Virtual Connection:

grpc secrets and port must not be empty — Can't connect using the virtual connection "<name>"...


This means Tableau Cloud isn't passing the required connection configuration (gRPC secrets and port) to Tableau Bridge for the Virtual Connection part of the data source. Bridge can't connect to the Virtual Connection, so the refresh fails with status code 3001.

This combination isn't supported yet. In a published data source refreshed through Bridge, all connections must be resolved together, including the Virtual Connection. Tests reproduced the failure whenever a Virtual Connection was combined with another database connection in a Bridge-driven refresh, regardless of connector type.

Other errors can show up in network captures and logs, such as OAuth-related messages. In this investigation they weren't the cause. Bridge was able to refresh its token and sign in, and the Virtual Connection configuration failure was the cause.

解決策
Resolution
Restructure the data source so the Virtual Connection isn't combined with another connection in the same Bridge-refreshed published data source. Options:
  1. Use the Virtual Connection in an embedded extract instead of a published data source.
  2. Split the data source so the Virtual Connection and the other connection are separate data sources, each refreshed on its own.
その他のリソース
How to Confirm You're Hitting This Issue
  1. Open the Bridge client log (TabBridgeClientWorker_svc) from the client that ran the failed job.
  2. Search for compute-task-error and grpc secrets and port must not be empty near the failure time.
  3. Check whether the failing data source contains a Virtual Connection plus at least one other connection.


ナレッジ記事番号

005461570

 
読み込み中
Salesforce Help | Article