Do not forget to engage the support on this matter, and ask them to solve the issue.
wow, this seems like quite an abrasive way to get it to work, but I do understand that it's a workaround. I am hopeful that Tableau support is pursuing in order to prevent these kinds of workarounds for the future.
Glad you got it working though.
Yea, I will be much happier when I can eliminate the restarts from the code.
Current update from Tableau Support is that they cannot replicate the problem on their machines and have not found any errors in the logs I have sent so far.
I have since sent them my workbook to evaluate if it is workbook specific and I have also sent Performance recordings of various processes (Vizqlserver, vizportal, backgrounder, tdeserver64, httpd, dataserver, and postgres) to see if the issue starts within a process.
Using the workbook I sent in, Tableau Support was able to recreate the problem with the error occurring at 35-45 downloads instead of 128, and have confirmed that tabcmd stops saving reports and all workbooks become inaccessible until the 'vizqlserver' process is restarted.
Mode updates as they come.
Thanks for the diligent follow-up on this, Michael! We run various exports of Tableau Server view information quite frequently on our server, but we've never slung that many requests at it in such a short timespan! Hopefully it can be fixed quickly.
It might been fixed in TS 9.0.6 release.
From the release notes:
Running a tabadmin export batch file caused intermittent "502 Bad Gateway" errors.
My guess they mixed up tabadmin and tabcmd.
@Michael, can you confirm it is solved with TS 9.0.6?
I am the Tableau software engineer working on this issue.
The issue appears to be caused by the reading of the Excel data source not releasing resources. I am working on a fix, but there is a workaround in the interim: In Desktop, in the workbook, take an extract of he Excel data source and republish the workbook to Server. By using the extract, Server does not have to make a connection to the Excel file.
Hi Doug Rudoff
We're experiencing the same issue but we're not using any Excel data sources. We are just taking an extract from our Netezza db every hour and displaying that info in a very simple view. We have a case open (01669756) as well.
We're not creating .pdfs, but .pngs and we are finding most of our attempts stall around 120 images (we need 142 currently). We've even gone as far as not using tabcmd and just having custom scripting try to grab the image with http get, but still facing a timeout towards the end of most runs.
We're struggling to find a solution and would love it if you guys can figure out why this is happening.
Any help would be much appreciated.
edit: to note that while we weren't using Excel in our dashboard, I was using a tiny (single column, 12 row) clipboard paste to constrain a tiny bit of the data. It was legacy as our data connection changed, but removing that data source seems to have sped this process up two-fold and we're not facing the same issues. More testing needed, but I'm starting to think this may be our issue as well.
From Michael's script...
::Reset the 128 Count limit before starting the file
net stop "Tableau Server Application Manager"
net start "Tableau Server Application Manager"
::Delay to allow Tableau to fully start before logging in
ping 18.104.22.168 -n 12 -w 5000
Thanks for the reply. My issue with this is that we're doing this hourly during business hours (from 7am until 10pm) and I'm unsure what consequences could arise from restarting the app manager every hour for a short period.
Please note my edit above, we're not completely tested but have had great progress so far after removing the other data source.
Another workaround to try is publish the live data source (Excel, or in Tim's case, Netezza) to Tableau Data Server, have the workbook connect to the published data source and use it to replace the original live data source, then republish the workbook.
For those who have not published and/or replaced a data source:
Publish data source to Server:
Data -> (Your data source name) -> Publish to Server
(In the case of an Excel file data source that a live connection is needed to read in updates to the file, you must unselect "Include External Files" at the bottom of the "Publish Data Source to Tableau Server" dialog. This can only be done if the Excel file is on a network share that both Desktop and Server can access, or a local file if Desktop is being run on the same system as a one-node Server. By default, when external files are included, a copy of the original Excel file is what is published.)
Connect to published data source:
Data -> New Data Source -> Tableau Server
Replace Data Source:
Data -> (Your data source name) -> Replace Data Source
Set "Current" to the original live data source, and "Replacement" to the newly published data source.
Server -> Publish Workbook
Did you found the solution for this.
We are also experiencing this error - has nothing to do with Excel data sources, but seems to have more to do with the number/frequency of GET requests to the server.
In our scenario, we have a job which retrieves database entries, iterates over them, and makes a request to the server, saving the file as a PDF. There are currently 618 records and this *intermittent* failure happens quite late in the process, and indeed doesn't always happen. It seems to have more to do with server load/usage.
Further, I have a scheduled task, which restarts Tableau and cleans logs (tabadmin clean --restart) right before the pdf process runs. This helps to speed up GET requests and typically avoids a "502" error. Although this morning, it did not.
Anything back from engineering/support? I'd be happy to provide access to log files/production environment.
I feel that I should also mention we're considering the purchase of another server license... hint hint.