KNOWLEDGE BASE

Tableau Desktop unable to connect to published data sources on Tableau Server with Error Code: 1076C501 & message: HTTP Status 405 – Method Not Allowed


Published: 14 Oct 2021
Last Modified Date: 19 May 2022

Issue

The error below may be encountered in Tableau Desktop when trying to connect to any data source published to Tableau Server:

An error occurred while communicating with Tableau Server
Bad Connection: Tableau could not connect to the data source.
Error Code: 
1076C501
Error: Unable to connect to this Tableau Server data source.
HTTP 405: <!doctype html><html lang="en"><head><title>HTTP Status 405 – Method Not Allowed</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 405 – Method Not Allowed</h1></body></html>
There was an error with the data source "xxxx". Verify that the data source is configured correctly.

 

Environment

  • Tableau Server
  • Tableau Desktop
  • Windows Server 
  • Proxy server
  • F5 Load balancer

Resolution

1. If an external load balancer such as F5 is used, check with the network administrator to verify and modify the HTTP profile setting in F5. 

2. Otherwise, run the following TSM commands on Tableau Server. If Tableau Server is running on a distributed environment, run the commands on the initial node in the cluster and inspect the results:
  • tsm configuration get -k gateway.trusted
  • tsm configuration get -k gateway.public.host
  • tsm configuration get -k gateway.public.port
The results from above commands must correspond with the appropriate tsm configuration set options described in the Tableau Help documentation Configuring Proxies for Tableau Server.

Cause

Tableau Server was not properly configured to work with proxy server and/or load balancer.
Or,
F5 Load Balancer HTTP profile was not configured correctly.
Did this article resolve the issue?