Download Track+ PM Installation Guide
Transcript
7 Trouble Shooting Track+ PM 7.1 Possible Conlicts with Competing Web Servers If on first startup you do not get the login screen, there may be another web server already running on port 80 and 8080 of your system. Competing web servers could have been installed for example as part of Windows Server, Visual.NET, or some other development software. Also known to cause problems are servers that have Oracle installed on them. Oracle might install its own web server on port 80 and 8080. Skype can also block these ports. To get Track+ PM running in such a case, you should either shut it down, or deploy Track+ PM with it. Alternatively you could change the default port in file server.xml of the Tomcat server (by default installed under C:\Program Files\Apache Software Foundation\Tomcat 8.0\conf) from 8080 to some other number. In this case you have to enter the port number as part of the URL where you access Track+ PM , like http://localhost:7080/track instead of http://localhost/track. 7.2 Potential Problem on Windows 2003 Server The Track+ PM installer runs itself an installer for the Firebird database management system. There is a known problem with this installer on Windows 2003 Server Systems. To solve this problem download the Firebird installer yourself and run it manually. Then have a look at the Track+ PM forum for an up to date work around to get the database server up an running. Thereafter run the Track+ PM installer again. 7.3 Possible Problems on 64-Bit Windows Systems On a 64-bit system, also make sure that you have a 64-bit Java installed, and that your JAVA_HOME variable points to the 64-bit version. If you have an older 32-bit version uninstall that first. 7.4 Installation Problem Debugging The installer writes a log file in the same directory from which you executed the installer. This log file contains a lot of hints in case something should have gone wrong. 41