KNOWLEDGE BASE

Tableau Server 2018.2 or 2018.3 does not automatically start after host reboot on Windows Server 2016


Published: 24 Oct 2018
Last Modified Date: 17 Nov 2019

Issue

A Tableau Server deployment on Windows 2016 does not automatically start up after rebooting the system, and requires that a user bring up the tabadmincontroller and tabadminagent services manually before being able to start Tableau Server.

The Windows Event Viewer will show the following errors under System: 

Source: Service Control Manager
Event ID: 7000
Level: Error
Detail: A timeout was reached (30000 milliseconds) while waiting for the <service_name> service to connect.

Source: Service Control Manager
Event ID: 7009
Level: Error
Detail: The <service_name> service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Environment

  • Tableau Server 2018.2.0 - 2018.2.8, 2018.3.0 - 2018.3.5  and 2019.1.0 - 2019.1.2 
  • Windows Server 2016

Resolution

Option 1: 

Upgrade to Tableau Server 2019.1.3, 2018.3.6, 2018.2.9 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: 

Use this workaround to increase the timeout for the Windows Service Control Manager:
  1. Click Start
  2. Click Run
  3. Enter the following, and then click OK:
    regedit
  4. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
  5. In the right pane, locate the ServicesPipeTimeout entry; if the ServicesPipeTimeout entry does not exist, you must create it: 
    • Go to Edit > New > DWORD Value
    • Type ServicesPipeTimeout, and then press ENTER.
  6. Right-click ServicesPipeTimeout, and then click Modify.
  7. Click decimal
  8. Enter 240000
  9. Click OK
  10. Restart the host
After restarting the host, WSCM will allow enough time for TSM to start.

Cause

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

Did this article resolve the issue?