1 of 1 people found this helpful
This is an issue we are aware of that was introduced in 2018.1. We are actively working to correct it.
Having updated to 2018.1 we also faced this issue with TabPy.
Do you have any esstimates when this will be fixed?
If necessary, we can provide any necessary data regarding the error (logs, etc.)
We are continuing to work on this issue. If you can send us your logs that would be very helpful!
Are you able to post them here?
Thank you for the reply. Could you please clarify what logs exactly do you
I need to know this to ask my Tableau Server admin to send me them. As far
as I know there are many logs on the server.
The logs we are looking for in this case are the vizqlserver logs, which should exist in the vizqlserver folder after you create a log snapshot and download it as described here:
Thank you very much for you time and cooperation!
2 of 2 people found this helpful
We now have a workaround for the issue. An error is occurring in the default timeout value for communications with TabPy. By manually setting this value in the server configuration using Tabadmin we can allow for connections to operate normally. The command to set is <vizqlserver.extsvc.connect_timeout_ms> and the default value to set it to is 1000. If setting this value to 1000 ms causes a timeout error, experiment with extending the timeout time. For more documentation on setting values with Tabadmin refer here:
The exact series of commands in the command line should look like:
cd "C:\Program Files\Tableau\Tableau Server\2018.1\bin"
tabadmin set vizqlserver.extsvc.connect_timeout_ms 1000
Worked perfect for me!
Nathan, appreciate this workaround
Wow - Thanks Nathan!!!