In versions prior to ArcIMS 9.0, when viewing a specific ImageServer or FeatureServer service in a Web site or other viewing client such as ArcExplorer Java, this error may occur:
"Server not available for Service: <my_service_name>."
The error displays in a window titled "Input/Output Exception", and may be generated when initially displaying the service in the viewer, or it may eventually appear after zooming, panning or querying the data.
The AppServerDebug_#############.log simultaneously records the following error:
"... Error (java.net.SocketException: Socket read failed) in ServerPrxoy ImageServer1: ..."
The error also may also force the ArcIMS Monitor service to restore the Spatial Server, causing all other services to be temporarily unavailable. Therefore, the availability of all your ArcIMS services is jeopardized if the source of this problem is not corrected.
The cause of the problem is invalid geometry storage in one or more source data sets, even though no errors are generated when the ImageServer or FeatureServer service is created.
Initial proof of this is revealed when creating the AXL file in ArcIMS Author. The Author Message Console -- with Message Level set to All' -- will display the following error when a problematic data set is displayed, such as when visibility is on:
"... com.esri.mo.file.shp.InvalidShapeException: # invalid shape/s were detected in <data_set_name>".
Solution or Workaround
Invalid shapes must be removed from your data set(s).
Instructions for a method to determine the invalid features and the procedure to delete them is in the Knowledge Base article titled "Error: InvalidShapeException: invalid shapes were detected". A link to this article is provided below.