English

How To: Diagnose a problem with the ArcIMS Application Server failing to start

Summary

Instructions provided will help you diagnose the reason, among several possible reasons, why the ArcIMS Application Server might fail to start.

Procedure

The following are four common reasons the ArcIMS Application Server fails to start. Try each procedure as outlined, in the order given. If they do not provide an answer, proceed to "Contact ESRI Technical Support" supplying the analysts with your answers to the questions, plus additional information as described in that section.

  1. WINDOWS ONLY: SERVICE LOGIN FAILURE

    When starting the ArcIMS Application Server an error message displays:

    "Error 1069: The service did not start due to a logon failure"

    Check for a problem with the user account associated with the service:

    A. Navigate to Control Panel > Administrative Tools > Services.
    B. Double-click on the ArcIMS Application Server service.
    C. Select the Logon tab.
    D. Browse to the user account you want to use.
    D. Re-type the password.
    E. Click OK.

    Does it start? If yes, repeat the steps for the ArcIMS Monitor and Tasker services. If not, try a different user account.

  2. CORRUPT SEZ FILES

    The .sez files store the information of your configuration as shown in Administrator and are being read by the ArcIMS Application Server.

    Determine if corrupt .sez files are preventing the ArcIMS Application Server from starting:

    A. Browse or change directory to your ArcIMS Application Server directory. On Windows this is usually located in <installation directory>\ArcGIS\ArcIMS\AppServer. On other platforms this is usually located in $AIMSHOME/Middleware/Application_Server.

    B. Rename ArcIMSSite.sez to another name such as ArcIMSSite.sez.old. After renaming there should not be an ArcIMSSite.sez file.

    C. Start the ArcIMS Application Server.

    If the Applicaton Server starts, the problem is related to a corrupt *.sez file and you'll need to re-create your ArcIMS map services in Administrator.

  3. REQUIRED PORT IS IN USE

    If another application is using port 5300 or port 5353 it may prevent the Application Server from starting. The AppServerStatus.log file, found in the Application Server directory, will contain an java.net.BindException message and indicate the port in use.

    To change the port:

    A. Run the ArcIMS Post Installation.
    B. Select Custom configuration.
    C. Check ArcIMS Configuration and uncheck the other options.
    D. Continue with the Post Installation and complete the information as asked.
    E. At the dialog box that asks for the Registry Port and the Connector Port, change the conflicting port number already in use on the system.
    F. If ArcIMS is distributed across multiple machines, repeat the above steps on each ArcIMS machine.

  4. USING BETA OR PRE-RELEASE SOFTWARE

    Beta or pre-release versions of the ArcIMS Application Server have time limits for use. If it expires the ArcIMS Application Server doesn't start. Look for the message that time has expired for the version being used in the AppServerStatus.log file found in the Application Server's directory.

    You will need to obtain a newer version of the product.
  5. Contact ESRI Technical Support

    If none of the procedures above gave satisfactory results, contact ESRI Technical Support. You will be asked to provide the following information:

    Question 1: What were your results when you followed the procedures in this article (#28010)? Please include this article number, #28010, in your request for support.

    Question 2: Can ESRI Support provide further assistance with any procedures given in this article?

    Question 3: Is this a new/updated installation of ArcIMS or was it working before?

    Question 4: Are any error messages received when attempting to start the Application Server?
    Question 5: Does the ArcIMS Monitor or Tasker start?

    Additional information to send:

    - AppServerStatus.log from the Application Server directory.

    - AppServer.properties file from the Application Server directory.

    - ArcIMSSite.sez file if it exists and seems to be related to the problem.