Problem: The ArcIMS Administrator Servers tab shows empty Server and Virtual Servers lists


When clicking on the Servers tab in the ArcIMS Administrator, the Server and its Virtual Servers list is empty.


Some of the most common causes are listed below. You can find the correlating solution to each cause by matching their item numbers in the Solution section that follows. For example, Cause 1. is solved by Solution 1., and so on.

1. The ArcIMS Spatial Server might not be running.
2. The environment variables needed for ArcIMS is not set correctly.
3. The ArcIMS Spatial Server is unable to communicate with the Application Server.
4. The ArcIMS Monitor's listener port that is used by the ArcIMS Application Server and ArcIMS Spatial Server for communication is already in use.

Solution or Workaround

Refer to the solution below that correlates with the cause of the same number above:

  1. Verify that the ArcIMS Spatial Server is running. Type:
    ps -ef | grep aims

    The return display will be similar to this:
    marin% ps -ef | grep aims
       ims40 10673     1  0   Apr 25 ?        0:00 /bin/sh ./aimsmonitor start
       ims40 10653     1  0   Apr 25 ?        0:00 /bin/sh ./aimsappsrvr start
       ims40 10693     1  0   Apr 25 ?        0:00 /bin/sh ./aimstasker start
       ims40 10730 10680  0   Apr 25 ?        0:05 /marin1/hema/ims40/AIMS40/aims40exe/bin/aims
    server.exe marin_1 marin 5050
       ims40  8698  8692  0 08:27:41 pts/4    0:00 grep aims

    The aimsserver.exe is responsible for running the Spatial Server.
  2. Verify that environmental variables are set when ArcIMS starts the Spatial Server; the most important environment variable is to set the LIBRARY PATH.
    The following variables should be set. This example assumes you are using the .cshrc file:
    setenv AIMSHOME <ArcIMS Installation Directory>/aims40exe
    setenv JAVA_HOME <JRE Installation Directory>/jre
    set path = ($JAVA_HOME/bin $AIMSHOME/bin $path .)

    IBM AIX and HP-UX machines use different settings for the LIBRARY PATH.
    IBM AIX requires:
    setenv LIBPATH $AIMSHOME/lib;$AIMSHOME/bin

    HP-UX requires:
  3. The Monitor daemon is responsible for starting the Spatial Server. To make sure the Monitor is running correctly, navigate to the Monitor directory:
    cd $AIMSHOME/Monitor

    Open the Monitor.properties file and verify that the 'registryHost' entry is valid such as:
    ### The name of the computer on which the ArcIMS Application Server is running.

    The Application Server is now communicating with the Spatial Server, using the correct name.
  4. Check the availability of the ArcIMS ports:

    A. Verify that the Monitor's listener port is free; by default this is port 5050. Verify that other instances of ArcIMS Monitor are not using this port. Type:
    ps -ef | more

    Check if the Monitor daemon is running. If so, get the PID of the process and kill the process. Type:
    kill -9  <PID>

    B. Check the /etc/services file to see if port 5050 is already in use. This file is a local source of information used to define which ports are used by the system daemons for particular services, such as ftp, http, and telnet.

    C. Get a list of the processes running or idle, including the ports assigned to each one of the processes. Type:
    netstat -an | more

    Verify that port 5050 is not in use.

    D. Sometimes a process will not be listed, but it is still running. To avoid such situations, navigate to $AIMSHOME/Xenv and shutdown the Monitor daemon. Type:
    ./aimsmonitor stop

    This will free the port if it is being used.
  5. If the Spatial Server is installed on a remote machine, things to check would be:

    A. If both machines are able to ping each other.
    B. The Montor's listener port is open; by default this is port 5050.
    C. The /etc/hosts file on each machine has the entry of <IP address> <machine name> of the other machine.
    D. The Monitor.properties file has the correct value for "registryHost", which is the name of the Application Server machine.
  6. In rare situations, ArcIMS 4.0.1 and earlier versions of the software on Unix platforms may require an additional environment variable setting. See the following document for more information:
    Error: An input/output error has occurred in ContainerProxy

    If none of the above steps helped to resolve the issue, enable the logs to get specific information. Information about related subjects can be found in the Index article below.

Related Information