KNOWLEDGE BASE

Processes Fail To Start and UserPrincipalNotFoundException error in Logs Restarting or Adding Services to Tableau Server


Published: 20 Feb 2019
Last Modified Date: 31 Jul 2020

Issue

Processes fail to start on some nodes, and logs contain an error related to a UserPrincipalNotFoundException, similar to the following:

627  2019-02-12 14:37:31.272 -0500 20008 main : INFO  com.tableausoftware.tabadmin.security.windows.permissions.appliers.RegistryRightApplier - Set required registry read/write permissions for <Run As Username> on MACHINE\Software\Tableau
  628: 2019-02-12 14:37:31.279 -0500 20008 main : ERROR com.tableausoftware.tabadmin.security.windows.filesystem.WindowsFilePermissions - Failed to read file permissions on backgrounder_1.20183.18.1019.1426 for install user, <username>, and run-as user, <Run As Username>
  629  java.nio.file.attribute.UserPrincipalNotFoundException

 

Environment

  • Tableau Server 2019.2.1, 2019.1.5, 2018.3.8, 2018.2.11 and earlier versions 

Resolution

Option 1: 

Upgrade to Tableau Server 2019.2.2, 2019.1.6, 2018.3.9, 2018.2.12 or a newer version. Click here for downloads of current and previous versions of Tableau Server: Tableau Server Downloads and Release Notes. For more information on current releases, see Upgrade Tableau Server and Server Upgrade.

Option 2:

As a workaround, use the following TSM commands if install user is no longer active: 
tsm configuration set -k install.username -v <valid AD user>
tsm pending-changes apply


It may be necessary to do the above steps twice. 

Option 3:

As a workaround, use the following TSM commands if Run As User is no longer active:
tsm configuration set -k service.runas.username -v <valid RAU>
tsm pending-changes apply


It may be necessary to do the above steps twice. 

Cause

This behavior is related to a known issue with ID 903696 which has been corrected in more recent versions.

Additional Information

This issue occurred when the user account used to install Tableau Server or the Run As User no longer an active user in Active Directory. The issue could occur when restarting or when adding processes as we'll need to revisit the users permission for access. 

Did this article resolve the issue?