---
schema_version: "1"
id: d56812a87db935a0b124e1707a4fd061ce1001a0f2f4c87eff5b6a8e23d83d6c
title: Troubleshoot Job Failures Due to Service Failures
collection: tableau
version: current
locale: en-gb
portal_url: https://docs.salesforce.com/tableau/current/en-gb/server-linux/trouble_job_failures.md
canonical_url: https://help.tableau.com/current/server-linux/en-gb/trouble_job_failures.htm
source_site: help.tableau.com
content_type: documentation
content_hash: 300ca5c5bf1898e141389f560f5aff69b916361fc663d9bc33f763aca8abd47b
description: Understand error messages for job failures caused by service failures.
---
[Skip to main content](#main-content)

# Troubleshoot Job Failures Due to Service Failures

Beginning in Tableau Server version 2021.1, a new set of error messages help you understand when jobs fail due to an issue with a service. This topic explains the messages and what they can mean.

An error message will be displayed in this format:

<nodeId>
<service>\_<instanceId>.<version>: <error>

There are four categories of errors:

- **Missing status** - If a service is unable to report its status, for example, if a node is down, if tabadminagent is unable to report status or if a service has failed in a way that results in its dependent services not being able to be installed, this will show up as a "missing status" error.
- **Failed to update configuration** - If a service is unable to update its configuration file, this shows up as a "failure to update configuration" error. This may occur during upgrades, when attempting to apply pending changes to new services. See the service's control app log, `<dataDir>\tabsvc\logs\<service>\control-<service>_<nodeId>-<instanceId>`, for more details about the error.
- **Failed to reach the requested state. Current state:<currentState>** - If a service cannot be installed/removed/started/stopped, this results in a "failed to reach requested state" error. This can happen during upgrades when new services are being installed and old ones removed. Possible options for <currentState> are: DEPLOY\_FAILED, INSTALL\_FAILED, DISABLE\_FAILED, ENABLE\_FAILED, CONFIGURE\_FAILED, UNINSTALL\_FAILED, REMOVE\_FAILED. Most common are: INSTALL\_FAILED, UNINSTALL\_FAILED and REMOVE\_FAILED. See the service's control app log, `<dataDir>\tabsvc\logs\<service>\control-<service>_<nodeId>-<instanceId>`, for more details about the error.
- **Failed to start/stop. Current status: <currentStatus>** - This occurs if a service that should be running is stopped or if a service that should be stopped continues to run. Possible values in <currentStatus> are: ACTIVE, BUSY, PASSIVE, UNLICENSED, DOWN, STATUS\_UNAVAILABLE and DEGRADED. The first three (ACTIVE, BUSY, PASSIVE) are considered "running" statuses. The last four are a "stopped" status. See the main service log, `<dataDir>\tabsvc\logs\<service>\<service>_<nodeId>-<instanceId>.log`, for more details about the error.

An example of an error message is:

This job failed due to unexpected error: 'ServiceOperationTimeoutException'
One or more services failed to reach their expected state.
node1:
     vizportal\_0.2021.4.0.0: Failed to reach requested state. Current state: INSTALL\_FAILED

Beginning in version 2021.3, an additional error message has been added for the second and third error types that will match the errors found in the control app logs.