Hi Chandra -
Tableau Server runs an instance of Apache Web Server for our own use. We expect the only instance of httpd on the box to be "ours", so maybe the startup configuration of "our" httpd is somehow impacting xampp? You're running a
If I had to figure this out on my own, I would find the httpd.conf file for EACH copy of httpd. Tableau's is generally here c:\programdata\Tableau\Tableau Server\data\tabsvc\config\httpd.conf
Find the one for your instance of apache and compare the two when Tableau Server is started vs. when Tableau Server has stopped. Are the values in "your" copy changing? Specifically, is the "Listen" property changing?
Maybe there's some sort enviornmental variable in play that is allowing "our" code to find "your" copy of httpd.conf and modify it, thinking it is ours.
This could be difficult to figure out, because you're not running a configration (two instances of apache on the same machine) that we'd really consider a best practice - we don't test for this.
Thanks Russell, If you have any other inputs will appreciate it.
Running two instances of Apache on the same box may not be considered a good practice, however, what is strange is that we did not face this issue in 8.0. We have an instance where it runs very well using 8.0
The use case is that we run an ETL using XAMPP on the same box so that refreshes could be quicker. (Or atleast we thought this was smart when we started)
We put the XAMPP and Server on Different Partitions (Drives) of the same box.
The problem stopeed.