3 Replies Latest reply on May 23, 2016 6:50 AM by Toby Erkson

    Tableau Server Backgrounder crashing leaving extracts not updated

    andrey tyurin

      Hi All,

       

       

      Our company using Tableau Server to allow business-users to explore data by themselves through editing predefined scaffolding workbooks that we have published. All data for scaffolding workbooks is stored on Tableau Server as extracts that are updated every day.

       

       

      Unfortunately we experience frequent crashes of Tableau Server Backgrounder component during daily updates thus leaving extracts not updated.

       

       

      This Backgrounder component is crashing with multiple records in Event Log:

      ...

      Restarting dead component 'Tableau Server Backgrounder 0'.

      ...

      Faulting application name: backgrounder.exe, version: 9200.16.204.1543, time stamp: 0x56b3f3a9

      Faulting module name: ntdll.dll, version: 6.3.9600.18194, time stamp: 0x56951674

      Exception code: 0xc0000374

      Fault offset: 0x00000000000f1b70

      Faulting process id: 0x2f34

      Faulting application start time: 0x01d1b23f26a9cb8d

      Faulting application path: c:\Program Files\Tableau\Tableau Server\9.2\bin\backgrounder.exe

      Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

      Report Id: 82018617-1e32-11e6-80bb-782bcb6dc07c

      Faulting package full name:

      Faulting package-relative application ID:

      ...

       

       

      Windows Error Reporting also creates records for each of these crashes.

       

       

       

      Additional information:

      — Tableau Server is installed on a dedicated server with Xeon E5649 @ 2.53GHz, 64 GB RAM, 500 GB RAID (200 GB free);

      — Performance Monitor does not show high CPU usage, memory pressure or high disk activity during background tasks;

      — SQL Server 2012 is the data source being used;

      — The issue happens occasionally on some data extracts, not all of them;

      — The issue persists if re-publishing the workbooks.

       

       

       

       

      Are there anyone who facing the same issue or has a clue on the reasons why this is happening?