Hello Jeff,

Yes, "tabadmin status -v" shows that all the processes are running.

The host machine has 2 CPUs, each CPU has 8 Cores / 16 Threads, so a total of 16 Cores / 32 Threads.

The CPU base frequency is 1.8 GHz and the maximum Turbo frequency is 2.9 GHz.

Thank you!

Well no, even though "tabadmin status -v" shows that all the processes are running tableau is not accessible from the browser as nothing is rendering.

When trying to access http://127.0.0.1./admin/systeminfo.xml again nothing is loading.

So as long as this message "Unable to determine if all components ..." is given when you run "tabadmin start" the instance is not accessible.

As I said, following the procedure from here: Unable to Determine if All Components of the Service Started Properly - Help Analysing the Log File  seems to solve the problem but this doesn't mean that is normal.

The host has 256GB RAM and SSD storage

So, I just reproduced this on Tableau Server 2018.1.3.

These are the details:

1. I installed from scratch Tableau Server 2018.1.3

2. I applied the settings, started the service, navigate on the browser, all is good

3. stopped tableau, restored the most recent back-up from version 10.4.3, then when I execute tabamin start I got the same issue

4. even though I got the message "Unable to determine if all components of the service started properly" when I run tabadmin status -v shows that all the processes are running - please see the attached image

5. http://localhost is blank

6. accessing http://127.0.0.1/admin/systeminfo.xml loads for ever, so nothing appears

Yes, the free space on D is 1.01TB from a total of 1.09TB

Thanks Jeff,

As long as Tableau 10.4.3 was running fine on the same host from months, the same should be happening with 2018.1.3. This is one of the dedicated nodes and no other application is running, no antivirus either.

I notice this time that in tabadmin.log from version 2018.1.3 there are more details and these 2 sections come to my attention:

First one:

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 .

Second one, there are multiple lines with  "Waiting for component on 8600 to become ready by requesting " and then:

2018-07-13 15:32:31.172 +0000_DEBUG_10.5.2.232:tableau002-par_:_pid=21864_0x2c7106d9__user=__request=__ Gave up on with_vizportal_ready or with_sitesaml_ready, Tableau Server not available; check that it is running. file:/D:/Tableau Server/2018.1/bin/tabadmin.jar!/lib/service.rb:2060:in `with_component_ready'

file:/D:/Tableau Server/2018.1/bin/tabadmin.jar!/lib/service.rb:2019:in `with_vizportal_ready'

file:/D:/Tableau Server/2018.1/bin/tabadmin.jar!/lib/service.rb:1391:in `start'

org/jruby/RubyArray.java:1615:in `each'

org/jruby/RubyEnumerable.java:951:in `each_with_index'

file:/D:/Tableau Server/2018.1/bin/tabadmin.jar!/lib/service.rb:1384:in `start'

file:D:/Tableau Server/2018.1/bin/tabadmin.jar!/lib/service/service_runner.rb:33:in `start'

file:/D:/Tableau Server/2018.1/bin/tabadmin.jar!/lib/commands/start.rb:36:in `run'

file:/D:/Tableau Server/2018.1/bin/tabadmin.jar!/lib/multicommand.rb:255:in `dispatch'

file:/D:/Tableau Server/2018.1/bin/tabadmin.jar!/bin/tabadmin.rb:35:in `(root)'

org/jruby/RubyKernel.java:1058:in `load'

file:/D:/Tableau Server/2018.1/bin/tabadmin.jar!/bin/tabadmin.rb:1:in `(root)'

org/jruby/RubyKernel.java:1033:in `require'

file:/D:/Tableau Server/2018.1/bin/tabadmin.jar!/META-INF/main.rb:36:in `require'

<script>:3:in `(root)'

2018-07-13 15:32:31.172 +0000_DEBUG_10.5.2.232:tableau002-par_:_pid=21864_0x2c7106d9__user=__request=__ Tableau Server not available; check that it is running.

2018-07-13 15:32:31.172 +0000_INFO_10.5.2.232:tableau002-par_:_pid=21864_0x2c7106d9__user=__request=__ Unable to determine if all components of the service started properly. See "tabadmin.log" for more information.

I'll see if I can open a support case.

Thanks again!

Best regards.

Bogdan

Hello Zach,

There is no antivirus and no recent windows updates installed on our host.

I encounter this issue only after I restore a back-up from tableau 10.4.3 on tableau 2018.1.3. The restoration process is executed using the --no-config option.

Thanks,

Bogdan Amarghioali