Skip to main content

Hi Folks, 

We host Tableau server for a client to allow them to create reports from data pulled from their their SQL database. 

 

I have had a request from their data analysis team, requesting Access to the Tableau repository through the PostgreSQL database. 

I have done some research and found the method to enble access, however I am hitting a wall. 

 

I ran the below command to try to create the read-only user: 

 

tsm data-access repository-access enable --repository-username RSARO_user --repository-password "INSERT_PASSWORD_HERE" 

 

When I run the above command, I get: 

 

 

C:\Windows\system32

>tsm data-access repository-access enable --repository-username RSARO_user --repository-password "FVRXCj9GpWZJEWamT43R" This operation will perform a server restart. Are you sure you wish to continue? (y/n): Y  

 

Starting update repository access asynchronous job. The update repository access job has failed. See '

F:\Program

Files\Tableau\Tableau Server\data\tabsvc\logs\tabadmincontroller\tabadmincontroller_*.log' on Tableau Server nodes running the Administration Controller process for server log information.  

 

Resource Not Found: The repository user 'rsaro_user' does not exist  

 

A little more research suggested that I would need to clean up any partially created user and try again, so I did the below: 

 

1️⃣ Make sure nothing is half-enabled

tsm data-access repository-access disable --repository-username RSARO_user

(Expect it to fail again with “not found”; that’s fine — it clears any pending config.)

2️⃣ Clean up Tableau’s configuration

tsm maintenance cleanup

That purges stale or orphaned configuration objects, including any broken repository-access records.

3️⃣ Regenerate internal service tokens

tsm security regenerate-internal-tokens

This command recreates Tableau’s internal “RSA” service accounts (those rsa__postgresql_access_* users). 

 It does

not affect licenses or content, but it forces Tableau to rebuild its internal trust credentials.

4️⃣ Restart Tableau Server

tsm restart

Wait until tsm status -v shows Repository 0 is running (Active Repository) again.

5️⃣ Try enabling access again with a new name 

 

 

tsm data-access repository-access enable --repository-username repoaccess_user --repository-password 

 

At this point, after trying to create the read-only user again, I get the same message. 

I ran the below to clean up: 

 

✅ Step 1 – Run cleanup

This removes any stale or half-written config objects from previous repository-access attempts:

tsm maintenance cleanup

Wait until it completes successfully.

✅ Step 2 – Regenerate internal service tokens

This command forces Tableau to recreate all of its internal service accounts — including the hidden 

 rsa__postgresql_access_* users that the enable command depends on:

tsm security regenerate-internal-tokens

You’ll be prompted to confirm a server restart. Type y when asked.

✅ Step 3 – Restart Tableau Server (if it didn’t automatically)

If the previous step didn’t already restart Tableau, do it manually:

tsm restart

Wait until:

tsm status -v

shows 

 'Tableau Server Repository 0' is running (Active Repository)

✅ Step 4 – Re-enable repository access with a new user name

Now try again — choose a brand-new username that hasn’t been attempted before (avoid rsa* prefixes; those are reserved):

tsm data-access repository-access enable --repository-username repo_access_user --repository-password

 

At this point I still get the same message. ChatGPT Tells me the below:

 

 

Then the internal repository mapping is missing from Tableau’s topology metadata. 

In that case:

  1. Gather logs:

tsm maintenance ziplogs --output "C:\temp\repo_access_issue.zip"

Open a Tableau Support case referencing:

Support has a repair script that re-registers the missing internal RSA record — it’s quick and safe.

Would you like me to help you locate exactly which log file line to check in 

 tabadmincontroller_*.log to confirm the missing repository user reference? That can confirm whether the regeneration succeeded before you retry.

You said:

when I run: tsm data-access repository-access enable --repository-username repo_access_user --repository-password "MyStrongPassword!2024" I Get: C:\Windows\system32>tsm data-access repository-access enable --repository-username rsa_repo_access_user --repository-password FVRXCj9GpWZJEWamT43R" This operation will perform a server restart. Are you sure you wish to continue? (y/n): y Starting update repository access asynchronous job. The update repository access job has failed. See 'F:\Program Files\Tableau\Tableau Server\data\tabsvc\logs\tabadmincontroller\tabadmincontroller_*.log' on Tableau Server nodes running the Administration Controller process for server log information. Resource Not Found: The repository user 'rsa_repo_access_user' does not exist.

ChatGPT said:

Thanks — this tells us something very specific and very important

: 

 

➡️ Tableau Server is failing BEFORE it can even create the new read-only user.

 

It is failing because

the internal Tableau “Repository Access Service Account” (RSA user) is missing, and regenerate-internal-tokens didn’t put it back.

And because of a design change in Tableau Server 2023.3+, the system must

have this internal RSA account before repository access can be enabled. 

 

Its now telling me to log a support ticket, Its some time since I dealt with Tableau server so I went looking for the Customer portal, which doesn't appear to exist anymore, and I have ended up here. 

 

Can anyone help me out here, or am I at a loss in trying to enable access? 

 

Regards, 

Lewis 

 

#Tableau

1 个回答
  1. 2025年11月26日 17:27

    @Lewis Benson

     

    The command is intended to be used with the username readonly. Don't try with a different user, only

    readonly user

    tsm data-access repository-access enable --repository-username readonly --repository-password "thepasswordyouwish"

     

    I strongly don't recommend you to use chatgpt for answers about Tableau Server. They frequently are incorrect or may damage your Tableau Server install.  In particular, 

    tsm security regenerate-internal-tokens

    is intended to run after install.  There are many reported cases that when this command is run in a production environment damages the install. 

     

    Instead of searching for answers with ChatGPT, look for expert assistance or create a questions here in the trailblazer community.  

     

    @Emeric LE SAULNIER DE SAINT JOUAN

    may have aditional info. 

     

    Finally, I wonder if despite the commands you have already run, your Tableau Server is still working. 

    https://help.tableau.com/current/server-linux/en-us/perf_collect_server_repo.htm#enable-access-to-the-tableau-server-repository

     

     

    If this post resolves the question, would you be so kind to "Select as Best"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you. 

     

    Regards, 

     

    Diego Martinez 

    Tableau Visionary and Forums Ambassador 

0/9000