KNOWLEDGE BASE

Error (403) Occurred While Communicating With the Server


Published: 23 Mar 2017
Last Modified Date: 30 Aug 2017

Issue

After opening a view in a new browser tab, you may notice that views that you have previously opened in other tabs in the same browser window are no longer accessible. You may also see the following error message:

“An error occurred communicating with the server (403). This may be a temporary network condition. Please retry the operation if this condition persists, contact your system administrator.”

 

Environment

  • Tableau Server

Resolution

Step 1

In the search box, type Command Prompt. In the list of results, right-click Command Prompt, and select Run as administrator

Step 2

In the Command Prompt dialog box, change folders to the “bin” folder in the Tableau Server directory. For example, type one of the following commands depending on your machine:
  • For a 32-bit machine: cd “c:\Program Files\Tableau\Tableau Server\[version]\bin”
  • For a 64-bit machine: cd “c:\Program Files (x86)\Tableau\Tableau Server\[version]\bin”
Note: Replace [version] with the version of Tableau Server running on your machine.

Step 3

Type the following commands:  
  1. tabadmin stop
  2. tabadmin set vizqlserver.protect_sessions false
  3. tabadmin configure
  4. tabadmin start

Cause

Trusted authentication has been set up for Tableau Server and security enhancements that protect your data from unauthorized access and other vulnerabilities may cause the error message. One of the enhancements include added protection against tampering with VizQL sessions, which contain the sensitive data displayed in your view.

 

Additional Information

Depending on your environment, you may not need added levels of security protection such as trusted authentication. If Tableau Server has been configured to use high levels of security and it becomes an issue more than a benefit, you can ask your Tableau Server administrator to disable this added security level to help resolve the above error.
Did this article resolve the issue?