When an extract refresh fails on Tableau Server, troubleshooting requires identifying the root cause—e.g., connectivity issues, resource constraints, or configuration errors. The Backgrounder process handles extract refreshes, so it’s a key focus, but the best diagnostic tool depends on granularity and context. Let’s explore this thoroughly:
Extract Refresh Process:
An extract refresh pulls data from a source (e.g., database, file) into a .hyper file stored on Tableau Server.
The Backgrounder executes these tasks based on schedules or manual triggers.
Errors could stem from: database connectivity, credentials, file access, resource overload, or task misconfiguration.
Option B (Background Tasks for Extracts administrative view): Correct. This is the most direct and detailed method:
Location: In the Tableau Server web UI, go to Server > Status > Background Tasks for Extracts (or site-specific under Site > Status).
Details Provided:
Task name, schedule, and workbook/data source.
Start/end times and status (e.g., Failed, Success).
Error messages (e.g., "Cannot connect to database," "Permission denied").
Why It’s Best: It pinpoints the exact failure (e.g., "timeout," "invalid credentials") for the specific refresh, offering actionable insights without needing to dig through logs manually. Server or site administrators can access this view to diagnose issues quickly.
Example: If the error is "Database login failed," you’d check credentials in the data source settings next.
Option A (Status of the Backgrounder process via tsm status -v): Partially useful but insufficient:
What It Shows: Running/stopped status of all processes (e.g., "Backgrounder: RUNNING").
Limitation: It confirms if Backgrounder is operational but doesn’t reveal why a specific task failed—no error details or task-level granularity.
Use Case: If Backgrounder is stopped or crashed, this might indicate a broader issue, but the question implies a single refresh error, not a server-wide failure.
Option C (The UNC path to the extract’s data source): Relevant but secondary:
Context: If the data source is a file (e.g., CSV on a network share), the UNC path (e.g., \\server\share\file.csv) must be accessible.
Why Not First: The error could be unrelated (e.g., database issue, not file-based). The admin view (B) would reveal if it’s a path issue first, guiding you to check the UNC path only if indicated (e.g., "File not found").
Practical Note: Backgrounder needs share permissions and the Run As account must access it—checking this without context wastes time.
Option D (Whether project permissions are set to Locked): Unlikely cause:
Permissions Impact: Locked permissions restrict who can edit/view content, not whether an extract refresh runs—that’s tied to the data source’s connection settings and Backgrounder execution.
Exception: If the refresh user lacks "Connect" permission to the data source, it might fail, but this is rare (owner/schedule typically has access). The admin view would flag this.
