Is This Content Helpful?
We're glad to know this article was helpful.
The ArcIMS Spatial Server writes LOG files on Windows to <ArcIMS Installation Directory>\Server\log and to $AIMSHOME/log on UNIX.
In a typical installation, a total of eight (version 3.x) or nine (version 4.x) LOG files are created each time the ArcIMS Monitor process is started. Each component of the ArcIMS Spatial Server--image, query, feature, geocode, extract, and metadata (4.x only)--has its own LOG file. In addition, two LOG files are created for third party applications and one LOG file describes the overall state of the Spatial Server. Optional extensions and multiple Spatial Servers add to the total number of LOG files.
The LOG file related to the metadata component is created only after a Metadata Service has been initialized for the site. Additional metadata LOG files are not created unless the initial file is deleted.
For ArcIMS 9.2 see ArcIMS Help topic 'About interpreting Spatial Server log files'
The following is an example of the information written to the LOG files when the log mode is set to 'On'. The LOG file mode is 'Error' by default and must be altered in order to retrieve this information. To learn about the various modes available and how to select them, see the link in Related Information below.
Tue Jun 13 09:14:51 2000][462 489 INFO1] SERVICE: reg
Tue Jun 13 09:14:51 2000][462 489 INFO2] AXL Parse Time: 0.010000s
Tue Jun 13 09:14:51 2000][462 489 INFO2] RENDERER SETUP: 0.000000s
Tue Jun 13 09:14:51 2000][462 489 INFO2] FEATURE LAYER:
Tue Jun 13 09:14:52 2000][462 489 INFO2] DATA SEARCH TIME: 0.701000s
Tue Jun 13 09:15:09 2000][462 489 ERROR] SE_stream_fetch :
The specified coordinate exceeds the valid coordinate range.
Tue Jun 13 09:15:09 2000][462 489 INFO2] SR FEATURES PROCESSED: 8478
Tue Jun 13 09:15:09 2000][462 489 INFO2] DATA RETRIEVAL TIME: 17.385000s
Tue Jun 13 09:15:09 2000][462 489 INFO2] TOTAL PROCESSING TIME: 18.086000s
Tue Jun 13 09:15:09 2000][462 489 INFO2] OUTPUT TIME: 0.060000s
Tue Jun 13 09:15:09 2000][462 489 INFO3] RESPONSE:
<ENVELOPE minx="344816.831000000470000" miny="5743678.860000000300000"
In addition to the information described above, the LOG files would also include any error messages generated by the Spatial Server.