> ## Documentation Index
> Fetch the complete documentation index at: https://docs.curator.interworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tableau Server Repository

> Connect directly to Tableau Server repository database for high-volume deployments

Sometimes (but very rarely) you may need to connect directly to Tableau Server's repository.  Generally this is
recommended when your user-count is very high (5000+ users), your Tableau Server connection is dealing with severe
latency that cannot be overcome (making the REST API responses very slow), or you need to enable the password reset
feature.  In these instances you will need to make sure your Tableau Server repository is enabled on Tableau Server first.

## Configuring Tableau Server's Readonly Account

By default, access to the Tableau Server repository is disabled.  To enable it, as well as set the password, you need to
issue a TSM command like the following against your Tableau Server:

```bash theme={null}
tsm data-access repository-access enable –repository-username readonly –repository-password "YOUR PASSWORD HERE"
```

Refer to Tableau’s [documentation](https://help.tableau.com/current/server/en-us/perf_collect_server_repo.htm) if you
would like a little more information about this.  Also, if your IT security has locked ports down on your Tableau
Server, make sure they open up port 8060 to Curator.

## Connecting Curator to the Repository

Once you have enabled access to the repository and set its password, you can configure the connection on Curator:

1. Login to the backend of your Curator instance (e.g. `http://curatorexample.com/backend`).
2. Navigate to the **Integrations** > **Connections** section from the left-hand menu.
3. Click on the Tableau Server connection you want to edit.
4. Expand the "Tableau Server Repository Connection" near the bottom of the page.
5. Enable the toggle for *Connect to Tableau Server's Repository Database* in the "Primary Tableau Connection" section.
6. Enabling the toggle will display a new section: "Tableau Server Repository Connection".
7. Check for any errors shown in this section.  They must be addressed before the connection can be established.
8. Expand the "Tableau Server Repository Connection" section and fill out the connection fields.  For information on how
   to find the default connection information on your Tableau Server, see:

   * **Repository Host** Tableau Server host url

   * **Repository Port** This value is *8060* by default.

   * **Repository User** *readonly* (recommended user)

   * **Repository Password** Password you set up in Step #1 on Tableau Server
9. Once properly filled out, click the "Save" button.

***

## Troubleshooting

### TABLEAU REPOSITORY CONNECTION FAILURE

If Curator logs the message `ERROR: TABLEAU REPOSITORY CONNECTION FAILURE`, Curator attempted to open a direct
PostgreSQL connection to Tableau Server's repository database and was refused or timed out.  Work through the
following checks:

1. **Confirm repository access is enabled on Tableau Server.**  Re-run the TSM command from
   [Configuring Tableau Server's Readonly Account](#configuring-tableau-servers-readonly-account) if you are unsure
   whether repository access was ever activated.  It is disabled by default on Tableau Server and must be explicitly
   enabled before Curator can connect.

2. **Verify port 8060 is open.**  Curator connects to Tableau Server's repository database on TCP port 8060 by
   default.  Confirm that the firewall on your Tableau Server allows inbound TCP connections from the Curator server
   on port 8060.  If the port is blocked, ask your IT or network team to open it from the Curator server's IP address
   to the Tableau Server.

3. **Check the credentials in Curator.**  In Backend > Integration > Connections, open the affected connection and
   expand the **Tableau Server Repository Connection** section.  Confirm that the **Repository Host**, **Repository
   Port** (default `8060`), **Repository User** (typically `readonly`), and **Repository Password** all match what you
   configured in the TSM command.

4. **Read the underlying PostgreSQL error in the Event log.**  Curator logs the full error every time the repository
   connection fails, so no debug toggle is required.  Navigate to Backend > Settings > Logs > Event log and open the
   `ERROR: TABLEAU REPOSITORY CONNECTION FAILURE` entry.  The complete error — including the underlying PostgreSQL
   error returned by Tableau Server's repository database — is recorded there and will tell you whether the failure
   was a refused connection, a timeout, an authentication error, or something else.

5. **Check the Custom Views listing for an on-page warning.**  On Tableau Server releases older than 2022.4 the
   Dashboard Custom Views listing (`/dashboard/:custom_views`) is built from the repository, so an unreachable
   repository makes it show the "Found no content" empty state.  When you open that listing while signed in to the
   backend, Curator also shows a warning banner above the tiles naming the Tableau Server whose repository
   connection failed, in addition to the Event log entry above.  Frontend-only visitors never see this banner; they
   only see the empty listing.  Newer releases and Tableau Cloud list Custom Views through the REST API instead, so
   the banner never appears for them even when the repository is enabled but unreachable.

> **Note:** Curator's general **Cron Debug Mode** (Backend > Portal Settings) logs cron job scheduling activity and is
> unrelated to repository connection failures.  You do not need to enable it — or any other debug mode — for this
> flow, because the connection error is always written to the Event log.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.