8 Replies Latest reply on Apr 5, 2018 4:29 AM by Mansi Bhandari

    Which log(s) to search for when unable to connect to the data source?

    Toby Erkson

      I have an end user who is using the REST API to view a workbook that has been published to the Tableau Server.  It seems to randomly generate this error (i.e. sometimes the connection is made and everything is glorious, sometimes the connection is not and thus errors):

       

      I'm trying to trouble-shoot what's going on.  I've searched the .log files on the primary and worker nodes for "fe_sendauth" as well as the User login ID to no avail.  Maybe it's simply not being captured.  Suggestions?

        • 1. Re: Which log(s) to search for when unable to connect to the data source?
          Jeff Strauss

          Hey Toby.  Typically when we run into issues with the API's, the way to debug is to use Postman.  I believe Postman is an extension to Chrome and it let's you send individual API commands to the server.  You start with a login and then whatever method is being called via the REST API documentation https://onlinehelp.tableau.com/current/api/rest_api/en-us/help.htm .  Also, I think I've seen the API traffic go through the httpd access log and then I think I've seen some errors appear within the vizportal logs so you can have a look here.

          1 of 1 people found this helpful
          • 2. Re: Which log(s) to search for when unable to connect to the data source?
            Toby Erkson

            Thanks Jeff.  I was able to get some info, like the vizql_session value...that may be helpful...

            • 3. Re: Which log(s) to search for when unable to connect to the data source?
              Toby Erkson

              ...nope

              Worth a shot but nothing in the logs nor http_requests table.  Maybe if the logging level was elevated above DEBUG but I'm not going to do that on our production environment.

              • 4. Re: Which log(s) to search for when unable to connect to the data source?
                Jeff Strauss

                I swear I've seen errors in the logs related to the API, but maybe it's a figment.  But when I look closer at your above screenprint, it appears as an authorization error / no password supplied.  Is it possible that it works when the data extracts is embedded in the workbook, but not when the data extract is published separate and has prompt for password?  Or is it a live connection that requires a password?

                 

                Also, if you happen to need help with Postman, let me know, we can have a quick webex as this is a good troubleshooting tool for calling the individual API methods.  What methods are being called anyways?

                • 5. Re: Which log(s) to search for when unable to connect to the data source?
                  Toby Erkson

                  I know nothing about API programming, this issue is with one of my end users.  I was trying to see if there is anything on the Tableau Server side that would help him, particularly since it appears randomly (not consistently reproducible).

                  • 6. Re: Which log(s) to search for when unable to connect to the data source?
                    Jeff Strauss

                    So is there any correlation to whether the workbook has a live connection that is prompting for a password (fails), vs. an embedded password (works)?

                     

                     

                    Also, I had a look in the httpd access log and vizportal log and see both requests (a signin, and then an API query of sites) appear in the httpd log and then only the first request (for whatever reason) show up in the vizportal log.

                     

                    • 7. Re: Which log(s) to search for when unable to connect to the data source?
                      Toby Erkson

                      It's an embedded password.

                      Yes, I saw the same info as you but nothing about any errors/warnings surrounding the time he gave me

                      I sent him the http_requests info and his response:

                      The Vizql session seems to have changed between when I landed on our dashboard asp.net page and it called the Tableau server, and when I clicked on a link on the page and it took me to a different Tableau report. 

                      Maybe that somehow creates an authentication problem now in 10.5 (haven’t seen this error in the past, even though I and many other users have made that transition from the default embedded report link to another report)?

                      This is all of the http_requests info regarding this issue (start from the bottom as created_at is shown in descending order):

                      idcreated_atcompleted_atcontrollerhttp_request_uriactionhttp_referersession_idportuser_idstatususer_cookievizql_sessionsite_idcurrentsheet
                      2605949604/02/2018 17:59:5804/02/2018 17:59:59/views/ShopcallImpact/EngineeringAll/views/ShopcallImpact/EngineeringAll?:embed=y&:showVizHome=n&:jsdebug=y&:tabs=n&:apiID=handler0undefinedshowhttp://ourcompany.net:81/HYJGlzbhT0KnYBrxj1ibWw91021772200NULL8C463533B2D749E5840906A419736C15-0:01ShopcallImpact/EngineeringAll
                      2605949504/02/2018 17:59:5804/02/2018 17:59:59/views/ShopcallImpact/EngineeringAll/views/ShopcallImpact/EngineeringAll?:embed=y&:showVizHome=n&:jsdebug=y&:tabs=n&:apiID=handler0undefinedshowhttp://ourcompany.net:81/HYJGlzbhT0KnYBrxj1ibWw91001772200NULL8C463533B2D749E5840906A419736C15-0:01ShopcallImpact/EngineeringAll
                      2605907904/02/2018 17:56:0804/02/2018 17:56:08/views/ShopcallImpact/EngineeringAll/views/ShopcallImpact/EngineeringAll?:embed=y&:showVizHome=n&:jsdebug=y&:tabs=n&:apiID=handler0undefinedshowhttp://ourcompany.net:81/HYJGlzbhT0KnYBrxj1ibWw91001772200NULL8C463533B2D749E5840906A419736C15-0:01ShopcallImpact/EngineeringAll
                      2605907804/02/2018 17:56:0804/02/2018 17:56:08/views/ShopcallImpact/EngineeringAll/views/ShopcallImpact/EngineeringAll?:embed=y&:showVizHome=n&:jsdebug=y&:tabs=n&:apiID=handler0undefinedshowhttp://ourcompany.net:81/HYJGlzbhT0KnYBrxj1ibWw91001772200NULL8C463533B2D749E5840906A419736C15-0:01ShopcallImpact/EngineeringAll
                      2605902504/02/2018 17:55:3704/02/2018 17:55:37/views/ShopcallImpact/PrintableDeptGroup/views/ShopcallImpact/PrintableDeptGroup?:embed=y&:showVizHome=n&:jsdebug=y&:tabs=n&:apiID=handler0undefined&RLG_Name=Department&Rlb_Name=Mechatronics&Rlc_Name=&Rld_Name=showhttp://ourcompany.net:81/HYJGlzbhT0KnYBrxj1ibWw91001772200NULL8C463533B2D749E5840906A419736C15-0:01ShopcallImpact/PrintableDeptGroup
                      2605842404/02/2018 17:49:0604/02/2018 17:49:06/views/CWORate/PrintableDeptGroup/views/CWORate/PrintableDeptGroup?:embed=y&:showVizHome=n&:jsdebug=y&:tabs=n&:apiID=host0showhttp://ourcompany.net:81/HYJGlzbhT0KnYBrxj1ibWw91021772200NULL1788C3437989406686D755D46195B8E0-0:21CWORate/PrintableDeptGroup
                      1 of 1 people found this helpful
                      • 8. Re: Which log(s) to search for when unable to connect to the data source?
                        Mansi Bhandari

                        Hello Toby

                         

                        This behavior occurs when:

                        • Address to connect to Tableau Server is not the hostname of the machine
                        • Tableau Server is not configured for a load balancer / proxy

                        Fortunately, there is a workaround in the meantime:

                        1. Open a command prompt as an administrator and navigate to the Tableau Server bin folder, for example C:\Program Files\Tableau\Tableau Server\9.0\bin
                        2. Run the following command:

                                     tabadmin set gateway.public.host "<name>"      

                        where <name> is the URL used to connect to Tableau Server, for example,  analytics.tableauserver.com

                         

                        If Tableau Server is configured for SSL (i.e. https://analytics.tableauserver.com), also run the following command:                  

                                    tabadmin set gateway.public.port 443

                        1. Apply the configuration changes, and restart Tableau Server by running the following commands:

                                            tabadmin config

                                            tabadmin restart

                         

                        Hope this helps!.