3 Replies Latest reply on Jul 19, 2018 9:40 PM by John Kuo

    upgrade error "Waiting for component on 8600 to become ready by requesting http://localhost:8600/vizportal/check_status"

    John Kuo

      I've ran into this issue a couple of time where in the final stage of upgrading, I can see in tabadmin.log that the process gives up after numerous try to check on vizportal. This is the snippet from tabadmin.log

       

      =__ Waiting for component on 8600 to become ready by
      requesting http://YOUR_SERVER_NAME:8600/vizportal/check_status...

      2018-05-31 02:16:23.269


      -0500_DEBUG_169.254.0.2: YOU_SERVER_NAME_:_pid=32980_0x43f1bb92__user=__request=__
      Waiting for component on 8600 to become ready by requesting http://YOUR_SERVER_NAME:8600/vizportal/check_status...

       

      2018-05-31 02:16:43.300-0500_DEBUG_169.254.0.2: YOU_SERVER_NAME_:_pid=32980_0x43f1bb92__user=__request=__

       

      Waiting for component on 8600 to become ready by requesting http://YOUR_SERVER_NAME:8600/vizportal/check_status...

       

      2018-05-31 02:16:53.316
      -0500_DEBUG_169.254.0.2:EDDEDATABAPP11_:_pid=32980_0x43f1bb92__user=__request=__

       

      Gave up on with_vizportal_ready or with_sitesaml_ready, Tableau Server not
      available; check that it is running. file:/D:/Program Files/Tableau/Tableau
      Server/10.2/bin/tabadmin.jar!/lib/service.rb:1978:in `with_component_ready'

       

      I have one firewall rule with all the necessary ports opened for Tableau Server, including port 8600. A colleague told me he has seen this error before and the solution is to make another standalone firewall rule to open port 8600. I did this and did not encounter the issue since.

       

      We suspect the cause is due to the installation trying to use an old deprecated command, per the tabadmin.log:

       

      IMPORTANT: Command executed successfully.

       

      However, "netsh firewall" is deprecated;

       

      use "netsh advfirewall firewall" instead.

       

      For more information on using "netsh advfirewall
      firewall" commands

       

      instead of "netsh firewall", see KB article
      947709

       

      at http://go.microsoft.com/fwlink/?linkid=121488