English

How To: Enable full verbose logging for ArcIMS Application Server, Monitor, Tasker, Spatial Servers, and ArcSDE on Windows

Summary

Instructions provided describe how to enable complete ArcIMS verbose logging functionality for Application Server, Monitor, Tasker, Spatial Servers, and ArcSDE. Enabling verbose logging with all the ArcIMS components is helpful for troubleshooting technical problems or for testing ArcIMS applications.

Procedure

The procedure below enables logging and generates clean log files. Clean log files are one of the best tools for troubleshooting issues in a problematic ArcIMS configuration. Follow the procedure carefully.

Note:
Use of logging is not recommended for extended periods of time. Logging uses unnecessary computer resources and slows computer performance.

Follow the steps below:
  1. Enable the ArcIMS Application Server log files.
    1. Stop the ArcIMS Services in the following order:
      1. ArcIMS Tasker
      2. ArcIMS Monitor
      3. ArcIMS Application Server
    2. Navigate to <drive>:\Program Files\ArcGIS\ArcIMS\AppServer.
    3. Open the Appserver.properties file in a text editor. Find the 'debug' and 'logToFile' variables and set them equal to True. For example:
      debug=True
      logToFile=True
    4. Save and close the Appserver.properties file.
    5. Navigate to <drive>:\Program Files\ArcGIS\ArcIMS\AppServer.
    6. **(OPTIONAL)** Rename the ArcIMSSite.sez and ArcIMSFolders.sez files to ArcIMSSite.old and ArcIMSFolders.old.
      Note:
      Renaming the 'SEZ' files to '.old' removes all the currently available mapservices from the Application Server. Original mapservices can be recovered by re-renaming these files back to '.sez'. This may be required to help troubleshoot the issue.
  2. Enable ArcIMS Monitor log files.
    1. Navigate to <drive>:\Program Files\ArcGIS\ArcIMS\Server\Monitor.
    2. Open the Monitor.properties file in a text editor. Find the 'debug' and 'logToFile' variables and set them equal to True. For example:
      debug=True
      logToFile=True
    3. Save and close the Monitor.properties file.
  3. Enable the ArcIMS Tasker log files.
    1. Navigate to <drive>:\Program Files\ArcGIS\ArcIMS\AppServer\Tasker.
    2. Open the Tasker.properties file in a text editor. Find the 'debug' and 'logToFile' variables and set them equal to True. For example:
      debug=True
      logToFile=True
    3. Save and close the Tasker.properties file.
  4. Set the ArcSDE logging, if using data stored in ArcSDE, to verbose.
    1. On the SDE Server, find and open the <SDEHOME>/etc/dbinit.sde file in a text editor.
    2. Add the following line to the end of the file:
      set SDEVERBOSE=1
    3. Save and close the dbinit.sde file.
      Note:
      With SDEVERBOSE=1 (or true), information is then written to the SDEHOME/etc/sde.errlog file.
  5. Enable the Spatial Server log files.
    • For ArcIMS 3.1/4.0/4.0.1

      1. Find and open the aimsserver.cfg file in a text editor. This file is located:
        • On Windows, in <ArcIMS installation directory>\server\etc.
        • On UNIX, in <ArcIMS installation directory>/etc.
      2. Modify the first line of code, changing the values from:
        <AIMSSERVER debug="false" logfiles="Off" >
        To:
        <AIMSSERVER debug="true" logfiles="On" >
      3. Save and close the aimsserver.cfg file.
      4. Restart the ArcIMS Services in the following order:
        1. ArcIMS Application Server
        2. ArcIMS Monitor
        3. ArcIMS Tasker.
    • For ArcIMS 9.0/9.1

      1. Navigate to <ArcIMS Installation Directory>\server\etc.
      2. Open aimsserver.cfg in a text editor.
      3. Find the following lines of code:
        <AIMSSERVER  debug="False" 
                     logpath="" 
                     logmaxsize="" 
                     savefiles="true"     
                     logfiles="1" >
      4. Change the bold items below so it looks like:
        <AIMSSERVER  debug="False" 
                     logpath="C:\Program Files\ArcGIS\ArcIMS\Server\log" 
                     logmaxsize="" 
                     savefiles="true"     
                     logfiles="4" >
      5. Save and close the aimsserver.cfg file.
      6. Restart the ArcIMS Services in the following order:
        1. ArcIMS Application Server
        2. ArcIMS Monitor
        3. ArcIMS Tasker
        Note:
        For more information about working with Spatial Server log files, see the ArcIMS Help under: Advanced Topics > Work with Spatial Server Configuration Files > Change Settings for error messaging.

        ---OPTIONAL---

        At ArcIMS 9.0, it is possible to turn on the spatial server logging dynamically. The following command can be run on the machine where the ArcIMS Administrator is installed, and a new set of logs are generated in the directory specified above:
        "C:\Program Files\ArcGIS\ArcIMS\Jre\bin\java.exe" com.esri.aims.admincore.cmd.Exec http://machinename admin admin cmd setlogs true
        - For the above to work, the path to java.exe needs to match where it is installed on the system. "admin admin" is the username and password used to access ArcIMS Administrator.
        Note:
        For more information about command line administration for ArcIMS, click here.
    • For ArcIMS 9.2

      1. Navigate to <ArcIMS Installation Directory>\server\etc.
      2. Open aimsserver.cfg in a text editor.
      3. Find the following lines of code:
        <AIMSSERVER  debug="True"
                     logpath=""
                     logtype="log"
                     logformat=""
                     logmaxsize=""
                     logmaxlines=""
                     logmaxfiles=""
                     logsavefiles="true"
                     logmsglevel="2" >
        
          <LOGTYPES>
          </LOGTYPES>
      4. Change the logmsglevel to 4.
        <AIMSSERVER  debug="True"
                     logpath=""
                     logtype="log"
                     logformat=""
                     logmaxsize=""
                     logmaxlines=""
                     logmaxfiles=""
                     logsavefiles="true"
                     logmsglevel="4" >
        
          <LOGTYPES>
          </LOGTYPES>
      5. Save and close the aimsserver.cfg file.
      6. Restart the ArcIMS Services in the following order:
        1. ArcIMS Application Server
        2. ArcIMS Monitor
        3. ArcIMS Tasker
        Note:
        For more information about working with Spatial Server log files, see the ArcIMS Help under: Using ArcIMS Log Files > Enabling full verbose logging
        ---OPTIONAL---

        At ArcIMS 9.2, it is possible to turn on the spatial server logging dynamically for a single session. To do this, open ArcIMS Administrator > Select Tools > ArcIMS Logging. If a check box is listed beside ArcIMS Logging it is enabled, and logs will be created in the default location of C:\Program Files\ArcGIS\ArcIMS\server\log
  6. Add and Run Test MapServices.
    1. Open ArcIMS Administrator.
    2. Add only the mapservice(s) relevant to the problem in need of troubleshooting. If other mapservices are present, the test may produce inaccurate results.
    3. Save the Site Configuration in ArcIMS Administrator.
  7. Reproduce the problem to generate the log files.
    1. Do only the action(s) necessary to reproduce the problem behavior.
    2. As soon as the problem behavior has been fully reproduced, stop the ArcIMS Services, and collect the following files:
      • AppServerStatus.log file.
      • MonitorStatus.log.
      • Most recent Application Server log file found in the <ArcIMS Installation Directory>\AppServer\log.
      • Most recent Monitor log file found in the <ArcIMS Installation Directory>\Server\Monitor\log (MonitorDebug_*.log).
      • The sde.err log file from the ArcSDE server, if applicable.
      • Most recent Spatial Server log files. These log files are found in the <ArcIMS Installation Directory>\Server\log.
    3. Note: These files are generated in sets of about 9 or 10; collect the most recent set:
      • ImageServer__<servername>_*.log
      • ImageServer_ArcMap_<servername>_*.log
      • <servername>_*.log
      • GeocodeServer_<servername>_*.log
      • ExtractServer_<servername>_*.log
      • FeatureServer_<servername>_*.log
      • RouteServer__<servername>_*.log
      • QueryServer__<servername>_*.log
      • stderr_<servername>_*.log
      • stdout_<servername>_*.log

Related Information