Was this page helpful?
Yes No
Tableau Help > Tableau Server for Windows Help > 
Manage Server > Troubleshooting > Work with Log Files

Work with Log Files

Tableau Server creates log files as a normal part of its activities. You may need to use the server log files when you are troubleshooting issues with Tableau Sever or if Tableau Support requests logs to help you resolve an issue.

You can create a zipped log file archive (snapshot) from the command line on the server, or using the Generate Snapshot option on the Maintenance page. The zipped archive contains copies of the logs you can copy or download using a web browser, and send to Tableau Support. Once you have a copy of the archive, you can delete the archive from your server. For more information on creating, downloading and deleting log file archives, see Archive Logs on Status Page (Snapshot).

This collection of topics provides information about how to create log file archives, the contents of specific log files, and details about when and how you might want to look at a log.

Investigating Tableau Server Issues

The range and complexity of possible issues with Tableau Server means that there is no simple process you can use to investigate all problems, but a general approach would include these steps:

  1. Clean up existing log files to reduce their size. For more information, see Remove Unneeded Files.
  2. Set the appropriate logging level. This is something that Tableau Support will instruct you on. For more information, see Change Logging Levels.
  3. Reproduce the issue you are troubleshooting so the logs capture the events related to the problem.
  4. Create an archive of the logs. For more information see Archive Log Files .

    Important: Use this archive when looking at the log files. You should not edit, move or delete any files directly on the server.

  5. Review the server configuration file (\config\tabsvc.yml) to get a basic understanding of the server environment.
  6. Review the admin log (\logs\tabadmin.log) to understand any maintenance that has been done on the server.

    Search for run as: <script> to find entries specific to tabadmin activity.

  7. Review the Apache logs (\httpd\access.####_##_##_##_##_##.log and \httpd\error.log) for requests that may be related to the issue you are investigating.

    The Apache logs will contain a fair amount of "noise" that does not apply to issues you are experiencing.

    • If you find a request that seems to be related to your issue, search \vizqlserver for entries that include the unique request ID from the Apache logs.
    • Look for the response code and message associated with the request ID.
    • Search for the name of the workbook, view, dashboard, or data source that is related to your issue. Make sure to look for a relevant timestamp.
    • If you find a request that seems to be related to your issue, look at the response code associated with the request. (200s are good, 500s indicate problems.)
    • Locate the unique request ID associated with the request you've identified (the unique request ID is a 24 character alphanumeric string at the very end of the request).
  8. Review the log archive further to search for other messages and possible errors.

    • Use the request ID from the Apache logs to search the \vizqlserver folder of the log archive for files containing related log entries. Look for indications of a problem (for example, error messages or long-running queries).
  9. Contact support

    If you are not able to solve the issue yourself, or if requested by Tableau Support, send the zipped archive to Tableau.

See the following topics for more information: