Verify that you are starting Tomcat from the following location:

   Start>All Programs>SAS>BIArchitecture>Start Tomcat

Problem scenario 1:
If another application is using port 8080, then Tomcat fails to
start an error message similar to the following appears:

   SEVERE: Error initializing endpoint java.net.BindException:
   Address already in use: JVM_Bind:8080

Solution:
Configure Tomcat to listen on an available port by editing
C:\Tomcat4.1\conf to select a port number other than 8080:

   <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
   port="8080">

Note: Make sure you also change the port number in the web addresses
(URLs) used to start your client applications.

Problem scenario 2:
If your machine has insufficient memory, Tomcat fails to start
and an error message similar to the following appears:

     Error occurred during initialization of VM
     Could not reserve enough memory for object heap

Solution:
The best solution for this particular situation is to add more
physical memory (RAM) to the machine.

Problem scenario 3:
Tomcat could have problems locating the correct version of the JDK.

The file startServletContainer.bat in C:\SAS\BIArchitecture\Lev1\web\
sets the JAVA_HOME environment variable to the full path of the
installation directory for the Java 2 SDK. If this directory does not
exist as specified, Tomcat will not start.

Problem scenario 4:
Tomcat may already be installed as a Windows service and running.

If this is the case, Tomcat attempts to start briefly and then
disappears.

Solution:
Check the windows services to make sure that Apache Tomcat 4.1 is not
running as a service. If it is running as a service, select it and
choose "Stop Service".



Additional information on troubleshooting Tomcat can be found at the
following URL:

     http://jakarta.apache.org/tomcat/

Operating System and Release Information