How to Restart Tableau Server

Restarting your Tableau Server is a critical piece of routine maintenance, whether you're applying updates, resolving performance hiccups, or just keeping the environment healthy. While it can feel a bit daunting, the process is straightforward once you understand the steps involved. This guide will walk you through exactly when and how to restart Tableau Server safely and effectively, covering both Windows and Linux installations.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Why Does Tableau Server Need a Restart?

Unlike a simple desktop application, Tableau Server is a complex collection of interconnected services and processes working together. A restart isn't just about turning it off and on, it’s a necessary procedure for several key situations.

• Applying Major Configuration Changes: Many significant changes you make using the Tableau Services Manager (TSM) require a full server restart to take effect. This includes modifying port numbers, configuring SSL, adjusting process settings, or updating authentication methods. The server needs to rebuild based on this new configuration.
• Troubleshooting Performance and Errors: A restart is often the first step in troubleshooting unexplained slowdowns, errors, or hung processes. It clears temporary caches, frees up memory, and terminates any rogue processes that might be bogging down the system, providing a clean slate for services to run correctly.
• Performing Scheduled Maintenance: Regular restarts can be part of a healthy maintenance plan. It proactively prevents minor issues from compounding into larger problems, ensuring your server remains stable and performant over time.
• Finalizing System-Level Updates: After applying operating system patches or server-level updates, a Tableau Server restart ensures all its components re-register and work correctly with the updated OS environment.
• Completing Upgrades and Restores: The restart is a non-negotiable step in the workflow for upgrading to a new Tableau version or restoring your server from a backup.

Before You Press Restart: A Pre-Flight Checklist

Jumping straight to a restart without preparation can lead to interrupted jobs, confused users, and corrupted data. Spending a few minutes on this checklist will save you headaches later.

1. Communicate with Your Users

Always announce the planned downtime. Send out a communication to all users letting them know when the server will be unavailable and for approximately how long. This prevents a flood of support tickets and manages expectations, showing that the maintenance is planned and controlled.

A typical announcement might say: "Please note: The Tableau Server will be down for scheduled maintenance on Tuesday from 10:00 PM to 10:30 PM EST to apply necessary updates. Please save your work and log off before this time."

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

2. Check for Active Jobs and Sessions

An abrupt restart can interrupt critical background tasks like extract refreshes, subscriptions, and data prep flows. This can result in incomplete data or jobs that need to be manually re-run.

Log into your Tableau Server, navigate to the Jobs page, and check for any tasks that are currently running or processing. It's best to wait for long-running jobs to finish. If necessary, you can manually cancel tasks before initiating the restart.

3. Verify Your Permissions

You can't restart the server without the proper credentials. You will need local administrator access to the machine where Tableau Server is installed. On Windows, this means running the Command Prompt as an Administrator. On Linux, you must be a user who is part of the tsmadmin group.

4. Review Pending Changes

The TSM interface allows you to queue up multiple configuration changes before applying them. Restarting the server will apply all of these pending changes. To avoid surprises, it’s wise to double-check exactly what you're about to apply.

Open a command-line interface and run the following command:

tsm pending-changes list

This will show you a list of all the configuration changes waiting to be applied. If you see something unexpected, you can clear the queue with tsm pending-changes discard before proceeding.

How to Restart Tableau Server: The Step-by-Step Guide

The standard, recommended method for restarting Tableau Server (version 2018.2 and later) is by using the Tableau Services Manager (TSM) command-line interface (CLI). TSM is the definitive tool for managing your deployment’s topology and configuration.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Method 1: The Standard Restart (Recommended for Most Cases)

The tsm restart command is your go-to. It’s a single command that gracefully stops all services, applies any pending configuration changes, and then starts them back up in the correct order.

Step 1: Open an Authorized Command Prompt

• On Windows: Go to the Start Menu, type cmd, right-click "Command Prompt," and select "Run as administrator."
• On Linux: Open a terminal session and log in as a user that belongs to the tsmadmin group.

Step 2: Run the Restart Command

In the command prompt window, type the following command and press Enter:

tsm restart

Step 3: Monitor the Process

The restart process will begin and can take several minutes, depending on your hardware and the complexity of your deployment. You'll see status updates printed directly to the console as TSM stops services, configures them, and brings them back online. Be patient and let it run to completion. You should see a "Server was restarted successfully" message at the end.

Method 2: The Manual Stop-and-Start

In some scenarios, you might want more control over the process. For example, you may need to clear temporary files, perform an offline backup, or run other maintenance scripts while the server is stopped. In these cases, you can stop and start the server as two separate actions.

Step 1: Open an Authorized Command Prompt

Follow the same process as above to open a command prompt with administrative privileges.

Step 2: Stop the Server

To shut down all Tableau Server processes, run:

tsm stop

Wait for the command to finish. This will confirm that all services are fully stopped before you proceed with any manual maintenance tasks.

Step 3: Start the Server

Once you've completed your maintenance, bring the server back online with:

tsm start

This command will restart all Tableau Server services. Note that if you have any pending configuration changes, they will not be applied with a simple tsm start. You must run tsm pending-changes apply after stopping the server but before starting it if you need those changes to take effect.

After the Restart: How to Verify Everything is Working

Once the restart command completes, your job isn't quite finished. You need to confirm that all services came back online correctly and that the server is healthy.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

1. Check the Service Status

Use the TSM status command to get a detailed report card on every process. The -v flag provides a verbose, process-by-process view.

tsm status -v

Scan the output. You are looking for an overall status of "RUNNING" at the top and confirming that each individual node and process listed also shows a "RUNNING" or "ACTIVE" status. If you see statuses like "DEGRADED," "ERROR," or "UNAVAILABLE," it’s time to start troubleshooting.

2. Access the Tableau Server UI

The most straightforward test is to log in. Open a web browser and navigate to your Tableau Server URL.

• Can you log in successfully?
• Does the home page load correctly?
• Click on a few dashboards or workbooks. Do they render as expected?

This simple smoke test immediately confirms if the end-user experience is functional.

Common Issues and Troubleshooting Tips

Sometimes, a restart doesn't go as smoothly as planned. Here are a few common problems and what to do about them.

• The Restart Takes a Very Long Time: On large, multi-node deployments, a restart can easily take 15-30 minutes or even longer. This is often normal. Don't be too quick to interrupt the process. If it seems truly stuck (e.g., no updates for over 20 minutes), you can check the tabadmincontroller log file for insights into what TSM is currently doing.
• One or More Processes Fail to Start: If tsm status -v shows a DEGRADED state with a specific process in an ERROR state (like VizQL Server or the Data Server), the first step is to try running tsm restart a second time. Sometimes, timing or dependency issues can cause a process to fail on the first attempt. If it continues to fail, examine the log files for that specific service to find the root cause.
• Permission Errors: If any tsm command fails with an "access denied" or permission error, double-check that you are running your Command Prompt or terminal session with the correct administrative privileges.

Final Thoughts

Restarting Tableau Server is a fundamental administrative task that keeps your analytics platform running smoothly. By following a structured approach - communicate, check for running tasks, use the correct TSM commands, and verify the outcome - you can perform this maintenance confidently and keep downtime to a minimum.

While Tableau is a powerful tool for deep, enterprise-level analysis, we’ve found that many marketing and sales teams get stuck on the technical setup and maintenance needed just to answer daily performance questions. We built Graphed to solve this by connecting directly to your marketing and sales platforms (like Google Analytics, Salesforce, and HubSpot) and letting you build dashboards using simple English. It delivers the insights you need instantly, without ever forcing you to manage server configurations or open a command line.