How to Restart Power BI Gateway

When your Power BI reports stop refreshing, it can feel like a major roadblock, but the solution is often surprisingly simple. A quick restart of your on-premises data gateway is one of the most effective first steps to solving a wide range of data refresh issues. This article will show you exactly how to do it using two different methods, helping you get your data flowing correctly.

Graphed

Your AI Data Analyst to Create Live Dashboards

Connect your data sources and let AI build beautiful, real-time dashboards for you in seconds.

Build Your First Dashboard

When your Power BI reports fail to refresh, a quick restart of your on-premises data gateway can often be the simple fix you need. A gateway can get stuck for various reasons, from network hiccups to a recently installed update, and restarting the underlying service acts as a clean reset. This guide will walk you through two reliable methods for restarting your gateway, plus key troubleshooting tips if the issue persists.

AI for Data Analysis

Crash Course

Graphed

Free PDF Guide

AI for Data Analysis Crash Course

Learn how to get AI to do data analysis for you — the best tools, prompts, and workflows to go from raw data to insights without writing a single line of code.

Download Free Guide

What is a Power BI Gateway?

Before we jump into the steps, let's briefly touch on what the on-premises data gateway actually is. Think of it as a secure bridge. It sits on a computer within your company's network and creates a safe pathway for cloud services, like Power BI, to access your on-premises data. This data lives behind your company firewall in sources like SQL Server databases, file shares, or other internal systems.

Without this gateway, Power BI wouldn't be able to reach your private data to keep your reports and dashboards updated. Like any constantly running software, it can sometimes run into temporary glitches that a simple restart resolves.

Common Reasons to Restart the Gateway:

• Failed Data Refreshes: This is the most common reason. If your scheduled refreshes are suddenly failing with generic connection errors, a restart is a great first troubleshooting step.
• Slow Performance: If refreshes are taking unusually long, the gateway service might have a memory leak or a hung process. Restarting it can clear these issues and restore performance.
• Configuration Changes: If you've recently made changes to the network environment, the gateway server, or firewall rules, a restart helps ensure the gateway service picks up these new settings correctly.
• Applying Updates: After updating the gateway software, it often needs a restart to finalize the installation and run the new version.

Method 1: Using the On-premises Data Gateway Application

The most straightforward way to restart the gateway is by using the application installed on your server. This method is user-friendly and designed to be the primary way of managing your gateway's service.

Step-by-Step Instructions:

1. Log into the Gateway Server: First, you'll need to remote into or physically access the Windows machine where your gateway software is installed. You'll need administrative rights on this machine.
2. Open the Gateway Application: Click the Start menu or use the Windows search bar and type "On-premises data gateway". Open the application from the search results.
3. Go to Service Settings: Once the application launches, look for the list of options on the left-hand menu. Click on the "Service Settings" tab.
4. Restart the Gateway: In the Service Settings screen, you'll see information about the gateway's status and an option to restart it. Simply click the "Restart now" button. The application will handle the rest, automatically stopping and then starting the service for you.
5. Confirm the Status: After a few moments, the application should show that the gateway is running and connected again. The main "Status" screen should display a green checkmark confirming everything is online and ready.

This is generally the best method for most users, as it's quick and requires no knowledge of Windows services management.

Method 2: Restarting From Windows Services

Sometimes, the gateway application itself might be unresponsive or fail to launch. In these cases, you can bypass the application entirely and restart the gateway directly from the Windows Services management console. This is a more direct approach and is just as effective.

Graphed

Your AI Data Analyst to Create Live Dashboards

Connect your data sources and let AI build beautiful, real-time dashboards for you in seconds.

Build Your First Dashboard

Step-by-Step Instructions:

1. Access Windows Services: On the gateway server, press the Windows Key + R to open the "Run" dialog box. Type services.msc into the box and press Enter. This will open the Services console.
2. Locate the Gateway Service: The Services window lists all the services running on the machine in alphabetical order. Scroll down until you find the service named "On-premises data gateway service".
3. Restart the Service: Right-click on "On-premises data gateway service" to bring up the context menu.
4. Click "Restart": Select the "Restart" option. Windows will now stop the service and all its related processes and then start it again. If "Restart" is greyed out, you can click "Stop," wait a few seconds for the status to show as blank, and then right-click again and select "Start."
5. Verify the Status: Once it's done, the "Status" column for the service should say "Running." Your gateway is now back online.

This method comes in handy when the gateway's interface is frozen, giving you a reliable backup plan to get your data flowing again.

Restarting a Gateway in a Cluster

If your organization uses a gateway cluster for high availability and load balancing, the process is largely the same, but it requires an extra layer of consideration. A cluster is simply a group of gateways working together. You'll need to restart the service on each individual machine that is part of the cluster.

Best Practices for Restarting a Cluster:

• Restart One at a Time: To avoid a complete outage of your data refreshes, it's best to restart the gateways sequentially, not all at once.
• Verify Each Node: Restart the service on the first machine using one of the methods above. Before moving to the next one, go to the Power BI service online and check that the cluster is still considered "online." At least one active gateway is usually enough to keep the cluster operational.
• Proceed to the Next Gateway: Once you've confirmed the cluster is stable, log into the second machine and restart its gateway service. Repeat this process until you've restarted every member of the cluster.

This staggered approach ensures that there's always at least one active gateway available to handle refresh requests, preventing any service interruptions for your end-users.

Troubleshooting After a Restart

Most of the time, restarting the gateway solves the problem. But what if it doesn't? If your data refreshes are still failing or the gateway appears offline even after a restart, here are a few things to check.

AI for Data Analysis

Crash Course

Graphed

Free PDF Guide

AI for Data Analysis Crash Course

Learn how to get AI to do data analysis for you — the best tools, prompts, and workflows to go from raw data to insights without writing a single line of code.

Download Free Guide

Gateway Shows as Offline

If the gateway is still offline in the Power BI Service after a restart, check the gateway application on the server. If it shows an error:

• Verify the Account: Make sure you are signed into the gateway application with the correct Power BI account. The account must have proper permissions to manage the gateway.
• Check Network Connectivity: Ensure the server itself has an active internet connection. Try pinging a public website like google.com from the server to confirm it has outbound connectivity. Corporate firewalls can sometimes block the necessary ports that the gateway uses to communicate with Power BI.

Data Refreshes Still Fail

If the gateway is online but reports continue failing:

• Test the Data Source Connection: In the Power BI Service, go to Settings > Manage gateways. Find your gateway, click the three dots, and select "Settings". From there, you can test each of your data source connections to see if credentials have expired or if the data source itself is unreachable.
• Examine the Gateway Logs: The gateway application itself has a diagnostics section where you can export detailed logs. These log files can be complex, but they often contain specific error messages that will point you directly to the root cause, whether it's a permissions issue on the data source or a problem with a specific query.

Final Thoughts

Restarting your Power BI on-premises data gateway is a fundamental troubleshooting step that can solve many common data refresh issues. By understanding how to restart it through either the gateway application or the Windows Services console, you can quickly address connection problems and keep your organization's data up-to-date and reliable.

While managing on-premises gateways is part of the job for many data professionals, the setup and maintenance can become tedious, especially when you're connecting dozens of platforms. At Graphed, we remove that friction entirely by connecting directly to your cloud data sources like Shopify, Salesforce, and Facebook Ads in just a few clicks. This completely eliminates the need for gateways and manual CSV downloads. We believe you should be able to get answers from your data instantly by just asking a question, not by spending your time troubleshooting IT infrastructure.