No Valid Session Found error on Tabcmd?
James Golden Dec 3, 2015 10:19 AMHi folks,
Interesting and frustrating issue here:
This issue has been persisting for many months now, and is resulting in misleading error notifications displaying "no valid session found".
This stems from a third party, universal scheduler tool (ActiveBatch) that is passing multiple tabcmd refreshextract commands (triggered from DW batch job completions), from that machine, to tableau server, using the tabcmd utility.
Important to note, running the tabcmd job WITHOUT --synchronous, submits the job to the server, where that takes over, and dumps it into pending or one of the backgrounders. With --synchronous, the job is waiting for completion, and this seems to be where a session is lost, or some type of communication breakdown, even though truly submits on tableau server.
The command is similar to the one as follows (we have tried many iterations):
tabcmd refreshextracts -s http://gcctableau.gct.com --synchronous --project "${Tableau_Project}" --datasource "${Tableau_job_name}" --timeout ${Tableau_timeout} -u tableau -p XXXXXXX
The misleading errors appear typically appear more frequent when all the backgrounders are used, and the pending queue is backed up.
We have a two machine configuration, set for high extracts, with the one worker handling all backgrounders (4). Each machine is 32GB memory, 8 core, plenty of disc.
The error seems to indicate the session is not available, not authorized, possible expiring?
Here is an example:
C:\Users\abprod\AppData\Local\Temp>tabcmd refreshextracts -s http://gcctableau.gct.com -u tableau -p XXXXXXX --synchronous --project "Renewal and File" --workbook "2016 Renewal Performance (Interim)" --timeout 3600 ===== Continuing previous session===== Server: http://gcctableau.gct.com===== Username: tableau===== Scheduling extracts for workbook 'Renewal and File/2016 Renewal Performance (Interim)' to be refreshed now...
*** Not authorized
No valid session found. (errorCode=46)
The job seems to go into pending and eventually complete, but it is returning the above, noted error of no valid session.
Has anyone experienced this sort of issue before, or tried to run numerous tabcmd jobs at one time? Some jobs complete as expected, but others end in this error, even though the actual command is still executed on Tableau server, and eventually finishes normally.
Thanks for looking!
Jamie